On Mon, Jul 12, 2021 at 02:32:12PM +0200, Michael Lange wrote:
> Hi,
>
> On Mon, 12 Jul 2021 13:16:13 +0200
> wrote:
>
> (...)
> > Your network clearly *thinks* it is up [...]
> well, as you may have guessed I am completely stupid when it comes to
> networking :)
Most of us are. I know I am.
Hi,
On Mon, 12 Jul 2021 13:16:13 +0200
wrote:
(...)
> Your network clearly *thinks* it is up. What makes you think your net
> doesn't work? (not that I'm doubting your perception, but a more precise
> symptom description might shed some light on the problem).
well, as you may have guessed I am
On Mon, Jul 12, 2021 at 01:00:08PM +0200, Michael Lange wrote:
> Does that tell something?
Yep. First, your interface name is "enp2s0" has not changed.
Second, someone (another instance of dhclient probably) have obtained a
lease, as indicated by both tcpdump and "ip a" outputs.
Reco
On Mon, Jul 12, 2021 at 01:00:08PM +0200, Michael Lange wrote:
[...]
> 2: enp2s0: mtu 1500 qdisc pfifo_fast state
> UP group default qlen 1000
> link/ether 50:e5:49:d8:51:94 brd ff:ff:ff:ff:ff:ff
> inet 192.168.178.27/24 brd 192.168.178.255 scope global dynamic enp2s0
>valid_lft
Hi,
On Mon, 12 Jul 2021 13:32:48 +0300
Reco wrote:
(...)
> does not add up.
>
> If, for some reason, an interface name had changed - you won't see
> "enp2s0" in the ifconfig output.
thanks for the clarification.
>
>
> > some sources I found suggest to look at
> > /etc/udev/rules.d/70-persist
Hi.
On Mon, Jul 12, 2021 at 12:16:59PM +0200, Michael Lange wrote:
This:
> With ifconfig the enp2s0 interface appears to be up,
combined with this:
> I suspected udev to have for some reason changed the interface name;
does not add up.
If, for some reason, an interface name had changed
6 matches
Mail list logo
