From: Daniel Barkalow <barkalow@iabervon.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Question about /etc/conf.d/net entry
Date: Sun, 4 Feb 2007 18:37:07 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0702041822060.20138@iabervon.org> (raw)
In-Reply-To: <7225537e0702030946i539055d1i9818d3a0cd5155c6@mail.gmail.com>
On Sat, 3 Feb 2007, Shawn Singh wrote:
> The cable checked out. I used it to hookup my work laptop with the other
> laptop I was using as my client, and was able to ping each host. The fact
> that I had no link made me curious ... and I realized it made user error ...
> I was "SURE" that I verified the NIC I was plugging into was eth1, as I've
> got 3 NICs in the machine ... the one with no link is really eth2 ... not
> eth1 ... I plugged into the correct interface, and (perhaps) needless to
> say, my client is now seeing the gateway and the gateway sees the client.
I'd suggest using udev rules (create or add to
/etc/udev/rules.d/10-local.rules) like this:
ACTION=="add", SUBSYSTEM=="net", SYSFS{address}=="00:10:b5:0e:d6:e9", NAME="extra"
(note, one = in the last one, two in all of the others) to give intuitive
names to all of the network cards. Then you replace "eth1" everywhere with
"extra". This makes it easier to read, so you don't forget which is which,
and it means that if the kernel device enumeration changes, your rules
don't break, and if you need to repurpose cards or something, you can just
change the MAC addresses and the rules will be right.
It's a lot easier to keep "left", "middle", and "right" (or "uplink",
"downlink", and "extra") straight than "eth0", "eth2", and "eth1".
-Daniel
*This .sig left intentionally blank*
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2007-02-04 23:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-02 17:07 [gentoo-user] Question about /etc/conf.d/net entry Shawn Singh
2007-02-02 17:33 ` Michal 'vorner' Vaner
[not found] ` <20070202150401.4bc336ce@pascal.spore.ath.cx>
2007-02-02 21:51 ` Shawn Singh
2007-02-02 23:55 ` Dan Farrell
2007-02-03 17:46 ` Shawn Singh
2007-02-04 23:37 ` Daniel Barkalow [this message]
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=Pine.LNX.4.64.0702041822060.20138@iabervon.org \
--to=barkalow@iabervon.org \
--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