All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Pattie" <pattieja@pcxperience.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] How to recognize P2P
Date: Tue, 30 Sep 2003 14:59:52 +0000	[thread overview]
Message-ID: <marc-lartc-106493442926192@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106461737829463@msgid-missing>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Derek wrote:
| The card problem is definately a fun one, although in my experience linux
| assigns iface names in the following fashion: PCI (from top (closest to
| AGP/CPU) to bottom), then Onboard. so usually I just play around with the
| order of the cards, although I'm sure theres a better way to do it. The
| networking HOWTO and appropriate mailing lists located here:
|
| https://secure.linuxports.com/
|
| will probably help a bit, too.

Actually, there is an effective way around this problem.  Find the MAC
address for each of your network cards.  Pick some names that are
meaningful for your interfaces, like 'internal' and 'external', or 'LAN'
and 'Internet'.  Then reassign those names to your interfaces so that
the name 'eth0' literally becomes 'external' and 'eth1' literally
becomes 'internal'.  You would then simply use your ifconfig or ip addr
commands to assign IP addresses and info just like you normally would.

I.e.,
ifconfig internal 192.168.0.1 netmask 255.255.255.0 ...
ifconfig external <Internet IP address> ...

How to do this, you ask?  nameif

man nameif is your friend.  It comes with the net-tools package under
Debian.  It should be installed by default on most RedHat and other
installs as well.

nameif takes the name you want to assign and the MAC address of the
device.  It will then change the name of the device with the specified
MAC address to the name you provide.  It apparently only works when the
device is available (i.e., loaded as a module or detected by the kernel)
and down.  I.e., it cannot be in an UP state.  With a little
experimentation, you can insert the nameif command into your startup
scripts and all your problems dissappear.  Then it doesn't matter in
what order the kernel detects your devices.

- --
Jason A. Pattie
pattieja@xperienceinc.com
Xperience, Inc. (http://www.xperienceinc.com)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQE/eZpouYsUrHkpYtARAgHDAJ9kdOFfHaUZ588wvr2EGBjl+XvevwCfbS7T
D1U0o+hsyaQLlF1doUPprWM=cJME
-----END PGP SIGNATURE-----


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
Mailscanner thanks transtec Computers for their support.

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2003-09-30 14:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-26 23:01 [LARTC] How to recognize P2P Jacek Bilski
2003-09-26 23:16 ` Derek
2003-09-26 23:31 ` Jacek Bilski
2003-09-29 15:03 ` Derek
2003-09-30 14:59 ` Jason A. Pattie [this message]
2003-09-30 21:45 ` miller69
2003-09-30 21:52 ` Jacek Bilski
2003-09-30 22:08 ` Derek

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=marc-lartc-106493442926192@msgid-missing \
    --to=pattieja@pcxperience.com \
    --cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.