Info regarding "WAN dies"

[WlanMan]

Full speed means Card/Port can send data while recieving data. Some Manufakturers call this 20 or 200mbit Mode, but in fakt ist not faster. You should set the port fixed to the rate your modem supports (mine for instance is only 10mbit), and set it to half because this doesen´t limit anythink in this situation and is the older and so hopefully compatible setting.

[Thorz]

Full speed means Card/Port can send data while recieving data. Some Manufakturers call this 20 or 200mbit Mode, but in fakt ist not faster. You should set the port fixed to the rate your modem supports (mine for instance is only 10mbit), and set it to half because this doesen´t limit anythink in this situation and is the older and so hopefully compatible setting.

Thanks m8 for that info.

[PROnline]

Hi there, I've configured the 500g as an accesspoint only because I was sick and tired of resetting the router. My ADSL-modem is doing the routering now.

Still the wanport died sometimes. I changed the WAN cable with one of my pc's and now only the PC dies when I copy for example a whole DVD.
But I don't lose the internet connection on the other PC's.

I was wondering if it would be possible for Oleg to make a custom firmware which uses lan1,2,3 or 4 as the WAN instead of the official WAN, to check if it's a port or a router capacity problem.

[Oleg]

In the AP mode all ports are bridged. So, you could avoid problems by connecting everything to LAN port, keeping WAN empty.

Yes, this a WAN port problem, LAN ports a being managed by internal switch and does not have any problems.

[Antiloop]

or just set it at a fixed speed
note: it can take a while (few minutes) before WAN port comes up then.

[SocoNaTromba]

I've recently bought a wl500g router, and dsl-300t d-link adsl modem.
I was suffering from this "wan port dies" problem... tried lot of cofigurations in the modem and in the router... but it kept crashing upon large amount of traffic, although the lan conections still worked perfectly, and I was even able to telnet to the router ..., everytime it crashed I used to hard reboot de router to get back internet connection again.
This used to happen even after I updated de router with the latest Oleg's firmware ( thankz oleg for your great work and dedication, it should be recognized "finantially" by asus)...

... I was really considering returning the router to the seller, till I tried the following:

I configured modem with the ip 192.168.0.254. then I configured it to work in bridge mode, and its dhcp server disabled. then I configured the router with the lan ip 192.168.0.110.

The "speed negotiation method" seem not to work with this modem, as its ethernet led never lits up when I set negotiation other then "auto".

I've configured manualy the DNS server 1 , as the second is locked to router's ip.

...configured username and password for dsl connection....

putted the wireless channel fixed to channel 6. changed SSID...
...blanked router's host name....

mac filtered to the pc's on the lan and to 2 wireless cards...
activated dhcp and manual ip for each mac address inserted.
distinct port forward to both lan connected computers so azureus could accept remote connections.

every other config as defaults...

well well, what did I do ?!

Now the connection IS completely stable, with constant heavy trafic, using 2 computers on lan both with Azureus connected 24H/day using all the bandwith, with frequently 400KB/s download speed / 100KB/s up speed ,,, and its efficiency is completely ok 100% without crashes... just the forced disconnection every 18 hours imposed by the isp...wich reconnects in aprox 30secs...

And the really funny thing:
when I try to, after all this configs, open http://192.168.1.1/ it prompts me for username and password, indicating: "level 15 access"... admin/admin does not work...

remember that my configs uses the group 192.168.0 instead of 192.168.1

it shouldn't exist a 192.168.1.1... on my local network...

so I made a trace route to that ip...

C:\Documents and Settings\Hugo Pinto>tracert 192.168.1.1

Rastreio da rota para 192.168.1.1 até o máximo de 30 saltos

1 <1 ms <1 ms 1 ms 192.168.0.110
2 18 ms 19 ms 19 ms r6613.nr.ip.pt [195.23.0.154]
3 19 ms 19 ms 19 ms 195-23-31-126.nr.ip.pt [195.23.31.126]
4 20 ms 22 ms 139 ms 195-23-31-129.nr.ip.pt [195.23.31.129]
5 52 ms 23 ms 27 ms 194-79-92-9.nr.ip.pt [194.79.92.9]
6 60 ms 25 ms 26 ms 195-23-31-234.nr.ip.pt [195.23.31.234]
7 27 ms 23 ms 25 ms 213-205-74-41.nr.ip.pt [213.205.74.41]
8 52 ms 31 ms 28 ms 192.168.1.1

Rastreio concluído.

hum? 192.168.1.1 goin out to the adsl connection?
could this be the reason of the wan crashes?

Because if somebody uses 192.168.1.1 as lan ip for router, the default ip for router, I wonder if it is somehow conflicting with the other ip existing on the internal network of my ISP...

I read somewhere at chupa.nl that the "wan dies" problem has something to do with the dns requests... so thats why I configured it manually...

Could any body that has the "wan dies problem" checkout if a tracert 192.168.1.1 , after configuring the ips with the 192.168.0 class, returns any jump?

Best regards

Hugo Pinto

[tomilius]

Your ISP has an interesting configuration, but not all ISPs are like this--that's very substandard. Interesting personal find, though. You might want to switch ISPs (if that's an option) since they seem pretty.. stupid.

[SocoNaTromba]

well yeah I know it... this is a new ISP here in portugal... they're still configuring their network, as they are implementing 16mbps adsl conections, .... for some reason I haven't received yet any request for payments, and I have the connection since March... also the download limits aren't yet counting... and speeds are way up then the producted I subscribed with them...(2mbps)
I made a port scan to ips from 192.168.1.1 to 192.168.1.254 and I found the first three with opened telnet and http ports...
telneting asks for password, adn browsing to those address it prompt for password to...

[tomilius]

Nice speed. From the hearsay (I'm not positive) the WL-500g might not be so great at handling it, though. That's still a valuable find--I mean, the router shouldn't have to crash for such a simple conflict. It's touchy that way. If only it could just tell you what was wrong... even Windows can tell you if there's an IP conflict. Anyway, yeah, I'd leave it as you have it if it works, or maybe you should switch all the way over the 10.x.x.x... but if it's not broken don't fix it, of course.

While you may not have pinpointed the problem for everyone, you have at least shed into further light the router's irrational touchiness.

[Oleg]

as for level 15 - this is also reported by int, so you're probably connected to the same ISP, and this addressed is used by some equipment of whatever.

[int]

as for level 15 - this is also reported by int, so you're probably connected to the same ISP, and this addressed is used by some equipment of whatever.

two difirent ISP...



my are SAPO ADSL

SocoNaTromba are CLIX ADSL

[int]

like i show to Oleg:


http://semana.com.sapo.pt/normal.gif
http://semana.com.sapo.pt/level15.gif
http://semana.com.sapo.pt/firefox_level15.gif

if i put any password show
http://semana.com.sapo.pt/failed.gif

this failed page, that i think are the failed page of ISP equipment, and not of WL

[SocoNaTromba]

well, I ' ve found these machines.....
192.168.1.1
192.168.1.2
192.168.1.3
192.168.1.100
192.168.1.254

every single one with telnet and http ports opened

is there any chance that the possibility of confliticting IP's could be the reason of the "wan dies" problem?

Me and Int, we have different ISPs but seems that they use the same way of configs...

[Oleg]

This is not a "wan dies" problem. As with wan dies the port could be recovered by typing this:

et -i eth1 promisc 0

[phedny]

Interesting to know:

At home I've got one WL-500g (w1) in Home Gateway mode connected to my ADSL modem. Another WL-500g (w2) in Access Point mode is connected to w1. The cable on w1 is on the LAN side.

Placing w2 cable side in LAN is no problem...
Placing w2 cable side in WAN gives the WAN-port-die problem after a couple of hours...

(By the way: I didn't try chaning any settings yet -- I just thought it would be interesting information)