Re: [CentOS] Back to eth shuffling ...

2015-05-14 Thread Ashley M. Kirchner
When I was working on this last time (with the r8169 driver), someone on this list provided the following script which is what fixed the issue at the time by creating a new 70-persistent-net.rules file with the devices enumerated in order. However, this no longer works now. echo [KICKSTART]

Re: [CentOS] Back to eth shuffling ...

2015-05-14 Thread Ashley M. Kirchner
Actually, I know what the MAC is for the builtin Port1 and 2. Those are listed in the BIOS. But ultimately I don't want to rely on them as I want the same kickstart file to work for other machines, so hardcoding those in the kickstart file wouldn't quite work, unless I start writing multiple

Re: [CentOS] Back to eth shuffling ...

2015-05-14 Thread Kahlil Hodgson
another identical machine will have the same bus ids. that's why this works. Kahlil (Kal) Hodgson GPG: C9A02289 Head of Technology (m) +61 (0) 4 2573 0382 DealMax Pty LtdGitHub: @tartansandal Suite 1416 401 Docklands

Re: [CentOS] Back to eth shuffling ...

2015-05-14 Thread Kahlil Hodgson
apologies. just realised I was top posting again. damn this email client :-( ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] Back to eth shuffling ...

2015-05-14 Thread Kahlil Hodgson
On 15 May 2015 at 03:51, Ashley M. Kirchner ash...@pcraft.com wrote: After the machine boots and I look in /root/ksnet-devices, I see the MAC addresses for the devices as: Port1 - eth0 PCIe Card- eth1 Port2 - eth2 And yet, during the machine's POST (which can verify by the PXE boot up of

Re: [CentOS] Back to eth shuffling ...

2015-05-14 Thread Kahlil Hodgson
So a 70-persistent-net.rules like # onboard port 1 - eth0 ACTION==add, SUBSYSTEM==net, BUS==pci, ID==:00:19.0, NAME=eth0 # PCIe card - eth2 ACTION==add, SUBSYSTEM==net, BUS==pci, ID==:03:00.0, NAME=eth2 # onboard port 2 - eth1 ACTION==add, SUBSYSTEM==net, BUS==pci, ID==:08:00.0,

Re: [CentOS] Back to eth shuffling ...

2015-05-14 Thread Ashley M. Kirchner
Right, I understand that part. However I believe I'm now in the realm of making this specific to this machine as I have no guarantee that another identical machine will pop up with those same bus IDs. Maybe for the internal ports, but I don't know if the same will happen for the PCIe bus. Would

[CentOS] Back to eth shuffling ...

2015-05-13 Thread Ashley M. Kirchner
So I'm back to this problem. A quick run down of what the original problem was: I have a machine that I'm configuring to use kickstart to setup. It has two builtin ethernet ports (labeled ports 1 and 2) and I'm adding a third one on its PCIe bus. Originally I was using an r8169 clone a default

Re: [CentOS] Back to eth shuffling ...

2015-05-13 Thread Kahlil Hodgson
Have you tried having kickstart set up a more appropriate /etc/udev/rules/70-persistent-net.rules? This is normally written by /lib/udev/write_net_rules. You should be able to modify the automatically generated one to match what you need. K ___ CentOS