Printable View
Hi all,
I upgraded my Asus WL-500gx to firmware v.1.9.2.7 CR3b, but I can properly change this Asus to fully functional client mode (just like 1.7.5.9-5).
I need connect to internet over Wifi and all eth ports is used on LAN with DHCP. Nat isn't used, because I have C blok routed over Wifi to my LAN.
Please help me with this settings.
Thanks a lot
I've already had two reboots last 40 minutes. This afternoon I have installed 1.9.2.7-3b on the WL500g. A reboot at 19:09 and 19:36. What causes this problem.
ISP is cable. USB stick plugged in. 1 wired pc, 1 wireless.
Need more info?
Edit:
Downgraded back to 1.9.2.7 (which I had before). Still the same problem.
Possible that the processor gets overheated, after using 3b?? (What's the routers behaviour when overheating?)
Something different now: What about the guerantee if you upgrade to an official firmware?
Hi Oleg,
I just upgradet my asus to 1.9.2.7-3b
when i use VPN (PPTP) my asus still fils syslog with this:
ASUS us in ethernet bridge mode, without NAT (AP operation mode, NOT HomeGateway)Quote:
Jan 22 23:04:19 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:19 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_new: : 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:19 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: entering
Jan 22 23:04:19 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: no master exp for ct 80c00480
Jan 22 23:04:20 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:20 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_new: : 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:20 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: entering
Jan 22 23:04:20 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: no master exp for ct 80c00480
Jan 22 23:04:22 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:22 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_new: : 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:22 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: entering
Jan 22 23:04:22 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: no master exp for ct 80c00480
Jan 22 23:04:22 172.16.x.x ntp client: time is synchronized to time.nist.gov
Jan 22 23:04:40 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:40 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_new: : 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:40 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: entering
Jan 22 23:04:40 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: no master exp for ct 80c00e20
Jan 22 23:04:40 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_pkt_to_tuple: found src key 0 for tuple 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:40 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_new: : 158.193.x.x:0x0 -> 172.16.x.x:0x0:1:0x880b
Jan 22 23:04:40 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: entering
Jan 22 23:04:40 172.16.x.x kernel: ip_conntrack_proto_gre.c:gre_destroy: no master exp for ct 80c00e20
Have you an idea what could be the problem? Is this just some debug info?
With 1.9.2.7-2 my asus go down and freezes finaly when i start transfer with pptp
THX
The same problem here. I tried all the Oleg's custom fws for 500gx, none works in client mode.
If switched to client mode ("station" on the web interface), the device doesn't respond to pings, or any other network connections on eth0, didn't try eth1 or eth2 though. Also, it reboots over and over every half a minute or so.
Quote:
Originally Posted by Cabal
Hi,
wl500g works fine with 1.9.2.7-3b in client mode..
Bridged (AP mode)
NATed (Home gateway mode)
Now i test it for stability....but no reboot since last 12h (bridged)
No problems with wl-500g, wl-500gx is what gives me the troubles.
Quote:
Originally Posted by pipos
can you please confirm this:Quote:
Originally Posted by hynek
turn on WPA-PSK encryption at wl500gx (don't use client stuff now) and verify it is using WPA-PSK or that it is OPEN(no encryption used at all)
I can't verify that at this moment, but the device was always reset after firmware upgrade, thus I assume, the wireless was set to OPEN.
Quote:
Originally Posted by Antiloop
that's not what I am askingQuote:
Originally Posted by hynek
turn on WPA-PSK encryption, and just verify it is using encryption at all or that it is using no encryption (while WPA-PSK has been turned on)
Just thought I would let you know that version 3b has seemed to clear up the problems I have been having with dropped VoIP calls on 1.9.2.7 firmware versions. Don't know why--but thanks for the hard work
Hi,
I'm using two computers linked through a WL500g (with firmware 1.9.2.7-3a, but as far as I can tell it's irrelevant). Both use wired connection and both boot either Linux or WindowsXP. When I use Windows sometimes the DNS seems to disappear. I can still connect from (obviously using IP numbers instead of fully qualified domain names) and to the corresponding computer (I have a Cygwin sshd running). I've not observerd the same problem with any of my computers using Linux. I've also observed that if I change the DNS "Use 192.168.1.1 as preferred DNS", then "Use DHCP provided DNS", Windows goes back to normal. There is probably a bug in the TCP/IP stack of Windows (who would have believed it ?) but the behaviour is strange: it does not occur if I connect directly to my provider (using DHCP as well) but only through the router and only with Windows. Does anybody have any idea ?
SurJector