No http access over wan port

[murph]

I seem to have an issue after a reboot that I can not get into my N5200R via the web browser over the WAN port. I can get in fine over the LAN ports via web though. When I browse via the WAN IP, I get a blank page that eventually times out. Using the LAN IP it goes straight otthe web login page.

I can ssh to the box over the WAN port, so I know it is not a routing or hardware issue.

No issues show up in the log at all.

Any ideas of what to look at?

-murph

[omega]

Hi murph,

in order to be able to imagine what could be wrong it would help if you post your network interface settings of the two network interfaces.

If you have SSH access then it would be perfect to post the output of these commands:

ifconfig
netstat -r

And it could be interesting if you post from what computers you're trying to access the N5200 and their IP settings.

It looks like you're having just a network misconfiguration....

Andreas

[murph]

Thanks Andreas,

I havenot changed any of the WAN or LAN addressing, and I can ping all of it. Since I can also get to the ssh over the wan address, I'm thinking it is something else. I am trying to access it from several different computers on my lan. The computers range in IP form 192.168.0.1 - 15. I also have 2 computers on the 192.168.2.x network as well for accessing on the lan side directly.

Here is the output you requested:

root@127.0.0.1:~# ifconfig
eth0 Link encap:Ethernet HWaddr 00:14:FD:10:76:D8
inet addr:192.168.0.225 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:58373 errors:0 dropped:0 overruns:0 frame:0
TX packets:82738 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12877594 (12.2 MiB) TX bytes:21950015 (20.9 MiB)
Base address:0xd400 Memory:e8100000-e8120000

eth1 Link encap:Ethernet HWaddr 00:14:FD:10:76:D9
inet addr:192.168.2.226 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:24564 errors:0 dropped:0 overruns:0 frame:0
TX packets:574 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3335212 (3.1 MiB) TX bytes:83239 (81.2 KiB)
Base address:0xd500 Memory:e8120000-e8140000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6125 errors:0 dropped:0 overruns:0 frame:0
TX packets:6125 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:888922 (868.0 KiB) TX bytes:888922 (868.0 KiB)

tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.118.216.1 P-t-P:10.118.216.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 B) TX bytes:3339 (3.2 KiB)

----------------------------------------------------------------------------------------------------------------------

root@127.0.0.1:~# netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
10.118.216.2 * 255.255.255.255 UH 0 0 0 tun0
192.168.2.0 * 255.255.255.0 U 0 0 0 eth1
10.118.216.0 10.118.216.2 255.255.255.0 UG 0 0 0 tun0
192.168.0.0 * 255.255.255.0 U 0 0 0 eth0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 192.168.0.201 0.0.0.0 UG 0 0 0 eth0


Not sure wher the 10.118.216.x addressing came from, unless one of the media server mondules added that (SlimServer or Jinzora)

-murph

[kevincy]

10.xx.xx.xx. is VPN ip for NSYnc .
Could you type the other command "route -n" .

[murph]

Thanks for the nsync clarification kevincy.
here is the info for the route - n command...

root@127.0.0.1:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
10.118.216.2 0.0.0.0 255.255.255.255 UH 0 0 0 tun0
192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
10.118.216.0 10.118.216.2 255.255.255.0 UG 0 0 0 tun0
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 192.168.0.201 0.0.0.0 UG 0 0 0 eth0

The 192.168.0.201 (gateway) is the router I am attached to.