This is a discussion on wireless interface initialization script within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> There seems to be a problem with the script /etc/rc.d/rc.inet1; my wireless adapter is linked to eth1 and the ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| There seems to be a problem with the script /etc/rc.d/rc.inet1; my wireless adapter is linked to eth1 and the ethernet to eth0. the rc.inet1 code lauches the rc.wireless script even for eth0; the main problem is that the rc.inet1 makes some initialisation for all interface which are not yet configure and up with this following statement: if ! /sbin/ifconfig | grep -w "${1}" 1>/dev/null || \ ! /sbin/ifconfig ${1} | grep "inet addr" 1> /dev/null ; then \ # interface not up or not configured ... if [ -x /etc/rc.d/rc.wireless ]; then . /etc/rc.d/rc.wireless ${1} start # Initialize any wireless parameters fi .... fi and only eth0 meets the requirements of this above first "if" statement because the ethernet network card is not linked I think. so the wireless initialisation never occurs for eth1. actually the rc.wireless script only loads the parameters defined in rc.wireless.conf which are not compulsory because the wifi card drivers define some default values; but I set some parameters which I would like to be loaded, so I would like to solve this misconception. |
| |||
| Linux and wireless is pretty much a big mess. The problem is usually with chipsets and drivers. The easy solution is to attach a bridge to your eth0 RJ45 port. A bridge is sometimes called a game adapter. A bridge can be configured by browsing to the IP of the bridge. No drivers are needed. Slackware scripts rc.inet1 and rc.wireless will not work unless you are working with a server or desktop in a fixed location. IOW, you will need ALWAYS to be connecting to the SAME access point(AP). This is because rc.wireless.conf ties the MAC of your adapter to a set of iwconf commands that are directed to a specific AP. If you are mobile, this will NOT work for you. My rc.inet1 on my laptop does nothing more than set up lo. After boot, I need to run an appropriate rc.wifi[Where-Ever-I-am] script to attach to an AP. Each of these scripts contains the necessary iwconfig/ifconfig/dhcpc commands to attach to the target AP. When a wifi is not available, I use kppp to connect via my cell phone. John |
| ||||
| actually, I'm mistaken by posting that issue a bit too early i think because i noticed later that the script rc.inet1 works fine with the rc.wireless one. I was complainint that the script wouldn't initialize the wireless interface but actually everytime i was running the script the wireless interface was already up. so to test the script i had to turn down whatever the interface i want rc.inet1 to initialize. $ifconfig ethX down $/usr/rc.d/rc.inet1 |
| Thread Tools | |
| Display Modes | |
|
|