[opensuse] Network does not start automatically nor manually after reboot (openSUSE 10.3)
I want my network connections starting automatically after booting on my toshiba laptop. However, when configuring it with yast it only works until rebooting. Under "Device Activation" I tried "At Boot Time", "On Cable connection", and "On Hotplug" without success. Even "Manually" does not enable me to ifup eth0 (instead it says "Interface eth0 is not available"). Strangely, the "External Zone" setting in yast's Network Card Setup seems to get lost after rebooting (and is set to "No zone, All Traffic Blocked"). When I re-run yast's Network Card Configuration and only change this firewall zone setting, everything works again, and the network is set up automatically, or at least I am able to ifup eth0 manually. Any hint how to enable automatic network start? Or at least manual start (with ifup) without having to launch yast every time? TIA Nino -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tue, Sep 23, 2008 at 9:07 AM, Nino Novak <nino@kflog.org> wrote:
I want my network connections starting automatically after booting on my toshiba laptop. However, when configuring it with yast it only works until rebooting. Under "Device Activation" I tried "At Boot Time", "On Cable connection", and "On Hotplug" without success. Even "Manually" does not enable me to ifup eth0 (instead it says "Interface eth0 is not available").
Strangely, the "External Zone" setting in yast's Network Card Setup seems to get lost after rebooting (and is set to "No zone, All Traffic Blocked"). When I re-run yast's Network Card Configuration and only change this firewall zone setting, everything works again, and the network is set up automatically, or at least I am able to ifup eth0 manually.
Any hint how to enable automatic network start? Or at least manual start (with ifup) without having to launch yast every time?
TIA Nino
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Does it start if you disable the firewall? Boris. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Boris Epstein wrote:
On Tue, Sep 23, 2008 at 9:07 AM, Nino Novak <nino@kflog.org> wrote:
I want my network connections starting automatically after booting on my toshiba laptop. However, when configuring it with yast it only works until rebooting. Under "Device Activation" I tried "At Boot Time", "On Cable connection", and "On Hotplug" without success. Even "Manually" does not enable me to ifup eth0 (instead it says "Interface eth0 is not available").
Strangely, the "External Zone" setting in yast's Network Card Setup seems to get lost after rebooting (and is set to "No zone, All Traffic Blocked"). When I re-run yast's Network Card Configuration and only change this firewall zone setting, everything works again, and the network is set up automatically, or at least I am able to ifup eth0 manually.
Any hint how to enable automatic network start? Or at least manual start (with ifup) without having to launch yast every time?
TIA Nino
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Does it start if you disable the firewall?
Boris.
No, disabling the firewall has no effect. Nino -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Nino Novak wrote:
I want my network connections starting automatically after booting on my toshiba laptop. However, when configuring it with yast it only works until rebooting. Under "Device Activation" I tried "At Boot Time", "On Cable connection", and "On Hotplug" without success. Even "Manually" does not enable me to ifup eth0 (instead it says "Interface eth0 is not available").
Strangely, the "External Zone" setting in yast's Network Card Setup seems to get lost after rebooting (and is set to "No zone, All Traffic Blocked"). When I re-run yast's Network Card Configuration and only change this firewall zone setting, everything works again, and the network is set up automatically, or at least I am able to ifup eth0 manually.
Any hint how to enable automatic network start? Or at least manual start (with ifup) without having to launch yast every time?
TIA Nino
Both my Toshiba laptops connect on boot. The only time they don't is if they have been unused for a while or when they have been shutdown while connected to a different network and then started when at my usual network. (Here network manager loses the setting to use a wep hex key - not always, but sometimes). my /etc/sysconfig/network/ifcfg-ath0 is: 13:01 alchemy/etc/sysconfig/network> sudo cat ifcfg-ath0 BOOTPROTO='dhcp' BROADCAST='' ETHTOOL_OPTIONS='' INTERFACETYPE='wlan' IPADDR='' MTU='' NAME='AR242x 802.11abg Wireless PCI Express Adapter' NETMASK='' NETWORK='' REMOTE_IPADDR='' STARTMODE='auto' USERCONTROL='yes' WIRELESS_AP='' WIRELESS_AUTH_MODE='open' WIRELESS_BITRATE='auto' WIRELESS_CA_CERT='' WIRELESS_CHANNEL='' WIRELESS_CLIENT_CERT='' WIRELESS_CLIENT_KEY='' WIRELESS_CLIENT_KEY_PASSWORD='' WIRELESS_DEFAULT_KEY='0' WIRELESS_EAP_AUTH='' WIRELESS_EAP_MODE='' WIRELESS_ESSID='skyline' WIRELESS_FREQUENCY='' WIRELESS_KEY='' WIRELESS_KEY_0='xxxxxxxxxx' WIRELESS_KEY_1='' WIRELESS_KEY_2='' WIRELESS_KEY_3='' WIRELESS_KEY_LENGTH='128' WIRELESS_MODE='Managed' WIRELESS_NICK='' WIRELESS_NWID='' WIRELESS_PEAP_VERSION='' WIRELESS_POWER='yes' WIRELESS_WPA_ANONID='' WIRELESS_WPA_IDENTITY='' WIRELESS_WPA_PASSWORD='' WIRELESS_WPA_PSK='xxxx_your_passphrase_xxxx' If you are using wpa-tkip, then you need to also configure wpa-supplicant. To set up wpa_supplicant.conf, do the following: wpa_passphrase "your_ESSID" "Some_Decent_PassPhrase_of_up_64_Characters" >> /etc/wpa_supplicant.conf Edit /etc/wpa_supplicant.conf and add the following lines into the network section: key_mgmt=WPA-PSK # proto=WPA proto=RSN Uncomment the proto=WPA line (and comment out the RSN line) to enable WPA1. Leave as is for WPA2 (stronger encryption). If it is an older Toshiba, the opensuse madwifi drivers are fine. If you have a newer atheros card in the laptop, you will have the best luck with the madwifi drivers from: http://download.opensuse.org/repositories/home:/schmolle1980/ Hope that helps. -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 23 September 2008 at 8:12 pm, David C. Rankin wrote:
my /etc/sysconfig/network/ifcfg-ath0 is:
David, thanks for your detailed description, my ifcfg-eth0 is pretty similar, but this is not the problem as the connection is always established quickly and stable - but only if I start 'yast network'. I even can abort the module right after initializing it. The connection seems to be activated through mere module starting. But no chance to get it started without yast. Yast's network module start seems to trigger connection establishment. After this initial trigger I am able to ifdown and ifup the connection deliberately. But I can't get it work without entering yast. ??? Regards, Nino -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Nino Novak wrote:
On Tuesday 23 September 2008 at 8:12 pm, David C. Rankin wrote:
my /etc/sysconfig/network/ifcfg-ath0 is:
David, thanks for your detailed description, my ifcfg-eth0 is pretty similar, but this is not the problem as the connection is always established quickly and stable - but only if I start 'yast network'. I even can abort the module right after initializing it. The connection seems to be activated through mere module starting.
But no chance to get it started without yast. Yast's network module start seems to trigger connection establishment.
After this initial trigger I am able to ifdown and ifup the connection deliberately. But I can't get it work without entering yast.
???
Regards, Nino
Nino, That's Strange indeed. Have you tried running knetworkmanager manually from konsole? The only other thoughts I have are when you establish a new connection in knetworkmanager, there is an option to 'autostart' the connection. Make sure you have that checked. Also, check /opt/kde3/env/knetworkmanager.default.sh, and it should contain: kdehome=$HOME/.kde test -n "$KDEHOME" && kdehome=`echo "$KDEHOME"|sed "s,^~/,$HOME/,"` knetworkmanager_autostart= if test ! -f $kdehome/share/config/knetworkmanagerrc; then knetworkmanager_autostart=$(. /etc/sysconfig/network/config && echo "$NETWORKMANAGER") elif test $kdehome/share/config/knetworkmanagerrc -ot /etc/sysconfig/network/config; then knetworkmanager_autostart=$(. /etc/sysconfig/network/config && echo "$NETWORKMANAGER") fi # kconfig will merge it in case we overwrite another setting if test -n "$knetworkmanager_autostart"; then echo "[General]" >> $kdehome/share/config/knetworkmanagerrc echo "Autostart=$knetworkmanager_autostart" >> $kdehome/share/config/knetworkmanagerrc fi Then to check your ~/.kde/share/config/knetworkmanagerrc (it should exist and contain information on your recent connections) If you have your card set in yast to use networkmanager, and the option that allows 'user control', then I suspect you haven't checked the 'autostart' option when configuring eth0 in knetworkmanager. (ifup used to be so easy...) -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Sep 25, 2008 at 10:08 PM, Nino Novak <nino@kflog.org> wrote:
David, thanks for your detailed description, my ifcfg-eth0 is pretty similar, but this is not the problem as the connection is always established quickly and stable - but only if I start 'yast network'. I even can abort the module right after initializing it. The connection seems to be activated through mere module starting.
But no chance to get it started without yast. Yast's network module start seems to trigger connection establishment.
After this initial trigger I am able to ifdown and ifup the connection deliberately. But I can't get it work without entering yast.
???
Regards, Nino --
Don't know type of your Toshiba, but does it have an on-off switch for wifi that always off when it reboot? It happens also on my friend Acer notebook. He always go to yast every time he boot to connect to wifi. Seems like the kernel doesn't recognize the switch. It is not happens in my Compaq laptop. medwinz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
Boris Epstein -
David C. Rankin -
medwinz -
Nino Novak