SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
my system has realtek network card built in the kernel and intel pro/wireless as a module. right now, i only use intel wireless, so i want to run dhcpcd ethN at boot, where N (0 or 1) corresponds to the intel wireless interface. i plan to do that by adding "dhcpcd eth1" to /etc/rc.d/rc.local.
here are my questions:
1) i use "dhcpcd eth1," assuming that it will be the case. is it possible it is assigned eth0 and the realtek card is assigned eth1? does that fact that the realtek support is built in the kernel and intel wireless is a module will always make realtek: eth0 and intel: eth1?
1) the ipw2100 module for the intel wireless card must have been loaded so that eth1 exists before /etc/rc.d/rc.local is run. in what file should i put "dhcpcd eth1" so that it is run after the module has been loaded (i have hotplug run at boot time)?
If you are running the later Slackwares (read that as 9.1 or 10.0) then look at the file, /etc/rc.d/rc.inet1.conf. You could, in that file, specify which, if any, NICs you want to configure via dhcpcd.
Let's say you do not want eth0 (your 'wired' NIC) to come up, then in the 'USE_DHCP[ n =""' and those that you want to come up via dhcpcd sould be 'USE_DHCP[n]="yes"
Note that you could also use this to configure any of your NICs for a static ip.
i guess that's easy enough.
however, i'm not sure if this is going to cause problems, but sometimes, like right now, ifconfig and iwconfig only see "lo" and "eth0" (wireless). usually it there are eth0 (wired) and eth1 (wireless). anyway i'll try and say yes for eth0 and eth1 (even though sometimes eth1 doesn't exist) and see what happens.
Should not be any problem saying yes to the eth? that sometime does not exist. On my laptop, I have "yes" to dhcp on both, the wired and the wireless NICs. When the wireless PCMCIA card is not plugged in, I get no error or compaints and have just the one NIC reported.
Some reason or another, the wireless card always comes up as eth0 and the hardwired NIC comes up as eth1, when both are running. When I pull the wireless out, then eth0 shows up as the wired nic. Since this never bothered me, I never investigated as to why the PCMCIA wireless always shows up before the hard-wired NIC.
If yu want to use the wireless NIC, only, you could put your wired NIC driver module in the /etc/hotplug/blacklist, which will prevent it from loading at bootup.
i mostly use the wireless interface, so blacklisting the wired one is perfect. but you also remind me of the ability to blacklist any module to prevent hotplug from loading it, saving boot time .