Printable View
No because the page(attach) are not in html, are in asp language, and the WL not resolve asp to html.. and show the code(asp).Quote:
Originally Posted by Oleg
looking for uptime... and I see the system log that WL500g restart... WL only restart whem I'm using must more the WL500g..Quote:
Originally Posted by Oleg
This is not an asp, but javascript, which is intended to run by browser.Quote:
Originally Posted by int
After changing the ip_conntrack_max to 4096 it works for a few minuts to half an hour, after that it has been resett to 1024. This happens if i put it in the post-boot script or if i do it manually.
:) Hallo everybody, first thing first a big thanks to Oleg not only because of the Firmware but also for his custom firmware page.
My WL-500g run vs. 1.9.2.7-2 work as a charm but i still have a short
request: I know the support for Samba is very limited but i still would like
to know if the share$ is on purpose kept read only
Wait for 1.9.2.7-3 or use search. Answered question yesterday. Hint: change user name to root.Quote:
Originally Posted by garimo
Just to update:
The router has not crashed/locked up/ or lost the WAN connection since yesterday. It seems that one of the problems is solved, although I don't know if it is because I went back to 1.8.1.7-3 or if it is truly a problem with a printer that is unpowered but attached to the WL-500g.
Also, I still cannot get a WAN connection when using the et command except if I it set it to auto. Here's the syntax I use
et -i eth1 speed XXX
where XXX = auto, 100full, 10full, 100half, or 10half. I have tried all speeds and firmwares 1.8.1.7-3, 1.9.2.7-1, and 1.9.2.7-2. My cable modem is a Toshiba PCX2500--perhaps it's some conflict with the modem?
Hi,
i have this problem with 1.9.2.7CR-2 using in client mode.
While I'm copuing files from my VPN (i'm also connected to VPN server), my Asus goes down after while.
if I'm not connected to VPN everything is OK.
in fw 1.7.9.5-5 i havent this problem.
What could i tried to fix?
Here is what i found in log:
Quote:
Jan 4 18:55:08 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 192.168.1.10:0x0 -> 172.16.1.248:0x66e:1:0x880b
Jan 4 18:55:08 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 192.168.1.10:0x0 -> 172.16.1.248:0x66e:1:0x880b
Jan 4 18:55:08 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 66e for tuple 172.16.1.248:0x0 -> 172.16.2.100:0x0:1:0x880b
Jan 4 18:55:08 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 192.168.1.10:0x0 -> 172.16.1.248:0x66e:1:0x880b
Jan 4 18:55:08 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 66e for tuple 172.16.1.248:0x0 -> 172.16.2.100:0x0:1:0x880b
Jan 4 18:55:08 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 192.168.1.10:0x0 -> 172.16.1.248:0x66e:1:0x880b
Jan 4 18:55:08 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 66e for tuple 172.16.1.248:0x0 -> 172.16.2.100:0x0:1:0x880b
Jan 4 18:55:08 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 192.168.1.10:0x0 -> 172.16.1.248:0x66e:1:0x880b
Jan 4 18:55:08 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 66e for tuple 172.16.1.248:0x0 -> 172.16.2.100:0x0:1:0x880b
Jan 4 18:55:08 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 192.168.1.10:0x0 -> 172.16.1.248:0x66e:1:0x880b
Jan 4 18:55:08 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 66e for tuple 172.16.1.248:0x0 -> 172.16.2.100:0x0:1:0x880b
Jan 4 18:55:08 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 66e for tuple 172.16.1.248:0x0 -> 172.16.2.100:0x0:1:0x880b
Jan 4 18:55:08 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 192.168.1.10:0x0 -> 172.16.1.248:0x66e:1:0x880b
Jan 4 18:55:20 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 66e for tuple 172.16.1.248:0x0 -> 172.16.2.100:0x0:1:0x880b
Jan 4 18:55:20 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 192.168.1.10:0x0 -> 172.16.1.248:0x66e:1:0x880b
Jan 4 18:55:20 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 66e for tuple 172.16.1.248:0x0 -> 172.16.2.100:0x0:1:0x880b
Jan 4 18:55:20 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 192.168.1.10:0x0 -> 172.16.1.248:0x66e:1:0x880b
Jan 4 18:55:20 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 66e for tuple 172.16.1.248:0x0 -> 172.16.2.100:0x0:1:0x880b
Jan 4 18:55:20 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 192.168.1.10:0x0 -> 172.16.1.248:0x66e:1:0x880b
Jan 4 18:55:20 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 66e for tuple 172.16.1.248:0x0 -> 172.16.2.100:0x0:1:0x880b
Jan 4 18:55:20 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 192.168.1.10:0x0 -> 172.16.1.248:0x66e:1:0x880b
Jan 4 18:55:41 kernel: ip_conntrack_pptp.c:pptp_outbound_pkt: outbound control message ECHO_REQUEST
Jan 4 18:55:41 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: sstate: 4->4, cstate: 3->3
Jan 4 18:55:41 kernel: ip_conntrack_pptp.c:pptp_inbound_pkt: inbound control message ECHO_REPLY
Jan 4 18:55:41 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: sstate: 4->4, cstate: 3->3
Jan 4 18:55:42 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: no full PPTP header, can't track
Jan 4 18:55:44 kernel: ip_conntrack_pptp.c:pptp_outbound_pkt: outbound control message SET_LINK_INFO
Jan 4 18:55:44 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: sstate: 4->4, cstate: 3->3
Jan 4 18:55:44 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 66e for tuple 172.16.1.248:0x0 -> 172.16.2.100:0x0:1:0x880b
Jan 4 18:55:44 kernel: ip_conntrack_pptp.c:pptp_inbound_pkt: inbound control message SET_LINK_INFO
Jan 4 18:55:44 kernel: ip_conntrack_pptp.c:pptp_inbound_pkt: invalid SET_LINK_INFO (TY=15)
Jan 4 18:55:44 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: sstate: 4->4, cstate: 3->3
Jan 4 18:55:44 kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 192.168.1.10:0x0 -> 172.16.1.248:0x66e:1:0x880b
Jan 4 18:55:44 kernel: ip_conntrack_pptp.c:pptp_outbound_pkt: outbound control message CALL_CLEAR_REQUEST
Jan 4 18:55:44 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: sstate: 4->4, cstate: 3->7
Jan 4 18:55:45 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: no full PPTP header, can't track
Jan 4 18:55:45 kernel: ip_conntrack_pptp.c:pptp_outbound_pkt: outbound control message STOP_SESSION_REQUEST
Jan 4 18:55:45 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: sstate: 4->2, cstate: 7->7
Jan 4 18:55:45 kernel: ip_conntrack_pptp.c:pptp_inbound_pkt: inbound control message STOP_SESSION_REPLY
Jan 4 18:55:45 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: sstate: 2->0, cstate: 7->7
Jan 4 18:55:45 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: RST/FIN received, timeouting GRE
Jan 4 18:55:45 kernel: ip_conntrack_proto_gre.c:ip_ct_gre_keymap_destroy: entering for exp 80c24780
Jan 4 18:55:45 kernel: ip_conntrack_proto_gre.c:ip_ct_gre_keymap_destroy: removing 808246a0 from list
Jan 4 18:55:45 kernel: ip_conntrack_proto_gre.c:ip_ct_gre_keymap_destroy: removing 80824660 from list
Jan 4 18:55:45 kernel: ip_conntrack_pptp.c:pptp_timeout_related: setting timeout of conntrack 807eea60 to 0
Jan 4 18:55:45 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: no full PPTP header, can't track
Jan 4 18:55:45 kernel: ip_conntrack_proto_gre.c:gre_destroy: entering
Jan 4 18:55:45 kernel: ip_conntrack_proto_gre.c:ip_ct_gre_keymap_destroy: entering for exp 80c24780
Jan 4 18:55:45 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: no full PPTP header, can't track
Jan 4 18:55:45 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: RST/FIN received, timeouting GRE
Jan 4 18:55:45 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: no full PPTP header, can't track
Jan 4 18:55:45 kernel: ip_conntrack_pptp.c:conntrack_pptp_help: no full PPTP header, can't track
J
Or change root to admin in smb.confQuote:
Originally Posted by Oleg
Friendly
Oldudu
thanks you all for replay, i got it working and you guys were right.
But my problem was that i changed in system setup the name "admin" for security reason, so in /etc/smb.conf force user = admin was not working and most likely also root for the same reason. It only worked with my login name.
My WL500G is used in access point behind a router (another ASUS).
Port forwarding is configure on the router to forward service FTP (port 21) and webcam (port 7776)
The problem is that FTP and webcam server don't work from wan access.
(It works in lan access).
The problem is the same when the router is a netgear or asus router.
Could you find a solution to my problem ?
Thank you
Alexis
Aren't you running on WinXP SP1? Is the connection lost in few minutes even if there's no data traffic? I suppose that "goes down" does not mean reboot nor hang.Quote:
Originally Posted by pipos
If that's the case, try to stop the Windows Management Instrumentation service before your VPN access attempt. SP2 update could also help.
Try to search the forum and double check your configuration. Try to configure the router from scratch (apply reset to defaults first).Quote:
Originally Posted by Alexis
In case you can't fix the problem still, specify your firmware version and more config related details.
I'm Running WinXP SP2,
It looks like eth2 die....
when i look at the shell and run top....the 5min avg usage goes up to 2.5 and then it disconetcs...
whne not in VPN...usage is cca 0.2
OK so you loose the wireless connectivity completely. What you do to make it working again? Do you have to reboot the router or do you just initialize the interface somehow?Quote:
Originally Posted by pipos
What's the free memory status?
could you supply a testaccount or something to test so I can confirm the possible 'bug' ?Quote:
Originally Posted by pipos
That's strange. I've been using VPN as well, and without any problems. Even with transferring large files, my vpn connection stayed up throughout the whole day, and so did my Asus.Quote:
Originally Posted by pipos
I use it to work from home, so I "hook up" my laptop wireless and work the whole day.
I've been running olegs 1.9.2.7-2 . I've just fired up a vpn connection to the office, and my average doesn't go up.
It runs rock solid over here.
...using in client mode...Quote:
Originally Posted by wiz
That's the difference!
Addiotinal load was probably caused by debug messages produced by pptp kernel modules - try 1.9.2.7-3.
I have found, that 1.9.2.7 firmware is is using command tc for bandwidth management and is distinct from wshaper added by Oleg.
Is someone using that?
Should I use tc or wshaper approach?
Can anyone suggest me which is better?
Also I have discovered that limits labeled as kbps (kilobits) in GUI are kBps (kilobytes) in fact (tc reports numbers eight times higher than entered!)
So, it looks like QoS doesn't work, but if you divide limits by eight, it works fine - maybe Oleg can fix that in custom FW.
Hi Oleg,Quote:
Originally Posted by Oleg
couldy you answer me to this questions please:
in 1.9.2.7-3
- is it possible to make wireless bridge in client mode (the same network at eth2 & eth0)
- where is watchdog configuration? how can i change it? what is in it's config by default?
- is it possible to enable afterburner with this fw?, does afterburner works in WDS mode too?
- what about WPA? does it works in WDS?
i cannot test this thing at this time, by i need them.
Could you, or somebody test this and give me answers?
thanks a lot for all.
btw. THX for very nice and helpful firmwares Oleg. I'll send you some donations when i earn some money. For this time i'm 'moneyless' :(
It's better to post this in the 1.9.2.7-3 thread.Quote:
Originally Posted by pipos
Yes, switch to AP mode, which should do the trick.Quote:
- is it possible to make wireless bridge in client mode (the same network at eth2 & eth0)
what do you need exactly?Quote:
- where is watchdog configuration? how can i change it? what is in it's config by default?
Sure.Quote:
- is it possible to enable afterburner with this fw?,
have no idea. I do not have afterburner capable devices.Quote:
does afterburner works in WDS mode too?
it does not work with 1.9.2.7.Quote:
- what about WPA? does it works in WDS?
There is no need to donate answers, the only donation Antiloop asked about was forum support, i.e. forum license and hosting. We're helping for free. :)Quote:
btw. THX for very nice and helpful firmwares Oleg. I'll send you some donations when i earn some money. For this time i'm 'moneyless' :(
I've been using 1.9.2.7-1 and everything was fine. Obviously, I disobeyed the rule.."don't touch it if it works" and I upgraded to 1.9.2.7-3. And it happened that I couldn't ping wireless clients and WDS clients anymore. Same happened when I downgraded to 1.9.2.7-2. When I downgraded to 1.9.2.7-1 again, it started working. All this was without hard reseting the router. BTW, in the Status&Log->Wireless section of the web interface, I could see the wireless client MAC address and it said .. associated.
Good finding, hopefully I've fixed it now.Quote:
Originally Posted by yato
bungee, this is not CR3 topic. also, there is already 1.9.2.7-3a available for download, which fixes most of the problems. If you still has problems, post your syslog to the correct thread.Quote:
Originally Posted by bungee