Netopia Router command to restart internet connection?

crudpuppy

We are using a Netopia 2247nwg router for our broadband which is currently supplied by Gaelic Telecom. The problem is, when we start the router, it doesn't automatically make a connection to the internet - we have to manually start it ourselves using the router's web interface,
http://192.168.1.254/indexRES.htm?homeRES.htm.

This is an unnecessary pain in the proverbial, especially given that when we start Firefox after initial bootup (running Ubuntu Jaunty) we end up with a bunch
of "Page not found" errors if we don't start the connection from the router in time.

So, I am modifying a Python script found at http://forum1.netgear.com/showthread.php?t=3635&page=5 (from Jetman3) to do this automatically from my Linux box.

It involves creating a telnet connection, logging in and then running the appropriate command. Unfortunately I can't identify the correct command. From the
router's command-line help I can see how to restart the router (restart), or reset the dsl (reset dsl) and a variety of other things (relating to configuration, status and troubleshooting) but I cannot see how to (re)start the connection. I'd also like to be able to use this script whenever the connection drops.

I've spent time yesterday experimenting and Googling, and no luck, not even from the Netopia manual (http://www.netopia.com/equipment/pdf/manuals/CLI/CLI_411-538-82.pdf)
which is for firmware versions 4, 5 and 8, whereas my router is running firmware 7.7.0r6 (Latest Firmware is 7.7.4 R1 according to http://www.netopia.com/support/hardware/2247w.html).

Can anyone help, please?

Thanks in advance,
Crudpuppy

cpu-dude

crudpuppy wrote: »

We are using a Netopia 2247nwg router for our broadband which is currently supplied by Gaelic Telecom. The problem is, when we start the router, it doesn't automatically make a connection to the internet - we have to manually start it ourselves using the router's web interface,
http://192.168.1.254/indexRES.htm?homeRES.htm.

This is an unnecessary pain in the proverbial, especially given that when we start Firefox after initial bootup (running Ubuntu Jaunty) we end up with a bunch
of "Page not found" errors if we don't start the connection from the router in time.

So, I am modifying a Python script found at http://forum1.netgear.com/showthread.php?t=3635&page=5 (from Jetman3) to do this automatically from my Linux box.

It involves creating a telnet connection, logging in and then running the appropriate command. Unfortunately I can't identify the correct command. From the
router's command-line help I can see how to restart the router (restart), or reset the dsl (reset dsl) and a variety of other things (relating to configuration, status and troubleshooting) but I cannot see how to (re)start the connection. I'd also like to be able to use this script whenever the connection drops.

I've spent time yesterday experimenting and Googling, and no luck, not even from the Netopia manual (http://www.netopia.com/equipment/pdf/manuals/CLI/CLI_411-538-82.pdf)
which is for firmware versions 4, 5 and 8, whereas my router is running firmware 7.7.0r6 (Latest Firmware is 7.7.4 R1 according to http://www.netopia.com/support/hardware/2247w.html).

Can anyone help, please?

Thanks in advance,
Crudpuppy

Eh, are you sure the router isn't set to manually connect? By default it's set to On Demand, you should set it to Always On.

On your computer, do the following:

Go to http://192.168.1.254/ > Expert Mode > Yes, Enter Expert Mode > Configure > Connection > Connection Type > Always On / On Demand / Manual > Save and Restart Connection.

crudpuppy

Thanks cpu-dude. It was set to on-demand. I have set it to always on which hopefully would sort out the problem at start time.

Regards,
Crudpuppy.

crudpuppy

To confirm: this works; just restarted router and it automatiically connected, whereas before it didn't. Thanks again.

cpu-dude

crudpuppy wrote: »

To confirm: this works; just restarted router and it automatiically connected, whereas before it didn't. Thanks again.

No problem!