OpenWrt Forum Archive

Topic: WAN port problems

The content of this topic has been archived on 31 Mar 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

I have a wrt54gsv3 that i just put rc5 on.
I have used rc4 on a gsv4, put this is the first time i've used this v3 router.
My problem is that I can't seem to use the wan port.
The light goes on and blinks when data goes through but if i try to ping the external address (192.168.1.220, static) i don't get a response.
When plugged into a LAN port, i can ping both the internal (192.168.1.200) and the external ip, as expected.
I do not know if the port worked with the original firmware, i didn't think to test more than i could get to the original firmware's web interface.
I have modifed firewall.user to allow port 22 and port 80 through on the wan port, but i don't think that matters if i can't even ping the bugger.
Hopefully it's a software issue, but if the wan port is damaged somehow, how can i reroute it to one of the other ports?
Let me know what info you need.

freecheeseman wrote:

The light goes on and blinks when data goes through but if i try to ping the external address (192.168.1.220, static) i don't get a response.
When plugged into a LAN port, i can ping both the internal (192.168.1.200) and the external ip, as expected.

Do you have the WAN and LAN ports on the same subnet?  That may be the cause of the issue, as OpenWrt default behaviour is to NAT the WAN port...

Cheers,
Martin.

they are both 192.168.1.*'s, can i easily set rc5 to use a 10.* network or is it better to go with 192.168.2.*?

i loaded the linksys firmware to check if the port itself is physically wrong, and after changing it to 192.168.2.1 and 255.255.255.128 i am able to get it to work as expected as long as i use a static wan ip. the wan dhcp freaks out like crazy, if i refresh the status page i can watch it jump from having an ip with dns servers, an ip without dns and to zeros randomly at very small intervals (it changes almost everytime i refresh). looks like you were right about the subnet bit. thanks for the point in the right direction, does anyone know why the dhcp so strange?

(Last edited by freecheeseman on 9 Apr 2006, 03:15)

The discussion might have continued from here.