Just installed from scratch 5.5
Weird, eth0 is now eth1 and eth1 is eth0. Don't even know how I'm sending this message as the the CentOS machine can't connect to the internet and this windoze box uses the Centos box as a gateway.
On 10-05-18 08:51 PM, Thomas Dukes wrote:
Just installed from scratch 5.5
Weird, eth0 is now eth1 and eth1 is eth0. Don't even know how I'm sending this message as the the CentOS machine can't connect to the internet and this windoze box uses the Centos box as a gateway.
I've had to swap out the ethX mapping enough times that I wrote down how to do it here:
http://wiki.alteeve.com/index.php/Changing_the_ethX_to_Ethernet_Device_Mappi...
Sorry for the long URL. Also, it's a side page to a larger paper, so the Xen stuff you can ignore. Other than that, it's a step-by-step walkthrough on swapping the ethX devices around.
Digimer wrote:
On 10-05-18 08:51 PM, Thomas Dukes wrote:
Just installed from scratch 5.5
Weird, eth0 is now eth1 and eth1 is eth0. Don't even know how I'm sending this message as the the CentOS machine can't connect to the internet and this windoze box uses the Centos box as a gateway.
I've had to swap out the ethX mapping enough times that I wrote down how to do it here:
http://wiki.alteeve.com/index.php/Changing_the_ethX_to_Ethernet_Device_Mappi...
Sorry for the long URL. Also, it's a side page to a larger paper, so the Xen stuff you can ignore. Other than that, it's a step-by-step walkthrough on swapping the ethX devices around.
nice, but a couple of comments: you have DEVICE=eth0 in all ifcfg-ethX files, shouldn't these match? you have the same HWADDR for the intel and d-link, you probably should have 00:AA:BB:CC:DD:EE for the d-link?
On 10-05-19 07:10 AM, Nicolas Thierry-Mieg wrote:
Digimer wrote:
On 10-05-18 08:51 PM, Thomas Dukes wrote:
Just installed from scratch 5.5
Weird, eth0 is now eth1 and eth1 is eth0. Don't even know how I'm sending this message as the the CentOS machine can't connect to the internet and this windoze box uses the Centos box as a gateway.
I've had to swap out the ethX mapping enough times that I wrote down how to do it here:
http://wiki.alteeve.com/index.php/Changing_the_ethX_to_Ethernet_Device_Mappi...
Sorry for the long URL. Also, it's a side page to a larger paper, so the Xen stuff you can ignore. Other than that, it's a step-by-step walkthrough on swapping the ethX devices around.
nice, but a couple of comments: you have DEVICE=eth0 in all ifcfg-ethX files, shouldn't these match? you have the same HWADDR for the intel and d-link, you probably should have 00:AA:BB:CC:DD:EE for the d-link?
Doh! I'll fix that in a couple of hours, thanks for pointing that out!
---- Digimer linux@alteeve.com wrote:
On 10-05-19 07:10 AM, Nicolas Thierry-Mieg wrote:
Digimer wrote:
On 10-05-18 08:51 PM, Thomas Dukes wrote:
Just installed from scratch 5.5
Weird, eth0 is now eth1 and eth1 is eth0. Don't even know how I'm sending this message as the the CentOS machine can't connect to the internet and this windoze box uses the Centos box as a gateway.
I've had to swap out the ethX mapping enough times that I wrote down how to do it here:
http://wiki.alteeve.com/index.php/Changing_the_ethX_to_Ethernet_Device_Mappi...
Sorry for the long URL. Also, it's a side page to a larger paper, so the Xen stuff you can ignore. Other than that, it's a step-by-step walkthrough on swapping the ethX devices around.
Thanks,
I edited the files last night and got it set like it was.
Eddie
On 5/19/2010 8:25 AM, tdukes@sc.rr.com wrote:
Weird, eth0 is now eth1 and eth1 is eth0. Don't even know how I'm sending this message as the the CentOS machine can't connect to the internet and this windoze box uses the Centos box as a gateway.
I've had to swap out the ethX mapping enough times that I wrote down how to do it here:
http://wiki.alteeve.com/index.php/Changing_the_ethX_to_Ethernet_Device_Mappi...
Sorry for the long URL. Also, it's a side page to a larger paper, so the Xen stuff you can ignore. Other than that, it's a step-by-step walkthrough on swapping the ethX devices around.
Thanks,
I edited the files last night and got it set like it was.
Sometimes it's easier to just move the cables... Or have someone on site do it.
On 10-05-19 10:33 AM, Les Mikesell wrote:
On 5/19/2010 8:25 AM, tdukes@sc.rr.com wrote:
Weird, eth0 is now eth1 and eth1 is eth0. Don't even know how I'm sending this message as the the CentOS machine can't connect to the internet and this windoze box uses the Centos box as a gateway.
I've had to swap out the ethX mapping enough times that I wrote down how to do it here:
http://wiki.alteeve.com/index.php/Changing_the_ethX_to_Ethernet_Device_Mappi...
Sorry for the long URL. Also, it's a side page to a larger paper, so the Xen stuff you can ignore. Other than that, it's a step-by-step walkthrough on swapping the ethX devices around.
Thanks,
I edited the files last night and got it set like it was.
Sometimes it's easier to just move the cables... Or have someone on site do it.
This is sometimes possible, but not always. Here are a few cases I can think of where it isn't:
* If you've got IPMI piggy-backing on a physical interface, you may not want it to be on an Internet-facing LAN. * If you have a particularly fast ethernet device you need for a storage network. * If you've got a subnet that needs to use jumbo frames but only one NIC supports frames large enough for your application...
On 10-05-19 07:10 AM, Nicolas Thierry-Mieg wrote:
Digimer wrote:
On 10-05-18 08:51 PM, Thomas Dukes wrote:
Just installed from scratch 5.5
Weird, eth0 is now eth1 and eth1 is eth0. Don't even know how I'm sending this message as the the CentOS machine can't connect to the internet and this windoze box uses the Centos box as a gateway.
I've had to swap out the ethX mapping enough times that I wrote down how to do it here:
http://wiki.alteeve.com/index.php/Changing_the_ethX_to_Ethernet_Device_Mappi...
Sorry for the long URL. Also, it's a side page to a larger paper, so the Xen stuff you can ignore. Other than that, it's a step-by-step walkthrough on swapping the ethX devices around.
nice, but a couple of comments: you have DEVICE=eth0 in all ifcfg-ethX files, shouldn't these match? you have the same HWADDR for the intel and d-link, you probably should have 00:AA:BB:CC:DD:EE for the d-link?
It's fixed, thanks for catching that and letting me know. :)