public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marc Joliet <marcec@gmx.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Browsers cannot access WWW while ping and host utilities work as expected.
Date: Mon, 5 Aug 2013 16:31:44 +0200	[thread overview]
Message-ID: <20130805163144.69653f43@marcec> (raw)
In-Reply-To: <20130805125909.GL25510@server>

[-- Attachment #1: Type: text/plain, Size: 1827 bytes --]

Am Mon, 5 Aug 2013 07:59:09 -0500
schrieb Bruce Hill <daddy@happypenguincomputers.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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2013-08-05 14:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-04 18:56 [gentoo-user] Browsers cannot access WWW while ping and host utilities work as expected gevisz
2013-08-04 19:21 ` Mark Pariente
2013-08-04 19:57 ` Mick
2013-08-04 20:10   ` Kurian Thayil
2013-08-05  6:06   ` gevisz
2013-08-05 10:06     ` Mick
2013-08-05 12:59       ` Bruce Hill
2013-08-05 14:31         ` Marc Joliet [this message]
2013-08-05 14:41           ` Bruce Hill
2013-08-05 15:21             ` Marc Joliet
2013-08-05 15:37             ` Mick
2013-08-05 16:43             ` Stroller
2013-08-05 17:28             ` Alan McKinnon
2013-08-06 22:57               ` Stroller
2013-08-12  7:13       ` gevisz
2013-08-12  9:10         ` Alan McKinnon
2013-08-13  6:31           ` gevisz
2013-08-13  7:05             ` Alan McKinnon
2013-08-05 18:37   ` [gentoo-user] " Grant Edwards

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130805163144.69653f43@marcec \
    --to=marcec@gmx.de \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox