Re: [gentoo-user] Re: losing network IP address

On 03/21/2017 03:17 PM, Kai Krakow wrote:
> 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:
>>>>
[snip]
>>> 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.

How to disable it? In a router or in /etc/init.d
config_net0="dhcp -IPv4LL"  ???

>
>> 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?

Well, not likely the connector; as I use two different cables.
Restarting the net0 gave me incorrect IP.  But I agree it might be the
connection.  However, I connected another small box Atom to the same
cable and it obtained correct IP on first boot.

This box "eden" I was watching booting, it got correct IP on boot but
soon after 5-min later the IP changed "dropped" to 169.254.156.68

>> 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?

Yes, I had to pull the plug on (the box-PC (not the router)) the power
supply, it wasn't responding at all.

My routers, in remote location is a Linksys, at home Asus.

The box in question is:
VIA Eden Processor 1200MHz
1024 MB Ram

>
>> 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).

My routers are working OK, it was only this "eden" small PC.
The problem is, it is happening random so I can not duplicate the IP drop.

--
Thelma