Re: How to recognize P2P

Linux Advanced Routing and Traffic Control

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----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@xxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxx
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

[Index of Archives]     [LARTC Home Page]     [Netfilter]     [Netfilter Development]     [Network Development]     [Bugtraq]     [GCC Help]     [Yosemite News]     [Linux Kernel]     [Fedora Users]
  Powered by Linux