The problem is that the definition of 'correctly' has changed. I don't know if this is 'correctly' from your perspective of 'this is how I'm used to seeing it' or 'correctly' from any of the three or more ways one could use udev. The various defintions of 'correctly' may not overlap.
If they're showing up as eth0/eth1...why? Is it because you disabled udev's renaming entirely via the kernel command-line parameter? Because you've done some magic in /etc/udev/rules.d/? If the former, then OK, this is a different issue. If the latter, be aware that this isn't a supported configuration! You may very well have to rename your interfaces before this is done, or let udev rename them for you. On 04/06/2013 10:55 PM, Nick Khamis wrote: > ifconfig -a and ifconfig eth0 etc.. lists the interfaces correctly. > When trying to start net.eth0 the error that struck me as odd was: > > /lib64/rc/net/wpa_supplicant.sh: line 68: _is_wireless: command not found > /etc/init.d/net.eth0: line 548: _exists: command not found > > Sorry I can't paste stuff directly. I am literally taking phone pics > and communicating through my laptop. > > N. > > On 4/6/13, Michael Mol <mike...@gmail.com> wrote: >> It's probably not a module issue. >> >> Are these interfaces supposed to be DHCP-configured, or are they >> supposed to be statically and locally configured? >> >> If they're supposed to be configured via DHCP, try "dhclient >> $interface_name". If they're supposed to be statically configured, try >> using ifconfig to configure them manually. >> >> Also, ipmaddr is *not* the command you should be using. That deals >> strictly in multicast addresses, not unicast addresses. I presume you're >> trying to get your unicast addresses working properly. >> >> ifconfig -a >> >> On 04/06/2013 10:35 PM, Nick Khamis wrote: >>> Sorry I did mean /sbin/ip... Long day. Regardless, /sbin/ipmaddr does >>> now show any ipv4 related material. Other than the network card >>> driver, what module should I ensure is loaded for ipv4 related stuff. >>> As for /etc/conf.d/net, net.eth0/eth1 these were untouched and still >>> point to eth0 and eth1. >>> >>> As for /sbin/ip. I have no such command. >>> >>> N. >>> >>> >>> On 4/6/13, Michael Mol <mike...@gmail.com> wrote: >>>> /sbin/ip, not /etc/ip >>>> >>>> Those inet6 addresses beginning with ff02 are link-local addresses. >>>> Those are automatically configured on a link simply by the link being >>>> up. >>>> >>>> Something is failing to configure your interfaces' ipv4 settings. >>>> >>>> The culprit is almost certainly somewhere in one of these places, its >>>> lack of being in these places it part of your problem: >>>> >>>> /etc/conf.d/net >>>> /etc/init.d/net.* >>>> /etc/runlevels/*/net.* >>>> >>>> Otherwise, try those find/grep lines I offered. >>>> >>>> On 04/06/2013 10:01 PM, Nick Khamis wrote: >>>>> I do not have /etc/ip however, I do have /etc/ipmaddr show: >>>>> >>>>> 1: lo >>>>> inet6 ff02::1 >>>>> 2: sit0 >>>>> inte6 ff02::1 >>>>> 3: eth0 >>>>> link 33:33:00:00:00:01 >>>>> inet6 ff02:1 >>>>> 4: eth1 >>>>> link 33:33:00:00:00:01 >>>>> inet6 ff02:1 >>>>> >>>>> Too much inte6 for my liking... Did I somehow get rid of ipv4? >>>>> >>>>> N. >>>>> >>>>> On 4/6/13, Michael Mol <mike...@gmail.com> wrote: >>>>>> On 04/06/2013 08:53 PM, Nick Khamis wrote: >>>>>>> I took a closer look at /etc/udev/70-something-rules-net and >>>>>>> /sys/class/net/eth0/ and all the ATTR (i.e., address, type, dev_id) >>>>>>> line up fine. I did not find a "name" file in /sys/class/net/eth0 >>>>>>> however, >>>>>>> name=eth0 in etc/udev/70-something-rules-net. >>>>>>> >>>>>>> Ifconfig alone returns nothing. Ifconfig eth0/1 and lo returns the >>>>>>> interface >>>>>>> with no tx and rx traffic. And no ip address as set in conf.d/net. >>>>>>> >>>>>>> Please help guys. Server room is numbing...... >>>>>> >>>>>> /sbin/ip link addr show >>>>>> >>>>>> That will tell you the names of your interfaces, as they currently >>>>>> exist. >>>>>> >>>>>> You cannot reliably use 70-persistent-net-rules to assign interfaces >>>>>> names which the kernel may chose. This means things like 'eth0' and >>>>>> 'wlan0' are unreliable in principle. >>>>>> >>>>>> Once you know what the interface name will be, rename >>>>>> /etc/init.d/net.eth0 to /etc/init.d/net.$YOUR_INTERFACE_NAME_HERE , >>>>>> remove /etc/runlevels/net.eth0 and create a symlink in /etc/runlevels >>>>>> pointing at your new /etc/init.d/net.$WHATEVER file. >>>>>> >>>>>> Then /etc/init.d/net.$WHATEVER restart ... and things should come up, >>>>>> at >>>>>> least partially. To find anything else that might be broken: >>>>>> >>>>>> find /etc|grep eth0 >>>>>> find /etc -print0|xargs -0 grep eth0|egrep -v ':#' >>>>>> >>>>>> and rename 'eth0' there to your new interface name. >>>>>> >>>>>> I just went through this entire process on one of my machines...but I >>>>>> wiped all the files out of /etc/udev/rules.d/ and went with udev's new >>>>>> defaults, rather than set up my on persistent net rules for this >>>>>> machine. (That's a task for another day.) >>>>>> >>>>>> Frankly, the process is a PITA...and I'm going to go back to a >>>>>> persistent-net.rules file in the future; having to go through that >>>>>> entire process because of a NIC swap or an upstream behavior tweak is >>>>>> not something I care to have to do. >>>>>> >>>>>> >>>>> >>>> >>>> >>>> >>> >> >> >> >
signature.asc
Description: OpenPGP digital signature
