[gentoo-user] Re: losing network IP address

[Kai Krakow]

Am Tue, 21 Mar 2017 15:05:53 -0600
schrieb thelma@×××××××××××.com:

> Thelma
> On 03/21/2017 01:25 PM, Kai Krakow wrote:
> > Am Tue, 21 Mar 2017 11:08:49 -0600
> > schrieb thelma@×××××××××××.com:
> >
> >> On 03/21/2017 10:21 AM, Ian Zimmerman wrote:
>  [...]
>  [...]
>  [...]
> >>
> >> The only strange entries I see in message logs are:
> >>
> >>  eden dbus[3276]: [system] Activating service
> >> name='org.freedesktop.UDisks2' (using servicehelper) eden
> >> udisksd[4067]: udisks daemon version 2.1.8 starting eden
> >> dbus[3276]: [system] Successfully activated service
> >> 'org.freedesktop.UDisks2' eden udisksd[4067]: Acquired the name
> >> org.freedesktop.UDisks2 on the system message bus eden
> >> apcupsd[2864]: Communications with UPS lost. eden
> >> postfix/pickup[3665]: 2BC8520064: uid=0
> >> from=<root@××××.localdomain> eden postfix/cleanup[4174]:
> >> 2BC8520064:
> >> message-id=<20170321045940.2BC8520064@××××.localdomain> eden
> >> postfix/qmgr[3666]: 2BC8520064: from=<root@××××.localdomain>,
> >> size=924, nrcpt=1 (queue active) eden postfix/cleanup[4174]:
> >> 7C18420023:
> >> message-id=<20170321045940.2BC8520064@××××.localdomain> eden
> >> postfix/qmgr[3666]: 7C18420023: from=<root@××××.localdomain>,
> >> size=1057, nrcpt=1 (queue active) eden postfix/local[4180]:
> >> 2BC8520064: to=<root@××××.localdomain>, relay=local, delay=0.59,
> >> delays=0.32/0.21/0/0.05, dsn=2.0.0, status=sent (forwarded as
> >> 7C18420023) eden postfix/qmgr[3666]: 2BC8520064: removed eden
> >> postfix/smtp[4184]: 7C18420023: to=<thelma@×××××××××××.com>,
> >> orig_to=<root@××××.localdomain>, relay=none, delay=0.13,
> >> delays=0.05/0.08/0/0, dsn=4.4.3, status=deferred (Host or domain
> >> name not found. Name service error for name=mail.sys-concept.com
> >> type=MX: Host not found, try again)
> >
> > What's strange about these logs?
> >
> >> This must be from "apcupsd"
> >> Could this service causes some problem with my network?
> >
> > That service is only victim of the IP address changing. It's not the
> > source of the problem.
> >
> >> Shortly after I could not receive any message from the system, I
> >> think the network connection got lost. --
> >
> > You wrote that this happened in different locations, I guess you
> > mean different networked sites with each their own DHCP server.
> >
> > So, I my best guess is that you're running a local DHCP server by
> > accident.
> >
> > Which service does configure your network?
> >
> > If it's systemd-networkd, you could check those logs after the
> > problem occurred:
> >
> > # journalctl -b -u systemd-networkd.service | fgrep -i dhcpv4
> >
> > Apparently, it doesn't tell you what the DHCP server is by MAC
> > address, but the reported "via" at least tells you the IP.
> >
> > It looks like this:
> >
> > Mar 17 19:21:33 jupiter systemd-networkd[680]: enp5s0: DHCPv4
> > address 192.168.4.102/24 via 192.168.4.254
> >
> > Other network management daemons should log similar lines. Try first
> > without fgrep.
>
> I run DHCP on my DD-WRT router, and all the boxes are running OK,
> except this one. The IP the box suppose to get is: 10.10.0.7 (static
> IP ) and here is an entry from last night long:

Maybe try OpenWRT instead, it's more active developed. I ditched DD-WRT
a long time ago due to unsolved stability issues. There's also LEDE but
it was a bit to experimental to me, having some grave bugs that
couldn't be resolved without installing from scratch on an older
version.

Then, I'm confused. What is "this box"? I suppose, it's not the router?

>  eden dhcpcd[7478]: net0: adding address fe80::a98a:8875:2106:64bc
>  eden dhcpcd[7478]: DUID 00:01:00:01:1a:bc:bc:ca:00:30:18:ad:ed:b4
>  eden dhcpcd[7478]: net0: IAID 18:ad:ed:b4
>  eden dhcpcd[7478]: net0: soliciting an IPv6 router
>  eden dhcpcd[7478]: net0: soliciting a DHCP lease
>  eden dhcpcd[7478]: net0: probing for an IPv4LL address
>  eden dhcpcd[7478]: net0: using IPv4LL address 169.254.156.68
>  eden dhcpcd[7478]: net0: adding route to 169.254.0.0/16

Please disable IPv4LL - I don't think you need that. It's likely that's
getting in the way with routing for you.

> I could suspect the cable but I use two different cable in two
> different location on same network and same thing happens.

So actually you already ruled the cable out. Maybe the connector?

> I took
> that box home and it hang up on me in the morning.

You mean it froze? Which is now "the box"? Your PC? The router?

> I've already
> ordered a replacement.  The only reason I was sticking to it as it is
> already configured for my hylafax, asterisk.

If "the box" is the router, I cannot follow what you write. If you use
your PC in different locations, I'd expect "the box" aka the router to
stay in place. So your particular problem may not be restricted to the
router (despite that being maybe part of your problem due to
instability).

-- 
Regards,
Kai

Replies to list-only preferred.