LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Networking
User Name
Password
Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.

Notices

Reply
 
Search this Thread
Old 02-18-2013, 08:53 AM   #1
fkasmani
Member
 
Registered: Dec 2007
Posts: 176

Rep: Reputation: 17
Ubuntu server randomly looses LAN connection


Hello,

I have this remote Ubuntu 12.04 minimal headless server which I access and manage over reverse-SSH-tunnel (because it's behind a NAT firewall).

However, the issue I'm facing is, that randomly it cannot be accessed, whether remotely or over the LAN.
When I say random,at times it can go for days and at times it doesn't go for more than 24hrs.

At first I thought it was maybe a power-saving thing or maybe the UPS having a problem or maybe even a hardware issue with the server itself, so I asked a guy on-site to make some observations:

- Server is not powering off
- server is not going into power saving mode
- I asked the guy there to press the power button and the server nicely shut down and powered off, so it had not crashed or frozen
- Then he pressed the power button again and the server booted up, connected to the internet and I could immediately access it over reverse-SSH-tunnel

I suspected that it could be a random clash of IP number - maybe the IP number assigned could have been in use previously and maybe an issue.
I also suspected some hardware issue with the network card.
So I set a background continuous ping command

Code:
ping 173.194.47.23 -i 600 >> ping.txt &
The result was, that after 48hrs I got 140 lines of which the first 136 lines were responses and the remaining 4 lines we, "Destination Host Unreachable".
Seeing that I had set the ping interval to 600 and there are 140 files, I can see the command went on for about 23.5hrs
Here's the results of ping.txt:

Code:
PING 173.194.47.23 (173.194.47.23) 56(84) bytes of data.
    64 bytes from 173.194.47.23: icmp_req=1 ttl=52 time=236 ms
    64 bytes from 173.194.47.23: icmp_req=2 ttl=52 time=231 ms
    64 bytes from 173.194.47.23: icmp_req=3 ttl=52 time=226 ms
    64 bytes from 173.194.47.23: icmp_req=4 ttl=52 time=225 ms
    64 bytes from 173.194.47.23: icmp_req=5 ttl=52 time=227 ms
    64 bytes from 173.194.47.23: icmp_req=6 ttl=52 time=227 ms
    64 bytes from 173.194.47.23: icmp_req=7 ttl=52 time=232 ms
    64 bytes from 173.194.47.23: icmp_req=8 ttl=52 time=226 ms
    64 bytes from 173.194.47.23: icmp_req=9 ttl=52 time=232 ms
    64 bytes from 173.194.47.23: icmp_req=10 ttl=52 time=234 ms
    64 bytes from 173.194.47.23: icmp_req=11 ttl=52 time=223 ms
    64 bytes from 173.194.47.23: icmp_req=12 ttl=52 time=228 ms
    64 bytes from 173.194.47.23: icmp_req=13 ttl=52 time=226 ms
    64 bytes from 173.194.47.23: icmp_req=15 ttl=52 time=220 ms
    64 bytes from 173.194.47.23: icmp_req=16 ttl=52 time=226 ms
    64 bytes from 173.194.47.23: icmp_req=17 ttl=52 time=229 ms
    64 bytes from 173.194.47.23: icmp_req=18 ttl=52 time=236 ms
    64 bytes from 173.194.47.23: icmp_req=19 ttl=52 time=226 ms
    64 bytes from 173.194.47.23: icmp_req=20 ttl=52 time=235 ms
    64 bytes from 173.194.47.23: icmp_req=21 ttl=52 time=217 ms
    64 bytes from 173.194.47.23: icmp_req=22 ttl=52 time=219 ms
    64 bytes from 173.194.47.23: icmp_req=23 ttl=52 time=225 ms
    64 bytes from 173.194.47.23: icmp_req=24 ttl=52 time=220 ms
    64 bytes from 173.194.47.23: icmp_req=25 ttl=52 time=222 ms
    64 bytes from 173.194.47.23: icmp_req=26 ttl=52 time=218 ms
    64 bytes from 173.194.47.23: icmp_req=28 ttl=52 time=240 ms
    64 bytes from 173.194.47.23: icmp_req=29 ttl=52 time=224 ms
    64 bytes from 173.194.47.23: icmp_req=30 ttl=52 time=230 ms
    64 bytes from 173.194.47.23: icmp_req=31 ttl=52 time=221 ms
    64 bytes from 173.194.47.23: icmp_req=32 ttl=52 time=227 ms
    64 bytes from 173.194.47.23: icmp_req=34 ttl=52 time=224 ms
    64 bytes from 173.194.47.23: icmp_req=35 ttl=52 time=277 ms
    64 bytes from 173.194.47.23: icmp_req=36 ttl=52 time=223 ms
    64 bytes from 173.194.47.23: icmp_req=37 ttl=52 time=216 ms
    64 bytes from 173.194.47.23: icmp_req=38 ttl=52 time=226 ms
    64 bytes from 173.194.47.23: icmp_req=39 ttl=52 time=217 ms
    64 bytes from 173.194.47.23: icmp_req=40 ttl=52 time=225 ms
    64 bytes from 173.194.47.23: icmp_req=41 ttl=52 time=685 ms
    64 bytes from 173.194.47.23: icmp_req=42 ttl=52 time=226 ms
    64 bytes from 173.194.47.23: icmp_req=43 ttl=52 time=233 ms
    64 bytes from 173.194.47.23: icmp_req=44 ttl=52 time=223 ms
    64 bytes from 173.194.47.23: icmp_req=45 ttl=52 time=242 ms
    64 bytes from 173.194.47.23: icmp_req=46 ttl=52 time=239 ms
    64 bytes from 173.194.47.23: icmp_req=47 ttl=52 time=226 ms
    64 bytes from 173.194.47.23: icmp_req=48 ttl=52 time=229 ms
    64 bytes from 173.194.47.23: icmp_req=49 ttl=52 time=227 ms
    64 bytes from 173.194.47.23: icmp_req=50 ttl=52 time=226 ms
    64 bytes from 173.194.47.23: icmp_req=51 ttl=52 time=238 ms
    64 bytes from 173.194.47.23: icmp_req=52 ttl=52 time=223 ms
    64 bytes from 173.194.47.23: icmp_req=53 ttl=52 time=225 ms
    64 bytes from 173.194.47.23: icmp_req=54 ttl=52 time=226 ms
    64 bytes from 173.194.47.23: icmp_req=55 ttl=52 time=225 ms
    64 bytes from 173.194.47.23: icmp_req=57 ttl=52 time=233 ms
    64 bytes from 173.194.47.23: icmp_req=58 ttl=52 time=228 ms
    64 bytes from 173.194.47.23: icmp_req=59 ttl=52 time=229 ms
    64 bytes from 173.194.47.23: icmp_req=61 ttl=52 time=227 ms
    64 bytes from 173.194.47.23: icmp_req=62 ttl=52 time=221 ms
    64 bytes from 173.194.47.23: icmp_req=63 ttl=52 time=222 ms
    64 bytes from 173.194.47.23: icmp_req=64 ttl=52 time=226 ms
    64 bytes from 173.194.47.23: icmp_req=65 ttl=52 time=226 ms
    64 bytes from 173.194.47.23: icmp_req=66 ttl=52 time=218 ms
    64 bytes from 173.194.47.23: icmp_req=67 ttl=52 time=208 ms
    64 bytes from 173.194.47.23: icmp_req=68 ttl=52 time=220 ms
    64 bytes from 173.194.47.23: icmp_req=69 ttl=52 time=216 ms
    64 bytes from 173.194.47.23: icmp_req=70 ttl=52 time=204 ms
    64 bytes from 173.194.47.23: icmp_req=71 ttl=52 time=205 ms
    64 bytes from 173.194.47.23: icmp_req=72 ttl=52 time=221 ms
    64 bytes from 173.194.47.23: icmp_req=73 ttl=52 time=205 ms
    64 bytes from 173.194.47.23: icmp_req=74 ttl=52 time=209 ms
    64 bytes from 173.194.47.23: icmp_req=75 ttl=52 time=207 ms
    64 bytes from 173.194.47.23: icmp_req=76 ttl=52 time=214 ms
    64 bytes from 173.194.47.23: icmp_req=77 ttl=52 time=205 ms
    64 bytes from 173.194.47.23: icmp_req=78 ttl=52 time=204 ms
    64 bytes from 173.194.47.23: icmp_req=79 ttl=52 time=205 ms
    64 bytes from 173.194.47.23: icmp_req=80 ttl=52 time=204 ms
    64 bytes from 173.194.47.23: icmp_req=81 ttl=52 time=213 ms
    64 bytes from 173.194.47.23: icmp_req=82 ttl=52 time=205 ms
    64 bytes from 173.194.47.23: icmp_req=83 ttl=52 time=203 ms
    64 bytes from 173.194.47.23: icmp_req=84 ttl=52 time=206 ms
    64 bytes from 173.194.47.23: icmp_req=85 ttl=52 time=204 ms
    64 bytes from 173.194.47.23: icmp_req=86 ttl=52 time=206 ms
    64 bytes from 173.194.47.23: icmp_req=87 ttl=52 time=206 ms
    64 bytes from 173.194.47.23: icmp_req=88 ttl=52 time=205 ms
    64 bytes from 173.194.47.23: icmp_req=89 ttl=52 time=206 ms
    64 bytes from 173.194.47.23: icmp_req=90 ttl=52 time=203 ms
    64 bytes from 173.194.47.23: icmp_req=91 ttl=52 time=206 ms
    64 bytes from 173.194.47.23: icmp_req=92 ttl=52 time=212 ms
    64 bytes from 173.194.47.23: icmp_req=93 ttl=52 time=204 ms
    64 bytes from 173.194.47.23: icmp_req=94 ttl=52 time=207 ms
    64 bytes from 173.194.47.23: icmp_req=95 ttl=52 time=206 ms
    64 bytes from 173.194.47.23: icmp_req=96 ttl=52 time=205 ms
    64 bytes from 173.194.47.23: icmp_req=97 ttl=52 time=205 ms
    64 bytes from 173.194.47.23: icmp_req=98 ttl=52 time=206 ms
    64 bytes from 173.194.47.23: icmp_req=99 ttl=52 time=204 ms
    64 bytes from 173.194.47.23: icmp_req=100 ttl=52 time=205 ms
    64 bytes from 173.194.47.23: icmp_req=101 ttl=52 time=205 ms
    64 bytes from 173.194.47.23: icmp_req=102 ttl=52 time=205 ms
    64 bytes from 173.194.47.23: icmp_req=103 ttl=52 time=204 ms
    64 bytes from 173.194.47.23: icmp_req=104 ttl=52 time=204 ms
    64 bytes from 173.194.47.23: icmp_req=105 ttl=52 time=205 ms
    64 bytes from 173.194.47.23: icmp_req=106 ttl=52 time=206 ms
    64 bytes from 173.194.47.23: icmp_req=107 ttl=52 time=216 ms
    64 bytes from 173.194.47.23: icmp_req=108 ttl=52 time=227 ms
    64 bytes from 173.194.47.23: icmp_req=109 ttl=52 time=221 ms
    64 bytes from 173.194.47.23: icmp_req=110 ttl=52 time=224 ms
    64 bytes from 173.194.47.23: icmp_req=111 ttl=52 time=224 ms
    64 bytes from 173.194.47.23: icmp_req=112 ttl=52 time=226 ms
    64 bytes from 173.194.47.23: icmp_req=113 ttl=52 time=212 ms
    64 bytes from 173.194.47.23: icmp_req=114 ttl=52 time=218 ms
    64 bytes from 173.194.47.23: icmp_req=115 ttl=52 time=208 ms
    64 bytes from 173.194.47.23: icmp_req=116 ttl=52 time=209 ms
    64 bytes from 173.194.47.23: icmp_req=117 ttl=52 time=211 ms
    64 bytes from 173.194.47.23: icmp_req=118 ttl=52 time=210 ms
    64 bytes from 173.194.47.23: icmp_req=119 ttl=52 time=215 ms
    64 bytes from 173.194.47.23: icmp_req=120 ttl=52 time=227 ms
    64 bytes from 173.194.47.23: icmp_req=121 ttl=52 time=229 ms
    64 bytes from 173.194.47.23: icmp_req=122 ttl=52 time=222 ms
    64 bytes from 173.194.47.23: icmp_req=123 ttl=52 time=237 ms
    64 bytes from 173.194.47.23: icmp_req=124 ttl=52 time=223 ms
    64 bytes from 173.194.47.23: icmp_req=125 ttl=52 time=224 ms
    64 bytes from 173.194.47.23: icmp_req=126 ttl=52 time=219 ms
    64 bytes from 173.194.47.23: icmp_req=127 ttl=52 time=223 ms
    64 bytes from 173.194.47.23: icmp_req=128 ttl=52 time=223 ms
    64 bytes from 173.194.47.23: icmp_req=129 ttl=52 time=225 ms
    64 bytes from 173.194.47.23: icmp_req=130 ttl=52 time=242 ms
    64 bytes from 173.194.47.23: icmp_req=131 ttl=52 time=240 ms
    64 bytes from 173.194.47.23: icmp_req=132 ttl=52 time=246 ms
    64 bytes from 173.194.47.23: icmp_req=133 ttl=52 time=235 ms
    64 bytes from 173.194.47.23: icmp_req=134 ttl=52 time=231 ms
    64 bytes from 173.194.47.23: icmp_req=135 ttl=52 time=229 ms
    64 bytes from 173.194.47.23: icmp_req=136 ttl=52 time=223 ms
    From 192.168.0.10 icmp_seq=137 Destination Host Unreachable
    From 192.168.0.10 icmp_seq=138 Destination Host Unreachable
    From 192.168.0.10 icmp_seq=139 Destination Host Unreachable
    From 192.168.0.10 icmp_seq=140 Destination Host Unreachable
The funny thing is, why did the pinging stop after 4 unreachables? The server remained ON; it had not crashed; it had not gone into sleep mode.

All other machines on the LAN are Windows based and there's not tech-guys on-site.

Any help and suggestions on how to handle and fault-find this, would be highly appreciated.
 
Old 02-19-2013, 03:07 AM   #2
pintooo15
Member
 
Registered: May 2004
Location: on the interwebz
Distribution: linux mint 13/sled 11 sp2
Posts: 72

Rep: Reputation: 21
what steps do you take after this point, where the ping.txt stops updating, to get the connectivity back? does the ping process also get killed? Besides possible hardware issues, I wonder if some firewall rules are eagerly labelling moderate usage as signs of DoS and blocking or turning off services and/or dropping off connections.
 
1 members found this post helpful.
Old 02-21-2013, 11:03 AM   #3
fkasmani
Member
 
Registered: Dec 2007
Posts: 176

Original Poster
Rep: Reputation: 17
Quote:
Originally Posted by pintooo15 View Post
what steps do you take after this point, where the ping.txt stops updating, to get the connectivity back?
All that can be done is to reboot the server.
Quote:
Originally Posted by pintooo15 View Post
does the ping process also get killed?
Looks like. 'Cos it shows 4 "Destination host unreachable" and nothing more, even though the server was powered up much longer and when attended to(about more than 48hrs later), the followng observations were made:
  • Server power indicator was ON and not blinking (so it was not in any power saving mode)
  • Someone on-site just gave a single-touch to the power botton and the server shut-down (he did not have to keep the power button pressed) which means the server and OS were alive and had not crashed.
  • In every such "unreachable" scenarion, the server is just rebooted and can then be accessed fom the LAN as normal
Quote:
Originally Posted by pintooo15 View Post
Besides possible hardware issues, I wonder if some firewall rules are eagerly labelling moderate usage as signs of DoS and blocking or turning off services and/or dropping off connections.
There's no firewall.

Calculating, it works out the last process in the ping took place at about 14:02 (17th Feb), so I looked for a syslog file in /var/log and in there at about 14:02 is:
Code:
Feb 17 14:02:47 dhclient: last message repeated 4 times
However,way back at about 13:29, issues seem to have started as autossh has been unable to connect.But I still can't figure out where the problem lies;I am however getting a feeling that it's to do with renewing the IP number? I've uploaded a portion of the syslog.1 file which I feel links to the problem. Here's the link.
 
Old 02-21-2013, 01:09 PM   #4
pintooo15
Member
 
Registered: May 2004
Location: on the interwebz
Distribution: linux mint 13/sled 11 sp2
Posts: 72

Rep: Reputation: 21
Pastebin the log txt file please. pastebin.ca is a good option. only suggesting.

If it is possible to attach a console/screen to the server box, you will have more options to diagnose the connectivity situation. First thing is you would take a look at /var/log/* to grep for stuff like "disconnected" or "dropped" or "rejected" or something in conjuntion with NetworkManager or pppd or whatever process manages the network connection. I won't care about specific services like ssh because even your ping fails. My intention is to just find a way to 1. get a time of the network going down and observing what (if any) other relevant processes might have logged that time. and 2. isolate the issue as either a software (some process dying or just tired of your networking load), hardware (network card) or firewall (NAT firewall) issue.

The dhclient line "last message repeated 4 times" refers to the line above it, which was repeated four times. Do paste that here. If it's a server, why is it's IP renewing and why is there a DHCP client running?
 
2 members found this post helpful.
Old 03-04-2013, 08:21 AM   #5
fkasmani
Member
 
Registered: Dec 2007
Posts: 176

Original Poster
Rep: Reputation: 17
Quote:
Originally Posted by pintooo15 View Post
Pastebin the log txt file please. pastebin.ca is a good option. only suggesting.
Thanks Pintooo15.

I had to delay my reply here, 'cos I ran another continuous ping command - this time logging date and time as well and was thus waiting for it to go down.

Well, it ran for a few days and then went down again, so I feel we're now in a better position as we can actually match the ping results to the logs.
I've done some pastebin's for the ping results as well as some files I found in the /var/log/ that happened to match the time to the ping results:
Ping Results: http://pastebin.com/Q1SDHk0j
dmesg.o http://pastebin.com/qkAwqzdy
Syslog.7 http://pastebin.com/i7YPEi2t

There was also a 'wtmp.1' file which matched the time of the failing ping, but was unable to pastebin it so it's available at:
http://www.fileconvoy.com/dfl.php?id...e460f6b4ed106d

Quote:
Originally Posted by pintooo15 View Post
If it is possible to attach a console/screen to the server box, you will have more options to diagnose the connectivity situation. First thing is you would take a look at /var/log/* to grep for stuff like "disconnected" or "dropped" or "rejected" or something in conjuntion with NetworkManager or pppd or whatever process manages the network connection. I won't care about specific services like ssh because even your ping fails. My intention is to just find a way to 1. get a time of the network going down and observing what (if any) other relevant processes might have logged that time. and 2. isolate the issue as either a software (some process dying or just tired of your networking load), hardware (network card) or firewall (NAT firewall) issue.
The server is a headless on and is in a different city with no tech guy around so attaching a screen to it could pose problems.
I do however have full SSH access to it with Webmin and Nagios3 installed (if these could be of help).

Quote:
Originally Posted by pintooo15 View Post
The dhclient line "last message repeated 4 times" refers to the line above it, which was repeated four times. Do paste that here.
Code:
Feb 25 23:56:19 openemr dhclient: DHCPREQUEST of 192.168.0.10 on eth0 to 192.168.0.1 port 67
Quote:
Originally Posted by pintooo15 View Post
If it's a server, why is it's IP renewing and why is there a DHCP client running?
Isn't the IP renewing 'cos it's connected to a DHCP router?
When installing Ubuntu 12.04 minimal, I just did the default installation and did not select DHCP client as a service or anything.
 
Old 03-09-2013, 03:05 AM   #6
catworld
Member
 
Registered: Nov 2004
Location: Horseheads, New York
Distribution: Mandriva 2010.1 / KDE 4.5.2, Slax, Knoppix, Backtrack & etc...
Posts: 198

Rep: Reputation: 36
Your server must be behind a firewall of sorts, if you get an IP address dynamically from the service provider. Does the IP of the server ever change?

BTW what's up with the two networks? Your ping returns 173.194... then gets an icmp alert from a 192.168.0.10 address? It looks like the 173... is the external IP of the internet facing router you are behind, and perhaps the 192.168.0.10 is the IP of your server's interface. Where did you get the 173... number from? Does this server have a routable host name? If so, does pinging it by name resolve to the 173.194.x.x address?

Your problem might be something the service provider is doing. They no doubt have to deal with a lot of mayhem coming off the internet. It would help us if we knew what services this server is presenting to the outside world.
 
1 members found this post helpful.
Old 03-10-2013, 01:58 AM   #7
fkasmani
Member
 
Registered: Dec 2007
Posts: 176

Original Poster
Rep: Reputation: 17
Thanks Catworld.
Quote:
Originally Posted by catworld View Post
Your server must be behind a firewall of sorts, if you get an IP address dynamically from the service provider. Does the IP of the server ever change?
Well, I've actually asked for a topology of the network and will post it here, but in the meantime: Yes the whole network is behind the IPS's NAT Firewall. Once in, there's a LAN in which this server sits. The server itself is set to DHCP and there must be some DLink or Linksys router managing this LAN (and providing local 192.168.0.xxx IP#'s). As for the ISP providing IP#'s - they provide dynamic IP's and we have no control over this.

Quote:
Originally Posted by catworld View Post
BTW what's up with the two networks? Your ping returns 173.194... then gets an icmp alert from a 192.168.0.10 address? It looks like the 173... is the external IP of the internet facing router you are behind, and perhaps the 192.168.0.10 is the IP of your server's interface. Where did you get the 173... number from? Does this server have a routable host name? If so, does pinging it by name resolve to the 173.194.x.x address?
The 173.194... comes from the ping result, doesn't it? (I was pinging to 173.194...) and 192.168.0.10 is the IP# of the server itself.

Quote:
Originally Posted by catworld View Post
Your problem might be something the service provider is doing. They no doubt have to deal with a lot of mayhem coming off the internet. It would help us if we knew what services this server is presenting to the outside world.
The server does not provide any services to the outside world. It's housing an Electronic Medical Records database app built around Apache, PHP, MySQL; so those on the LAN wanting to access this app just point their web browser to http://192.168.0.10/openemr
It's only connection to the outside world is for me to be able to login over reverse-ssh-tunnel and provide support & updates (there's also Nagios & Webmin installed on it).
However, when the server is unreachable, not only me but all those on it's LAN too cannot access it - yet as previously mentioned, it's powered up and not in sleep mode or anything.
 
Old 03-10-2013, 03:25 AM   #8
nimnull22
Senior Member
 
Registered: Jul 2009
Distribution: OpenSuse 11.1, Fedora 14, Ubuntu 12.04/12.10, FreeBSD 9.0
Posts: 1,571

Rep: Reputation: 92
In your Syslog.7:
Feb 25 23:26:37 openemr dhclient: DHCPREQUEST of 192.168.0.10 on eth0 to 192.168.0.1 port 67
Feb 25 23:26:38 openemr dhclient: DHCPACK of 192.168.0.10 from 192.168.0.1
Feb 25 23:26:38 openemr dhclient: bound to 192.168.0.10 -- renewal in 1598 seconds.

This is normal. But in the local network I would suggest to use static IP. But anyway - this is normal behavior.
Next after 1598 seconds:
Feb 25 23:53:16 openemr dhclient: DHCPREQUEST of 192.168.0.10 on eth0 to 192.168.0.1 port 67
Feb 25 23:53:32 openemr dhclient: DHCPREQUEST of 192.168.0.10 on eth0 to 192.168.0.1 port 67
Feb 25 23:53:42 openemr dhclient: DHCPREQUEST of 192.168.0.10 on eth0 to 192.168.0.1 port 67
Feb 25 23:53:57 openemr dhclient: DHCPREQUEST of 192.168.0.10 on eth0 to 192.168.0.1 port 67
Feb 25 23:54:15 openemr dhclient: DHCPREQUEST of 192.168.0.10 on eth0 to 192.168.0.1 port 67
Feb 25 23:54:57 dhclient: last message repeated 3 times
Feb 25 23:55:18 openemr dhclient: DHCPREQUEST of 192.168.0.10 on eth0 to 192.168.0.1 port 67
....Feb 26 00:26:39 openemr postfix/master[1208]: reload -- version 2.9.3, configuration /etc/postfix

Feb 26 00:26:39 openemr dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Feb 26 00:26:42 openemr dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Feb 26 00:26:49 openemr dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Feb 26 00:26:56 openemr dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
Feb 26 00:27:11 openemr dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 16
Feb 26 00:27:27 openemr dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20
Feb 26 00:27:47 openemr dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 13
Feb 26 00:27:50 openemr nagios3: Auto-save of retention data completed successfully.
Feb 26 00:28:00 openemr dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
Feb 26 00:28:18 openemr dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
Feb 26 00:28:33 openemr dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 12
Feb 26 00:28:45 openemr dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
Feb 26 00:29:03 openemr dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 20
Feb 26 00:29:23 openemr dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
Feb 26 00:29:30 openemr dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 14
Feb 26 00:29:44 openemr dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
Feb 26 00:29:53 openemr dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 19


Your dhcp server doesn't work properly.
And ones again - for the local network interface use static IP.

Last edited by nimnull22; 03-10-2013 at 08:43 AM.
 
1 members found this post helpful.
Old 03-10-2013, 08:24 AM   #9
catworld
Member
 
Registered: Nov 2004
Location: Horseheads, New York
Distribution: Mandriva 2010.1 / KDE 4.5.2, Slax, Knoppix, Backtrack & etc...
Posts: 198

Rep: Reputation: 36
Using static might be the answer, but then the ISPs routing or arp tables might potentially lose the server, no?

If the ultimate problem is the DHCP server it would be the ISPs problem... maybe. I'd ask them how they run the DHCP service. Maybe there's some minute incompatibility in the stack between the ISP and your distro's implementation.
 
Old 03-10-2013, 08:42 AM   #10
nimnull22
Senior Member
 
Registered: Jul 2009
Distribution: OpenSuse 11.1, Fedora 14, Ubuntu 12.04/12.10, FreeBSD 9.0
Posts: 1,571

Rep: Reputation: 92
His server uses 192.168.0.10 - those are LAN IPs and don't have any relation to ISP IPs. All OP needs to do is to make DHCP address pool higher then 192.168.0.10, so 192.168.0.2-10 can be used for static.

This is what I think.
 
1 members found this post helpful.
Old 03-10-2013, 09:15 AM   #11
catworld
Member
 
Registered: Nov 2004
Location: Horseheads, New York
Distribution: Mandriva 2010.1 / KDE 4.5.2, Slax, Knoppix, Backtrack & etc...
Posts: 198

Rep: Reputation: 36
Is the OP running the dhcp server? I thought the ISP is the one handing out addresses, and the OP has no access to dhcp configs.
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Cannot connect over LAN to ssh server or SMB, also it randomly disconnects from wifi Lumify Linux - Software 2 08-22-2012 01:20 PM
Slow ssh connection over lan with Ubuntu Desktop and Ubuntu Server Recursion Linux - Networking 1 05-23-2009 02:17 AM
modem looses lan rblampain Linux - Hardware 2 06-26-2007 11:59 PM
Knoppix looses internet connection sosh Debian 9 12-09-2003 11:05 AM
Wu-ftpd looses connection? Sir.Del Linux - General 0 12-20-2001 07:21 PM


All times are GMT -5. The time now is 04:54 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration