Network timeout

[markebailey]

I have not made it back to Torrey yet but a couple of guests have tried to help me out who were there. No luck yet.

Maybe this is the problem: On the Torrey Linksys router WRT54G set up page, Setup/DDNS/dyndns.org shows the internet IP address as 10.0.0.6, a LAN address not a WAN address. I don't see how to change that to the WAN IP address. Perhaps this is a clue: On the Torrey Linksys router under Administration/Management there is no Web Access section like there is on my Linksys WRT54G router in SLC where "Access Server: HTTP or HTTPS /Wireless Access Web: Enable Disable" can be checked.

My account at Dyndns.org is set up for the Torrey WAN IP with a new host name.

Also, I had my son, who was in Torrey, enable Remote Management on the Torrey router. I tried to access it via dyndns and via the torrey address IP:8080 from SLC and got, you guessed it, Network Timeout.

WTF? :blink:

[d_l]

My best guess as to why DynDNS has a private IP is that your router's WAN port is probably being issued a private IP from your DSL modem. This might happen if the modem was making the PPPoE connection and it wasn't configured to passthrough the public IP.

If it doesn't have a public IP passthrough option, then you would have to bridge the modem and let the router make the PPPoE connection. Once it makes the connection, it will know what the public IP is.

[markebailey]

Thank you d_l. I'm getting an education. Next time I'm in Torrey I'll check the DSL modem settings. It does look like the DSL modem is issuing a private IP address to both the router and to dyndns and is not passing through my address requests to remote manage the router -- or any other addressing requests.

[d_l]

I thought the router was doing the DynDNS updating. Then the router would only have that private IP to update DynDNS.

... or did you try updating DynDNS remotely from SLC with the public IP at Torrey? That public IP should then keep changing back to the private IP if the router is doing its updating job correctly.

Yes, it is entirely possible that the DSL modem is blocking inbound packets to the router. In that case, the modem would be acting as a router and "protecting" your regular router from your "attack". This is a called double NAT situation.

If this is the problem, the modem must either be put into a DMZ mode to pass all port traffic (often times the public IP passthrough will put it in a DMZ mode too) through or be bridged.

[markebailey]

I don't know what updates DynDNS. The router is set to, but the router has the local address which seems to be set by the DSL modem. I did try updating DynDNS remotely from SLC. 10 hours later it still has the public IP address I put in. Maybe that is a clue too. Thanks again for your help on this. I assume there is no way to manage a DSL modem remotely. I hope to be in Torrey later this weekend.

[d_l]

Some DSL modems can be remote managed, but that isn't a regular feature of most. If you have to bridge it, that should be done on site.

I think the Linksys router is only supposed to update DynDNS when the router has seen a change in the IP at its WAN. It probably doesn't have the sophistication to check if the IP DynDNS is using has changed. That isn't something that would happen often and so there is no need for that capability.

[markebailey]

As I think this through to the best of my understanding at this point, it looks to me like the DSL modem has been the problem all along. It gave the router the local ip address and the router updated DynDNS. The modem has blocked all incoming packets no matter how the router was set up and no matter if they came through DynDNS or were addressed directly. I've been barking up the wrong tree chasing down the source of the local ip problem. d_l, good trouble shooting!

[markebailey]

I am in Torrey. When I browse for my current Torrey WAN IP address I now get the DSL Modem administrative interface. I get it whether or not DMZ is enabled. I tried setting the modem dmz for the local 10.0.0.6 address as well as the 192.etc address. I get the same thing when I browse for the dyndns.org address. All the bridge settings seem to be previously enabled. Maybe if the system were addressed from outside my LAN it would be passed through to the meteohub, but I doubt it. It looks like I need more specific help setting up the DSL modem's DMZ or the pass through or the bridge or some such.

My unfullfilled goal remains to access the meteohub's administrative interface from the public internet.

[d_l]

Is there any option for a passthrough of the public IP?

[markebailey]

Hi d_l, No, I don't see the word passthrough anywhere in the setup or configuration areas.

[d_l]

What is the modem model and who is your internet provider?

[markebailey]

Visionnet W202, South Central Communications (Utah). I'm planning on call SC tomorrow.

[d_l]

I can't find a manual for that modem model on the internet.

Does it have a factory default reset button? The reason I ask is that you might have to bridge the modem to insure that your router WAN is getting the public IP and all the incoming packets for all the ports. If the bridging doesn't work, the reset button is useful to restore the modem to the way you have it now.

You would make the PPPoE connection with the router when the modem is bridged.

[markebailey]

I had looked for the manual too. Thx for checking. The modem does have a reset button. In messing around I have had to use it. The reset button works. I have not been able to find the place in the admin interface to set the modem to bridge to the router nor can I see where I would set up the router to make the PPPoE connection with my ISP username and password. Maybe the ISP can tell me.

[d_l]

For the various WRT54G models, there is a drop down box for Internet Connection Type on the main page that lists PPPoE. That would be what the selection you want. Do you have anything like that on your router?