Re: [SLUG] Locking network interface number to specific MAC address

2007-05-30 Thread Matthew Hannigan
On Wed, May 30, 2007 at 02:06:57PM +1000, Jeff Waugh wrote: Yeah, what Simon meant was that these are hardware-specific things that are set during install/use, which make an Ubuntu install harder to 'port' to different hardware... one of the things that has traditionally been a great

Re: [SLUG] Locking network interface number to specific MAC address

2007-05-29 Thread Simon Wong
On Thu, 2007-05-17 at 14:49 +1000, Erik de Castro Lopo wrote: Thanks Jdub. Perfect fix. Also explains why the interfaces on this machine were eth2 and eth3 and not eth0 and eth1 (the drive was cloned from another machine with the same motherboard). Yes, one of the two main things that are not

Re: [SLUG] Locking network interface number to specific MAC address

2007-05-29 Thread Erik de Castro Lopo
Simon Wong wrote: Yes, one of the two main things that are not portable with Ubuntu Sorry, my problem had nothing to do with Ubuntu, but was a direct result of me cloning the disk of a working Ubuntu install and then booting a whole bunch of other machines from the cloned disks. Erik --

Re: [SLUG] Locking network interface number to specific MAC address

2007-05-29 Thread Jeff Waugh
quote who=Erik de Castro Lopo Simon Wong wrote: Yes, one of the two main things that are not portable with Ubuntu Sorry, my problem had nothing to do with Ubuntu, but was a direct result of me cloning the disk of a working Ubuntu install and then booting a whole bunch of other machines

Re: [SLUG] Locking network interface number to specific MAC address

2007-05-17 Thread Paul Trevethan
On Thu, 17 May 2007 14:36:20 +1000 Jeff Waugh [EMAIL PROTECTED] wrote: quote who=Erik de Castro Lopo I have a motherboard with two identical (apart from the MAC addresses of course) ethernet interfaces. The two MAC addresses are consectutively numbered; XX:XX:XX:XX:XX:34 and

Re: [SLUG] Locking network interface number to specific MAC address

2007-05-17 Thread Mark Phillips
Hi Erik, In my purpose built kernel I have in /etc/udev/rules.d/26-network.rules ACTION==add, SUBSYSTEM==net, BUS==pci, ID==:00:10.0, NAME=eth0 ACTION==add, SUBSYSTEM==net, BUS==pci, ID==:00:11.0, NAME=eth1 to solve this very problem. However tracking down the fix gave lot's of other

[SLUG] Locking network interface number to specific MAC address

2007-05-16 Thread Erik de Castro Lopo
Hi all, I have a motherboard with two identical (apart from the MAC addresses of course) ethernet interfaces. The two MAC addresses are consectutively numbered; XX:XX:XX:XX:XX:34 and XX:XX:XX:XX:XX:35. On most reboots, the interface with the 34 MAC address becomes eth2 and the other becomes

Re: [SLUG] Locking network interface number to specific MAC address

2007-05-16 Thread Jeff Waugh
quote who=Erik de Castro Lopo I have a motherboard with two identical (apart from the MAC addresses of course) ethernet interfaces. The two MAC addresses are consectutively numbered; XX:XX:XX:XX:XX:34 and XX:XX:XX:XX:XX:35. On most reboots, the interface with the 34 MAC address becomes eth2

Re: [SLUG] Locking network interface number to specific MAC address

2007-05-16 Thread Joseph Goncalves
On Thu, 17 May 2007, Erik de Castro Lopo wrote: I have a motherboard with two identical (apart from the MAC addresses of course) ethernet interfaces. The two MAC addresses are consectutively numbered; XX:XX:XX:XX:XX:34 and XX:XX:XX:XX:XX:35. On most reboots, the interface with the 34 MAC

Re: [SLUG] Locking network interface number to specific MAC address

2007-05-16 Thread Tony Green
On Thu, 17 May 2007 14:20:33 +1000, Erik de Castro Lopo [EMAIL PROTECTED] wrote: Hi all, I have a motherboard with two identical (apart from the MAC addresses of course) ethernet interfaces. The two MAC addresses are consectutively numbered; XX:XX:XX:XX:XX:34 and XX:XX:XX:XX:XX:35. On

Re: [SLUG] Locking network interface number to specific MAC address

2007-05-16 Thread Erik de Castro Lopo
Jeff Waugh wrote: /etc/iftab to the rescue (if you're facing this problem on your usual Debian or Ubuntu). Nice and simple! :-) Thanks Jdub. Perfect fix. Also explains why the interfaces on this machine were eth2 and eth3 and not eth0 and eth1 (the drive was cloned from another machine with