> See Network-Startup how to restart NetStack.

It might be necessary to quit it before restarting. Proper quitting has been described here by the NetStack author.

@Chris

Once this happens, open a new shell and issue an ifconfig command, paste the output. If the eth0 address isn't 0.0.0.0, try to do a ping 8.8.8.8, paste the output. This should tell us a bit more about what the issue might be in your case.

I can't seem to go 24hrs without my network dropping for awhile now, but whatever!....I'm no programmer

Quote:

Same diagnostical instructions apply.

use static ip address

When network started

New Shell process 2
Ram Disk:> ifconfig
lo0: flags=8009<UP,LOOPBACK,MULTICAST> MTU=16436
inet 127.0.0.1 netmask ff000000
Hardware type: Loopback

eth0: flags=4863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,SANA> MTU=1500
inet 192.168.1.64 netmask ffffff00 broadcast 192.168.1.255
Hardware type: Ethernet, address: 0:14:51:15:b8:ba

Use "ifconfig -h" for usage.
Ram Disk:>

When network dropped

Ram Disk:> ifconfig
lo0: flags=8009<UP,LOOPBACK,MULTICAST> MTU=16436
inet 127.0.0.1 netmask ff000000
Hardware type: Loopback

eth0: flags=4863<UP,BROADCAST,NOTRAILERS,RUNNING,SIMPLEX,SANA> MTU=1500
inet 0.0.0.0 netmask 0 broadcast 0.0.0.255
Hardware type: Ethernet, address: 0:14:51:15:b8:ba

Use "ifconfig -h" for usage.
Ram Disk:>

I don't know what it means to 'ping' anything

> I don't know what it means to 'ping' anything

http://en.wikipedia.org/wiki/Ping_(networking_utility)

Quote:

Thanks. I have in fact already found the reason for this issue and it will be resolved in 3.6 but for now you may also change your router's configuration - set the DHCP lease time to the maximum value.

Thanks, but how? Is this done in system settings?

Quote:

In your *router's* settings.

Oh, I don't remember how to do that. I initially set up on a PC with some help from customer service a few years ago.

Quote:

Your router should probably be controlled with its web interface. Try opening http://192.168.1.1 in your browser. If that doesn't work try http://192.168.1.254 instead. And if that isn't correct address either try to find out which your gateway address is (for example with "traceroute -q 1 8.8.8.8" in shell.

Then it asks login and password, which you should know. If you haven't changed them ever, maybe you have your router's manual around. Or try admin/admin. Or google default password for your router's model.

When you get logged in, browse those menus until you find correct DHCP settings :)

Good to hear that this will be addressed and that there's a workaround as well. The suggestion to use a static IP address also worked for me. Once I did that, no more issues.

Thanks JPV, but apparently I'd have to reset the router, since the passes didn't work. I think I'll just wait for the upgrade rather than fiddle around, and unintensionally mess up a setting, which MorphOs is not the only system on it.