Does this happen to anyone? If my net drops sometimes i will cycle down then power back up my modem/router. This inturn disconnects my server from my network and my only fix i know is to reboot my server machine. This isnt a major issue just wondering if there is a cleaner way of reconnecting my server once it disconnects?

 

Cheers

Steve

 

 

Does this happen to anyone? If my net drops sometimes i will cycle down then power back up my modem/router. This inturn disconnects my server from my network and my only fix i know is to reboot my server machine. This isnt a major issue just wondering if there is a cleaner way of reconnecting my server once it disconnects?

 

Cheers

Steve

Try typing:

/etc/rc.d/rc.inet1  restart

What happens, of course, is that the old IP assigned to your server is no longer valid in the router's IP table.    So you need to do the Linux equivalent of Windows' "IPConfig /renew" command.

 

Fortunately, Joe L has posted that command for us -- I definitely made a note of it !!

(Thanks Joe)

 

You could either run a static IP or static DHCP lease on your router for your server and avoid the DHCP lost lease issues on router reboot.  What router are you using?

 

Setting a static IP on your server would indeed be a reasonable way to avoid this issue.  Just be sure it's (a) in the same subnet as the DHCP-assigned range for the router; and (b) "out of the way" of the IP's the router may assign via DHCP ... e.g. if the router is set to assign IP's from 192.168.1.1 ... 192.168.1.50, then use 192.168.1.55 for your server.

 

thanks Joe L, i assume that command needs to be typed in once you have logged into the server? Which has always been a hassle for me due to never being able to get the telnet function working properly. I have noted that command though im sure it'll come in handy, cheers

 

A permanent solution sounds good i have just switched over two other machines on the home network to static IPs.

 

Just be sure it's (a) in the same subnet as the DHCP-assigned range for the router; and (b) "out of the way" of the IP's the router may assign via DHCP

 

Im using a Netgear DGND3700v2 modem/router. My gateway is 192.168.0.1

I have 'use router as DHCP server' ticked.

My ip address range is 192.168.0.2 - 192.168.0.254

My other wireless devices that come on and off the network get dynamically assigned ip addresses and are always around the 192.168.0.6 or .7..ect

I assigned my netbook and htpc static ip addresses of 192.168.0.2 and .4 respectively last week.

Are you suggesting i should re-assign those devices and assign my tower a static ip address outside the range ie 192.168.0.255? But insure that the 'subnet' is indeed 192.168.0

Is this right?

 

edit:

windows wont allow me to assign a static ip address to my netbook above .255, so i guess i'm wrong

 

Regards

Steve

 

My ip address range is 192.168.0.2 - 192.168.0.254

My other wireless devices that come on and off the network get dynamically assigned ip addresses and are always around the 192.168.0.6 or .7..ect

I assigned my netbook and htpc static ip addresses of 192.168.0.2 and .4 respectively last week.

Are you suggesting i should re-assign those devices and assign my tower a static ip address outside the range ie 192.168.0.255? But insure that the 'subnet' is indeed 192.168.0

Is this right?

 

Regards

Steve

 

Yes, I'd change the static IPs to something well above anything the router's likely to assign.  You said it's set to assign IP's between 192.168.0.2 - 192.168.0.254 ... so something like 192.168.0.66 and .77 would be very safe.    In fact, you could change the settings in the router to only assign from 192.168.0.2 to 192.168.0.50, and then you'd KNOW it would never conflict with your static addresses.

 

FWIW I have my router set to assign between .2 and .100, and simply use addresses above .100 for the few static addresses I use.

 

thanks gary, should i use this address reservation tool i found on my modem GUI?

 

If i was to duplicate your behavior and limit the routers range i would do so by taking out the 254 and replacing it with 100?

 

Is this right?

 

Cheers

Yes, if you change the 254 to 100 you'll be limiting the DHCP assignments to 192.168.0.2 to 192.168.0.100

 

Then you could use 192.168.0.101 and 192.168.0.102, etc. for static IPs.

 

An alternative to using static addresses is to use the address reservations you noted ==>  you can use that to identify specific hardware and ensure it is always assigned the same IP via DHCP.    But if you use static IPs, you don't need to do this.

 

Since your router provides for address reservations, you may want to use that instead of static IPs.    For a fixed installation it doesn't make much difference -- but if you're using anything that's mobile (e.g. your netbook), then using a reserved address will ensure it always has the same address when connected to your network;  but is still using DHCP, so it will also work okay if you're using it somewhere else (where the specific static address you might have assigned may not work).

 

I wll go back into windows and reassign my netbook as 'obtain an ip address automatically'

Then under my my router interface reserve it an ip address of 192.168.0.102

And this way it will have the same benefits of a static assigned device but also still be able to connect to public networks or tethered networks when its on the road.

 

Your the man Garycase!

I wll go back into windows and reassign my netbook as 'obtain an ip address automatically'

Then under my my router interface reserve it an ip address of 192.168.0.102

And this way it will have the same benefits of a static assigned device but also still be able to connect to public networks or tethered networks when its on the road.

 

Your the man Garycase!

 

:)

 

There may be one thing you have to do differently ==> I'm not sure if a reserved IP address can be "outside" of the range you've told it to assign IPs in (I'd THNK it can, but one never KNOWS without trying).    You may have to use an IP within the .02 to .100 range it's allowed to assign.    Depends on what your router allows.  I'd try the .102 you suggested, but if it won't accept that, just use something like 102.168.0.91

 

I run a script that adds a cronjob to check for internet access and restart the services if it is down, it would be the equivalent of the command posted by Joe L., just it would run by itself. I had to do this as a workaround for my network card dropping connection every once in a while. I can send you the script if the current solution doesn't solve your problem.