Terry L. Inzauro wrote:
Jan Kalcic wrote:
Simple, I configure eth0 with 192.168.0.6, reboots, and then it
doesn't have an IP address
eth1 is configured with 192.168.100.2, and it keeps it upon reboot.
Scanning through /var/log/boot.msg doesn't yield much
I have noticed that udev renamed the eth devices, and if I rename eth0
to something like eth2 it works fine, but that's not really an option,
since some code (like iptables, smb, MySQL & heartbeat are bound to
the network devices. This is part of a cluster, so to change the ether
device names on 1 machine cold cause problems all over the LAN
<6>eth1: SiS 900 PCI Fast Ethernet at 0xa800, IRQ 225, 00:0f:ea:c3:3c:55.
<6>eth0 renamed to ethxx0
<6>eth1 renamed to eth0
<6>ethxx0 renamed to eth1
Kind Regards
Rudi Ahlers
CEO, SoftDux
Web: http://www.SoftDux.com
Forum: http://Forum.SoftDux.com
Join SA WebHostingTalk today, on http://www.WebHostingTalk.co.za
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
Hi,
I wouldn't say that boot message doesn't produce much. On SuSE 9.3 you
had hotplug and coldplug which are now substitute by udev. What you
simply need to do is fix the lines in
/etc/udev/rules.d/30-net_persistent_names.rules. Now you propably have
several rules which create different interfaces for different devices.
Just keep the two rules you need and delete all the others. Then you
maybe have to reconfigure your network with YaST.
Regards,
Jan
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
i had this same issue on gentoo. i just want to state that this issue is not
specific to any one
distro, but more so specific to udev.
create a file like "/etc/udev/rules.d/persistent_net.rules" with the following.
the udev
documentation can cite more examples if necessary. the following is just an
example, but
nevertheless works;)
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:50:8b:cf:15:e0",
NAME="eth0"
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:50:8b:cf:15:e1",
NAME="eth1"
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:50:8b:cf:73:9a",
NAME="eth2"
SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:50:8b:cf:73:9b",
NAME="eth3"
regards,
_Terry
I have "plaid" around with that file quite a bit, and it really only
maps the eth device name to the device's MAC address. It doesn't really
control the device's IP address. Renaming the device(s) yielded the same
problem. As you can see from one of my other replies.
Unplugging the LAN cable from the one device simple "swapped" the active
NIC to other one. If eth1 was on 192.168.100.2 & eth0 had no address,
and the pulled the cable on eth1, eth0 got it's address as 192.168.0.6 -
almost like it I could only use one NIC @ time. The re-installation is
done, but it's busy setting up the online update source, after
downloading the catalogs, and it's taking a hel'va long time. So I'll
just wait for it to finish, and try again
Kind Regards
Rudi Ahlers
CEO, SoftDux
Web: http://www.SoftDux.com
Forum: http://Forum.SoftDux.com
Join SA WebHostingTalk today, on http://www.WebHostingTalk.co.za
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
