| 1 |
Am Tue, 21 Mar 2017 11:08:49 -0600 |
| 2 |
schrieb thelma@×××××××××××.com: |
| 3 |
|
| 4 |
> On 03/21/2017 10:21 AM, Ian Zimmerman wrote: |
| 5 |
> > On 2017-03-21 06:59, thelma@×××××××××××.com wrote: |
| 6 |
> > |
| 7 |
> >> Sometimes it does, the IP stays for a several days but sometimes it |
| 8 |
> >> boots with correct IP and the IP changes after few hours to |
| 9 |
> >> something like 192.168.xxx (which is not what my firewall |
| 10 |
> >> provides.) |
| 11 |
> > |
| 12 |
> > Maybe you have another (misconfigured) DHCP server on the network? |
| 13 |
> > tcpdump could be your friend. |
| 14 |
> |
| 15 |
> The only strange entries I see in message logs are: |
| 16 |
> |
| 17 |
> eden dbus[3276]: [system] Activating service |
| 18 |
> name='org.freedesktop.UDisks2' (using servicehelper) eden |
| 19 |
> udisksd[4067]: udisks daemon version 2.1.8 starting eden dbus[3276]: |
| 20 |
> [system] Successfully activated service 'org.freedesktop.UDisks2' |
| 21 |
> eden udisksd[4067]: Acquired the name org.freedesktop.UDisks2 on the |
| 22 |
> system message bus eden apcupsd[2864]: Communications with UPS lost. |
| 23 |
> eden postfix/pickup[3665]: 2BC8520064: uid=0 |
| 24 |
> from=<root@××××.localdomain> eden postfix/cleanup[4174]: 2BC8520064: |
| 25 |
> message-id=<20170321045940.2BC8520064@××××.localdomain> eden |
| 26 |
> postfix/qmgr[3666]: 2BC8520064: from=<root@××××.localdomain>, |
| 27 |
> size=924, nrcpt=1 (queue active) eden postfix/cleanup[4174]: |
| 28 |
> 7C18420023: message-id=<20170321045940.2BC8520064@××××.localdomain> |
| 29 |
> eden postfix/qmgr[3666]: 7C18420023: from=<root@××××.localdomain>, |
| 30 |
> size=1057, nrcpt=1 (queue active) eden postfix/local[4180]: |
| 31 |
> 2BC8520064: to=<root@××××.localdomain>, relay=local, delay=0.59, |
| 32 |
> delays=0.32/0.21/0/0.05, dsn=2.0.0, status=sent (forwarded as |
| 33 |
> 7C18420023) eden postfix/qmgr[3666]: 2BC8520064: removed eden |
| 34 |
> postfix/smtp[4184]: 7C18420023: to=<thelma@×××××××××××.com>, |
| 35 |
> orig_to=<root@××××.localdomain>, relay=none, delay=0.13, |
| 36 |
> delays=0.05/0.08/0/0, dsn=4.4.3, status=deferred (Host or domain name |
| 37 |
> not found. Name service error for name=mail.sys-concept.com type=MX: |
| 38 |
> Host not found, try again) |
| 39 |
|
| 40 |
What's strange about these logs? |
| 41 |
|
| 42 |
> This must be from "apcupsd" |
| 43 |
> Could this service causes some problem with my network? |
| 44 |
|
| 45 |
That service is only victim of the IP address changing. It's not the |
| 46 |
source of the problem. |
| 47 |
|
| 48 |
> Shortly after I could not receive any message from the system, I |
| 49 |
> think the network connection got lost. -- |
| 50 |
|
| 51 |
You wrote that this happened in different locations, I guess you mean |
| 52 |
different networked sites with each their own DHCP server. |
| 53 |
|
| 54 |
So, I my best guess is that you're running a local DHCP server by |
| 55 |
accident. |
| 56 |
|
| 57 |
Which service does configure your network? |
| 58 |
|
| 59 |
If it's systemd-networkd, you could check those logs after the problem |
| 60 |
occurred: |
| 61 |
|
| 62 |
# journalctl -b -u systemd-networkd.service | fgrep -i dhcpv4 |
| 63 |
|
| 64 |
Apparently, it doesn't tell you what the DHCP server is by MAC address, |
| 65 |
but the reported "via" at least tells you the IP. |
| 66 |
|
| 67 |
It looks like this: |
| 68 |
|
| 69 |
Mar 17 19:21:33 jupiter systemd-networkd[680]: enp5s0: DHCPv4 address 192.168.4.102/24 via 192.168.4.254 |
| 70 |
|
| 71 |
Other network management daemons should log similar lines. Try first |
| 72 |
without fgrep. |
| 73 |
|
| 74 |
|
| 75 |
-- |
| 76 |
Regards, |
| 77 |
Kai |
| 78 |
|
| 79 |
Replies to list-only preferred. |
Archives