Re: [gentoo-user] Browsers cannot access WWW while ping and host utilities work as expected.

[Marc Joliet]

Am Mon, 5 Aug 2013 07:59:09 -0500
schrieb Bruce Hill <daddy@×××××××××××××××××××××.com>:

> On Mon, Aug 05, 2013 at 11:06:52AM +0100, Mick wrote:
> >
> > > Suggestions of  Michael Kintzios
> >
> > > > This is the new kernel naming scheme of NICs.  Which-ever nomenclature
> > > > you decide to use, check that that's the only one having a symlink in
> > > > /etc/init.d to net.lo
> > >
> > > Yes, there is only enp2s15 links to lo in /etc/init.d
> >
> > The idea here is that you need consistent naming of your iface.  If you have
> > settled on the kernel naming of enp2s15, then stick with this throughout your
> > configuration.
> > --
> > Regards,
> > Mick
>
> If this is "the new kernel naming scheme of NICs", why this in dmesg:
>
> [    4.725902] systemd-udevd[1176]: renamed network interface wlan0 to enp0s18f2u2
>
> It looks as if systemd-udev renamed the NIC to me. Can you explain?

It already has been explained in the previous NIC renaming discussion: what's
broken is renaming a device within the kernels internal namespace, which
contains eth*, wlan* (and maybe others). The problem is that there is a race
condition with the kernel when renaming ethX to ethY. What you *can* do is
rename ethX to somethingelseX or somethingelseY, because then you are not racing
against the kernel to hand out device names.

This is explained on the website that also explains the new default renaming
scheme used by udev. I (and IIRC others, too) already linked to it in in the old
thread, and the relevant news item also referenced it, but here it is again:

  http://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/

HTH
-- 
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup