https://bugzilla.novell.com/show_bug.cgi?id=393801
User casualprogrammer@yahoo.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=393801#c17
Casual J. Programmer changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|casualprogrammer@yahoo.com |
--- Comment #17 from Casual J. Programmer 2008-05-27 01:13:29 MDT ---
I just had a chance to repeat all the steps for configuration, I will just list
them here, then we can decide whether some of them are bugs in their own right.
Clean installing from factory sets network up for use with NetworkManager, to
use the traditional method yast2 lan needs to be invoked and NICs reconfigured.
First of all "Network Settings/Global Options" check "Traditional Method" with
ifup, as well as set up the credentials for wlan ( ESSID / Pasphrase ) and the
Routing Gateway.
Yast2 spends a lot of time setting up routing, it then comes to a point where
it wants to install smpppd and kinternet, which fails as during network setup
repos are not available as network is down.
Checking this shows wlan0 comes preconfigured with "Enable Device Control for
Non-root User Via Kinternet" unchecking this makes yast2 lan finish properly.
Nothing goes at all..
there are two instances of dhcpcd running, killing and restarting one with
dhcpcd wlan0 achieves nothing.
As wpa_supplicant is required, checking whether it's up. ps -A | grep wpa shows
2 instances are running. ifdown wlan0 makes one go away. So there must be one
left over from NetworkManager. Killing it and ifup wlan0 produces a state where
the AP (192.168.0.1) can be pinged but no network access possible.
Going over every step again, reveals that yast2 lan is removing the entry for
the routing gateway when started, it has to be set explicitly again before
closing it.
After that both dhcpcd as well as dhclient can get IP address and Name
Resolution.
One thing I added in the previous experiments was the concurrent use of dhcpd
and dhclient, as I wasn't aware that they are really two different animals
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.