* Mathias Homann [03-17-15 12:27]:

That there doesn't look like "it has an IP address", it looks like "it does NOT have an IP address, except for an autogenerated link-local address based on the MAC address of the NIC". So yes, networkmanager seems to be broken there... or the DHCP server died.

Cheers MH

On 17/03/15 16:12, Bernhard Voelker wrote:

...

On 03/17/2015 03:08 AM, Patrick Shanahan wrote:

...

with NetworkManager reporting connection ifconfig: wlp3s0 Link encap:Ethernet HWaddr 48:D2:24:A8:07:0D inet6 addr: fe80::4ad2:24ff:fea8:70d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1133 errors:0 dropped:0 overruns:0 frame:0 TX packets:526 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:160461 (156.7 Kb) TX bytes:100254 (97.9 Kb)

No local address

Ok, reverted to NM and still no connection ps auxf |grep dhcp has no output dhcpcd wlp3s0 provides connection What *should* start dhcpcd <wlp3s0> or how do I correct the situation? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Neil Rickert [03-17-15 20:41]:

On Tuesday, March 17, 2015 02:14:06 PM Patrick Shanahan wrote:

...

Ok, reverted to NM and still no connection ps auxf |grep dhcp has no output

dhcpcd wlp3s0 provides connection

What *should* start dhcpcd <wlp3s0> or how do I correct the situation?

tks,

I had a similar problem with a newly install 20150309. But I don't recall whether that was after I switched from NetworkManager to wicked, or after I later switched back to NetworkManager.

I had an IPv6 address, but no IPv4 address. That included a public IPv6 address, which it presumably picked up from a router announcement. So I did have network of sorts.

To fix it, I used:

systemctl stop network systemctl start network

It has been fine on reboot thus far.

Didn't work for me, rebooting requires changing to wicked and back, then executing "dhcpcd wlp3s0" in order to connect with NetworkManager. Wicked connects fine but is not good for traveling :^( tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Wednesday 18 March 2015 13.14:47 Patrick Shanahan wrote:

* Patrick Shanahan [03-16-15 22:11]:

...

Tumbleweed

Just forced to return to wicked on my acer laptop. NetworkManager says it connects but creates no local address for inet, s/b 192.168.1.14.

yast network activate wicked restart network

and I have service.

wtf,

resolve.conf is regenerated but not changed

with NetworkManager reporting connection ifconfig: wlp3s0 Link encap:Ethernet HWaddr 48:D2:24:A8:07:0D inet6 addr: fe80::4ad2:24ff:fea8:70d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1133 errors:0 dropped:0 overruns:0 frame:0 TX packets:526 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:160461 (156.7 Kb) TX bytes:100254 (97.9 Kb)

No local address

with wicked: ifconfig: wlp3s0 Link encap:Ethernet HWaddr 48:D2:24:A8:07:0D inet addr:192.168.1.14 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::4ad2:24ff:fea8:70d/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1904 errors:0 dropped:3 overruns:0 frame:0 TX packets:905 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:369344 (360.6 Kb) TX bytes:157962 (154.2 Kb)

Today's update to VERSION="20150316 (Tumbleweed)" offers *no* improvement.

Did you check what dhpc client is used and is it working with networkmanager ? Just a rough guess ... -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Board, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 03/21/2015 01:58 PM, Patrick Shanahan wrote:

* Bruno Friedmann [03-21-15 13:43]:

...

On Wednesday 18 March 2015 13.14:47 Patrick Shanahan wrote: [...]

...

Today's update to VERSION="20150316 (Tumbleweed)" offers *no* improvement.

Did you check what dhpc client is used and is it working with networkmanager ? Just a rough guess ...

tks, but there is *no* dhcp* running ps auxf dhcp no output

returning to dwicked

rpm -qa *dhcp* dhcpcd-3.2.3-47.82.2.x86_64 dhcp-4.2.6-13.1.x86_64 dhcp-client-4.2.6-13.1.x86_64

On my Tumbleweed installation using NM, DHCP services are provided by dhclient. The appropriate ps command follows: finger@larrylap2:~> ps ax | grep dhcp 1348 ? S 0:00 /sbin/dhclient -d -q -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient-c04ada3f-50f7-4137-b4cf-78704bcc5d6c-wlan0.lease -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0 File /sbin/dhclient is provided by package dhcp-client, thus it should be on your system. I have the same rpms installed plus I have dhcp-server so that I can test access points using hostapd, but you should not need that. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 03/21/2015 06:14 PM, Patrick Shanahan wrote:

* Larry Finger [03-21-15 16:36]:

...

On 03/21/2015 01:58 PM, Patrick Shanahan wrote:

...

* Bruno Friedmann [03-21-15 13:43]:

...

On Wednesday 18 March 2015 13.14:47 Patrick Shanahan wrote: [...]

...

Today's update to VERSION="20150316 (Tumbleweed)" offers *no* improvement.

Did you check what dhpc client is used and is it working with networkmanager ? Just a rough guess ...

tks, but there is *no* dhcp* running ps auxf dhcp no output

returning to dwicked

rpm -qa *dhcp* dhcpcd-3.2.3-47.82.2.x86_64 dhcp-4.2.6-13.1.x86_64 dhcp-client-4.2.6-13.1.x86_64

On my Tumbleweed installation using NM, DHCP services are provided by dhclient. The appropriate ps command follows:

finger@larrylap2:~> ps ax | grep dhcp 1348 ? S 0:00 /sbin/dhclient -d -q -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient-c04ada3f-50f7-4137-b4cf-78704bcc5d6c-wlan0.lease -cf /var/lib/NetworkManager/dhclient-wlan0.conf wlan0

File /sbin/dhclient is provided by package dhcp-client, thus it should be on your system. I have the same rpms installed plus I have dhcp-server so that I can test access points using hostapd, but you should not need that.

switch using yast to NetworkManger after reinstalling dhcp-client-4.2.6-13.1.x86_64

no network, nop ipv4 address for wireless

rebooted box

still no network and ps ax |grep dhcp provides nothing

systemctl reports NetworkManager active (running)

The applet shows a connection to my intended netowrk

NetworkManager.service - Network Manager Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled) Active: active (running) since Sat 2015-03-21 18:13:29 EDT; 1min 57s ago Main PID: 3665 (NetworkManager) CGroup: /system.slice/NetworkManager.service └─3665 /usr/sbin/NetworkManager --no-daemon

Mar 21 18:14:19 acer NetworkManager[3665]: <info> (wlp3s0): Activation: Stage 5 of 5 (IPv6 Commit) scheduled... Mar 21 18:14:19 acer NetworkManager[3665]: <info> (wlp3s0): Activation: Stage 5 of 5 (IPv6 Commit) started... Mar 21 18:14:19 acer NetworkManager[3665]: <info> (wlp3s0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] Mar 21 18:14:19 acer NetworkManager[3665]: <info> (wlp3s0): Activation: Stage 5 of 5 (IPv6 Commit) complete. Mar 21 18:14:19 acer NetworkManager[3665]: <info> (wlp3s0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] Mar 21 18:14:19 acer NetworkManager[3665]: <info> (wlp3s0): device state change: secondaries -> activated (reason 'none') [90 100 0] Mar 21 18:14:19 acer NetworkManager[3665]: <info> NetworkManager state is now CONNECTED_LOCAL Mar 21 18:14:19 acer NetworkManager[3665]: <info> (wlp3s0): roamed from BSSID C0:C1:C0:B4:EA:20 (camellia1) to C0:C1:C0:B4:EA:21 (camellia1) Mar 21 18:14:19 acer NetworkManager[3665]: <info> (wlp3s0): Activation: successful, device activated. Mar 21 18:14:19 acer NetworkManager[3665]: <info> startup complete

ifconfig wlp3s0 shows no ipv4 address ping yahoo.com fails

returning to dwicked provides netowrk but a network reset is required.

It appears that dhclient is failing to start. I should have had you use 'ps ax | grep dhclient'. The NM part of the log is as follows: NetworkManager[732]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed NetworkManager[732]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless ne NetworkManager[732]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled. NetworkManager[732]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started... NetworkManager[732]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0] NetworkManager[732]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds) NetworkManager[732]: <info> dhclient started with pid 1348 NetworkManager[732]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete. NetworkManager[732]: <info> (wlan0): DHCPv4 state changed nbi -> preinit NetworkManager[732]: <info> (wlan0): DHCPv4 state changed preinit -> bound NetworkManager[732]: <info> address 192.168.1.108 NetworkManager[732]: <info> plen 24 (255.255.255.0) NetworkManager[732]: <info> gateway 192.168.1.1 NetworkManager[732]: <info> server identifier 192.168.1.1 NetworkManager[732]: <info> lease time 86400 NetworkManager[732]: <info> nameserver '192.168.1.1' NetworkManager[732]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Configure Commit) scheduled... NetworkManager[732]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started... NetworkManager[732]: <info> (wlan0): device state change: ip-config -> ip-check (reason 'none') [70 80 0] NetworkManager[732]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete. NetworkManager[732]: <info> (wlan0): device state change: ip-check -> secondaries (reason 'none') [80 90 0] NetworkManager[732]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0] NetworkManager[732]: <info> NetworkManager state is now CONNECTED_LOCAL NetworkManager[732]: <info> NetworkManager state is now CONNECTED_GLOBAL NetworkManager[732]: <info> Policy set 'Larry_ac' (wlan0) as default for IPv4 routing and DNS. NetworkManager[732]: <info> Activation (wlan0) successful, device activated. Mine is doing IPv4, not IPv6. Perhaps that is the difference. Larry -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* 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) -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Larry Finger [03-24-15 21:14]: [...]

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. :)

Well, tks for lookin. My "Irish" luck is fantastic, especially after a half-gallon of Mexican Beer, Dos Equis. I have tried six or more NM installs and failed on all except a short period on my acer which began this thread. Either too many teeth or not enought Dos Equis :^) tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 24/03/15 12:37, 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)

I don't know whether this is of any help ..... I have a desktop using T'Weed installed clean from a Jan 2015 snapshot. I have only ever done updates, never upgrades, since then. I have a wired connection. NM has always worked, although occasionally it fails to connect at boot up, but using the applet if I disconnect and then connect it works. When I look at the process tree, I see dhclient as a sub-process of NM. I should add that I know almost nothing about network set-ups, it just worked out of the box. Regards, David. ----------------------- XFCE 4.12 NM 1.0.0 ==== My settings in "yast network": Global enable ipv6 hostname to send: auto (change default route via dhcp) Overview *** Different from yours - all buttons disabled, but showing the hardware details (Manufacturer, MAC address etc.), plus: - Device name: emp3s0 - Started manually - IP address Assigned using DHCP Hostname/DNS Nothing checked here. Routing not changed (system default) ==== NetworkManager Connection settings for emp3s0 General Auto connect when available All users may connect Ethernet Mac address specified MTU automatic IPv4 Settings Auto (DHCP) addresses only IPv6 Settings Link-Local only All other tabs untouched. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org