On 03/24/2015 07:37 AM, Patrick Shanahan wrote:
* Patrick Shanahan
[03-21-15 21:13]: * Larry Finger
[03-21-15 21:08]: [...] It appears that dhclient is failing to start. I should have had you use 'ps ax | grep dhclient'.
dhclient is definitely failing to start, but *why*.
ADD: Just reformatted and installed a dell inspiron 1750 laptop which defaulted to NetworkManager and failed to start dhcp. I was able to connect by issuing "dhcpcd wlp12s0", but lost connection when closing the root term where it was issued. "ps auxf |grep dhcp" revealed it was still running.
Used "yast network" to return to wicked.
Why is NetworkManager working for most others (I hear few complaints) and consistantly failing for me?
My settings in "yast network"
Global enable ipv6 hostname to send: auto (change default route via dhcp)
Overview General Activate at boot time Address Dynamic DHCP both ver Hardware not changed (system default)
Hostname/DNS Change via DHCP
Routing not changed (system default)
My previous efforts had been done using a Tumbleweed installation that had been upgraded from 13.2. On the off chance that my success was due to the path that I followed, I downloaded the NET install ISO, wrote it to USB, and booted. From there, I blew away the old partition, but kept /home. After installation of the OS and the firmware (my wifi device uses b43), I could connect to my AP using NM with no difficulty. Again, my only IPv6 address is the default one based on the MAC address, but IPv4 is OK. My YaST network parameters are the same as yours - at least when appropriate. I have no idea what is wrong for you. I guess it must be the luck of the Irish. :) Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org