View Full Version : Why /sbin/ifup eth1 everytime?
20th September 2005, 02:36 AM
I am running FC4 on a HP Pavillion DV4000.
Everytime I login I have to 'turn on' wireless networking with a
"/sbin/ifup eth1" command.
Why is this a necessary step? I also have to do the ifup thing in my awake from
sleep script that acpi invokes when the lid is opened...
I put the ifup command in rc.local but it did no good.
20th September 2005, 06:28 AM
.. im guessing your wireless is all setup.. to have it automatically come on at boot:
click edit > eth1
check activate device on boot
exit/save changes and restart and it should automatically come on at boot... I don't know if this will also come on after the sleep script... but i suppose you could possible add that in the script
20th September 2005, 01:43 PM
The checkbox is ticked to start at boot.
I checked the ifcfg-eth1 and the ONBOOT is set to true.
I tried doing an ifup eth1 in rc.local but I still had
to repeat the command after I logged in....
I currently have the ifup eth1 command as one of my
session startup actions and it appears to work ok, but
that seems like a kludge.
14th December 2005, 03:55 PM
I had the same issue on a newly-installed laptop on which I had other wireless network troubles. I probably hadn't experimented with it as much as you. After reading your post, I started studying the scripts in /etc/sysconfig/network-scripts/. Soon, my head started to hurt. Then, when I rebooted, it went away.
It may be that there is a state variable stored by one of those scripts that influences this behavior, but the scripts are sufficiently complex that I'm unmotivated to look further. I was activating and deactivating using system-network-config which I suspect uses those scripts. The interface just never would start on boot, even when the other networking issues seemed resolved. If you are using Gnome, try activating eth1 using system-network-config (as root) and then rebooting.
I'm sorry to suggest something this unsatisying, but I experienced the same frustration and it went away for reasons I don't understand.
14th December 2005, 04:23 PM
Oh well, maybe it is just as well that it did not come up
I decided to go for stronger encryption and installed "wpa_supplicant"
to enable WPA encryption.
I start the wpa_supplicant in rc.local and by the time I log in
I have an wireless connection ready to go.
vBulletin® v3.8.7, Copyright ©2000-2013, vBulletin Solutions, Inc.