| 1 |
On Tue, 9 Jan 2007 10:42:37 +1000, Richard Watson wrote: |
| 2 |
|
| 3 |
> Hi, I recently upgraded my system with emerge -uDN world. Afterwards I |
| 4 |
> found that net.eth0 was grabbing my firewire port (ieee1394) and I |
| 5 |
> needed to create net.eth2 for my NIC as net.eth1 was being assigned to |
| 6 |
> my wireless. My problem is that although "rc-update show" indicates all |
| 7 |
> my interfaces are NOT being loaded other than net.lo at boot (which is |
| 8 |
> what I want) my system keeps trying to start net.eth0 net.eth1 net.eth2 |
| 9 |
> in the " default" run level. Can anybody help? It's very frustrating |
| 10 |
> waiting for these interfaces to try and connect before timing out. |
| 11 |
|
| 12 |
Add RC_PLUG_SERVICES="!net.*" to /etc/conf.d/rc to stop the interfaces |
| 13 |
coming up at boot. Use udev rules to have the naming as you want. For |
| 14 |
example, I use |
| 15 |
|
| 16 |
KERNEL=="eth*", SYSFS{address}=="00:1a:23:3c:76:26", NAME:="eth0" |
| 17 |
KERNEL=="eth*", SYSFS{address}=="00:2d:94:ef:f2:c0", NAME:="eth1" |
| 18 |
KERNEL=="eth*", SYSFS{address}=="00:3c:99:ff:fe:3c:76:26", NAME:="eth2" |
| 19 |
|
| 20 |
To make my wired interface eth0, wireless eth1 and firewire eth2. The |
| 21 |
address strings are the MAC addresses of the interfaces. |
| 22 |
|
| 23 |
Alternatively, you can get rid of the firewire interface altogether by |
| 24 |
unsetting CONFIG_IEEE1394_ETH1394 in your kernel config |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
Neil Bothwick |
| 29 |
|
| 30 |
Will we ever get out of this airport? asked Tom interminably. |
Archives