public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kerin Millar <kerframil@fastmail.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Ethernet Machination
Date: Sat, 05 Jan 2013 16:03:10 +0000	[thread overview]
Message-ID: <50E84EBE.1050007@fastmail.co.uk> (raw)
In-Reply-To: <loom.20130102T214951-919@post.gmane.org>

james wrote:
> After deleting the 70-persistent-net.rule file
>
> udev does not re-create it. All is now fine with rc-status
> only showing net.eth0 which is set up how I like it
> per /etc/conf.d/net. All services are fine

Beware. The automatic persistent net rules generator is intrinsically 
broken because naming eth* devices within the same namespace (eth* to 
eth*) can break things horribly. I have had this happen to me on several 
occasions and was helping someone out in #gentoo who had experienced the 
same issue only recently.

For more information, take a look at this bug:

   https://bugzilla.redhat.com/show_bug.cgi?id=782145

Because of this, Kay Sievers has removed the rule generator from later 
versions of udev (*). The current version of udev marked stable in 
gentoo still has it but it can be disabled by setting 
USE="-rule_generator". I've started doing exactly that on my systems 
because it has only ever caused problems instead of providing solutions. 
Besides which, eventually a version of udev will be stabilized that no 
longer has it.

If you want to use persistent net rules, the only safe way of doing it 
is to define the rules manually and to rename interfaces in such a 
fashion that they don't conflict with the existing device namespace. For 
example, you could rename "eth0" to "lan", "eth1" to "dmz" or whatever 
is deemed appropriate.

This doesn't appear to be common knowledge, so it struck me as worth 
mentioning.

Cheers,

--Kerin

* I cannot recall the exact version off-hand.


  parent reply	other threads:[~2013-01-05 16:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-02  0:50 [gentoo-user] Ethernet Machination James
2013-01-02  0:55 ` Canek Peláez Valdés
2013-01-02 12:53   ` Tanstaafl
2013-01-02 15:24     ` Michael Mol
2013-01-02 15:35       ` Tanstaafl
2013-01-02 15:47         ` Michael Mol
2013-01-02  0:56 ` Mark Knecht
2013-01-02 20:57   ` [gentoo-user] " james
2013-01-02 21:03     ` Bruce Hill
2013-01-02 21:12     ` Mark Knecht
2013-01-02 21:18     ` Todd Goodman
2013-01-02 22:04     ` Canek Peláez Valdés
2013-01-02 23:10       ` William Kenworthy
2013-01-05 16:03     ` Kerin Millar [this message]
2013-01-05 17:45       ` Mark Knecht
2013-01-08  1:46         ` Canek Peláez Valdés

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=50E84EBE.1050007@fastmail.co.uk \
    --to=kerframil@fastmail.co.uk \
    --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