I’m running 13.1 on a Dell XPS laptop, have been for a while with no big issues, but now I have no network connectivity at all. Neither Wifi or ethernet connection will work. According to network manager, I am connected but I cannot get out, on any port. Any ideas on how to fix this? Do I need to reinstall network manager (I’ll have to see if I can find the disk somewhere)? Thanks.
What is reported by the following?
ip addr
ip route
grep -i name /etc/resolv.conf
Are you able to ping an internet address? eg
ping 8.8.8.8
ip addr returns:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: p5p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
link/ether 84:8f:69:b1:9f:4d brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 74:e5:0b:30:0c:50 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.2/24 brd 192.168.1.255 scope global wlp3s0
valid_lft forever preferred_lft forever
inet6 fe80::76e5:bff:fe30:c50/64 scope link
valid_lft forever preferred_lft forever
ip route returns:
default via 192.168.1.1 dev wlp3s0 proto static
192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.2 metric 9
grep -i name /etc/resolv.conf doesn’t return anything, but I am able to ping. I didn’t try using an ip address last night, only a domain name, which didn’t work.
On 11/26/2015 08:16 AM, z2 wrote:
>
> ip addr returns:
>
> Code:
> --------------------
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> inet 127.0.0.1/8 scope host lo
> valid_lft forever preferred_lft forever
> inet6 ::1/128 scope host
> valid_lft forever preferred_lft forever
> 2: p5p1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN qlen 1000
> link/ether 84:8f:69:b1:9f:4d brd ff:ff:ff:ff:ff:ff
> 3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
> link/ether 74:e5:0b:30:0c:50 brd ff:ff:ff:ff:ff:ff
> inet 192.168.1.2/24 brd 192.168.1.255 scope global wlp3s0
Valid address asigned to the wireless adapter.
> valid_lft forever preferred_lft forever
> inet6 fe80::76e5:bff:fe30:c50/64 scope link
> valid_lft forever preferred_lft forever
> --------------------
>
>
> ip route returns:
>
> Code:
> --------------------
> default via 192.168.1.1 dev wlp3s0 proto static
> 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.2 metric 9
Looks good.
>
> --------------------
>
>
> grep -i name /etc/resolv.conf doesn’t return anything, but I am able to
> ping. I didn’t try using an ip address last night, only a domain name,
> which didn’t work.
Opps! you do not have any nameservers defined. Edit (as root)
/etc/resolv.conf and add a couple of nameservers, the line should look
similar to this:
nameserver 8.8.8.8
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996
Thanks. Any idea why the name servers would have been deleted from that file? I haven’t messed with the network setting since I installed 13.1 about 2 years ago.
See the documentation referenced in the /etc/resolv.conf file’s comments. Direct edits to the file may not survive indefinitely.
You need to
If your network connection is configured as a DHCP client, the settings are empty and set to retrieve automatically.
- You can over-ride whatever your DHCP is supposed to provide by specifying your nameservers in your NM DHCP setting
- You can over-ride whatever your DHCP is supposed to provide by specifying in YAST > Hostname/DNS tab
- You can over-ride whatever your DHCP is spoosed to provide by following the instructions in /etc/resolv.conf
TSU
Ok, thanks. Now my question is why is DHCP not working? I can only resolve domains if I manually enter a DNS server, but this was never a problem before. It’s also not a problem with my router since the other computers work just fine, as does the XPS when I boot into windows. How do I fit it to just accept the DHCP settings from the router?
On 11/26/2015 10:06 AM, z2 wrote:
>
> Thanks. Any idea why the name servers would have been deleted from that
> file? I haven’t messed with the network setting since I installed 13.1
> about 2 years ago.
>
>
Best guess is a replaced modem/router that is not configured with
nameservers in the DHCP settings.
–
Ken
linux since 1994
S.u.S.E./openSUSE since 1996
Nope. I’ve had this modem for about a year now and it has nameservers listed, this computer just won’t accept the DHCP settings. Anyone else have any ideas as to why this would not be working? If it was a problem with the router, all the other computers would have this problem, but they don’t. It’s only the one. I also double checked the DNS servers in the router, they’re fine.
Could this problem have been caused by an update? I’m only asking because I just tried to install the latest updates listed in the desktop applet and received the following error:
NetworkManager-0.9.8.8-10.1.x86_64 requires ppp = 2.4.5, but this requirement cannot be provided
I haven’t really been keeping track of which packages get updated every time. I just install the updates whenever I get around to it. Also, ppp version 2.4.5 is installed.
So, no one has any ideas? I’ve also recently discovered that only my wifi works, the ethernet port will not recognize a connection, or maybe not accept DHCP settings? I can plug the cable into a different computer and it works, if I plug it into my laptop it just says not connected. No one knows how to fix this, or diagnose it?
Also, the ethernet works just fine when I boot into windows, so it’s not a hardware problem.
You could open a terminal and do the following
sudo tail -f /var/log/messages
then plug in the ethernet cable and observe the immediate output. CTRL-C to terminate.
Also, the ethtool command can give you link status information. Use the relevant interface name for your machine eg
/sbin/ethtool enp3s0
Thanks. sudo tail -f /var/log/messages results in:
2015-12-03T13:21:48.604697-05:00 xps kernel: 6026.816492] r8169 0000:06:00.0 p5p1: link up
2015-12-03T13:21:50.423383-05:00 xps kernel: 6028.637569] IPv4: martian source 255.255.255.255 from 172.30.51.173, on dev p5p1
2015-12-03T13:21:50.423404-05:00 xps kernel: 6028.637603] ll header: 00000000: ff ff ff ff ff ff 48 5b 39 d3 f7 5e 08 00 ......H[9..^..
2015-12-03T13:21:50.632302-05:00 xps kernel: [ 6028.846679] IPv4: martian source 255.255.255.255 from 172.30.51.169, on dev p5p1
2015-12-03T13:21:50.632319-05:00 xps kernel: 6028.846722] ll header: 00000000: ff ff ff ff ff ff a4 ba db 02 7e 49 08 00 ..........~I..
2015-12-03T13:21:52.043477-05:00 xps kernel: 6030.259060] IPv4: martian source 255.255.255.255 from 172.30.51.146, on dev p5p1
2015-12-03T13:21:52.043496-05:00 xps kernel: 6030.259093] ll header: 00000000: ff ff ff ff ff ff 60 fb 42 eb 42 5a 08 00 ......`.B.BZ..
2015-12-03T13:21:53.470982-05:00 xps kernel: 6031.687737] IPv4: martian source 255.255.255.255 from 172.30.51.158, on dev p5p1
2015-12-03T13:21:53.471013-05:00 xps kernel: 6031.687771] ll header: 00000000: ff ff ff ff ff ff 00 1f d0 23 8a 5e 08 00 .........#.^..
2015-12-03T13:21:54.433388-05:00 xps kernel: 6032.650994] IPv4: martian source 255.255.255.255 from 172.30.51.184, on dev p5p1
2015-12-03T13:21:54.433415-05:00 xps kernel: 6032.651019] ll header: 00000000: ff ff ff ff ff ff 48 5b 39 d3 f7 79 08 00 ......H[9..y..
2015-12-03T13:21:56.356033-05:00 xps kernel: [ 6034.575263] IPv4: martian source 255.255.255.255 from 172.30.51.221, on dev p5p1
2015-12-03T13:21:56.356068-05:00 xps kernel: 6034.575295] ll header: 00000000: ff ff ff ff ff ff 68 5b 35 95 a0 f7 08 00 ......h[5.....
2015-12-03T13:21:57.315377-05:00 xps kernel: [ 6035.535429] IPv4: martian source 255.255.255.255 from 172.30.51.34, on dev p5p1
2015-12-03T13:21:57.315414-05:00 xps kernel: 6035.535462] ll header: 00000000: ff ff ff ff ff ff e8 40 f2 e2 67 d3 08 00 .......@..g...
2015-12-03T13:21:58.875601-05:00 xps kernel: 6037.096968] IPv4: martian source 255.255.255.255 from 172.30.51.107, on dev p5p1
2015-12-03T13:21:58.875631-05:00 xps kernel: 6037.096999] ll header: 00000000: ff ff ff ff ff ff 00 50 b6 52 de 50 08 00 .......P.R.P..
which just keeps repeating over and over again.
/sbin/ethtool p5p1 returns:
Supported ports: TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Link partner advertised pause frame use: No
Link partner advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Cannot get wake-on-lan settings: Operation not permitted
Current message level: 0x00000033 (51)
drv probe ifdown ifup
Link detected: yes
How is the interface configured?
ip link
ip addr
ip route
ip link:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: p5p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000
link/ether 84:8f:69:b1:9f:4d brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT qlen 1000
link/ether 74:e5:0b:30:0c:50 brd ff:ff:ff:ff:ff:ff
4: wlp0s29u1u2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT qlen 1000
link/ether 7c:dd:90:16:ca:27 brd ff:ff:ff:ff:ff:ff
ip addr:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: p5p1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP qlen 1000
link/ether 84:8f:69:b1:9f:4d brd ff:ff:ff:ff:ff:ff
inet6 fe80::868f:69ff:feb1:9f4d/64 scope link
valid_lft forever preferred_lft forever
3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 74:e5:0b:30:0c:50 brd ff:ff:ff:ff:ff:ff
inet6 fe80::76e5:bff:fe30:c50/64 scope link
valid_lft forever preferred_lft forever
4: wlp0s29u1u2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
link/ether 7c:dd:90:16:ca:27 brd ff:ff:ff:ff:ff:ff
inet6 fe80::7edd:90ff:fe16:ca27/64 scope link
valid_lft forever preferred_lft forever
ip route: nothing returned.
Note: this is with wifi disabled and the ethernet plugged in. I’m using the wlp0s29u1u2 connection to actually reply to this message (external wifi antenna) although the wlp3s0 connection works as well.
So I guess no one knows what is happening? First it was the DNS for DHCP not working (still isn’t, I have to manually assign it) and now my ethernet connection doesn’t work, but wifi does.
It’s not clear yet why no IPv4 address is assigned.
- Do you have Network Manager controlling the network interfaces? Use the following to confirm to us
nmcli d
- You could observe what NM is doing by opening a terminal and watching NetworkManager logging with
sudo tail -f /var/log/NetworkManager
Then connect the ethernet cable. CTRL-C to terminate. Copy/paste any relevant output.
- Also, with the ethernet interface connected, let’s see how dhclient is reported…
systemctl status NetworkManager
Thanks for replying.
nmcli d:
DEVICE TYPE STATE
p5p1 802-3-ethernet disconnected
wlp3s0 802-11-wireless connected
This is with the ethernet plugged in.
Network Manager log:
2015-12-04T22:35:19.225585-05:00 xps NetworkManager[853]: <info> Policy set '08FX06003025' (wlp3s0) as default for IPv4 routing and DNS.
2015-12-04T22:35:19.227705-05:00 xps NetworkManager[853]: <info> Activation (wlp3s0) successful, device activated.
2015-12-04T22:35:19.365620-05:00 xps NetworkManager[853]: dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
2015-12-04T22:35:19.366012-05:00 xps NetworkManager[853]: dns-resolver: You can find my version in /etc/resolv.conf.netconfig
2015-12-04T22:35:19.366228-05:00 xps NetworkManager[853]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
2015-12-04T22:35:19.366424-05:00 xps NetworkManager[853]: You can find my version in /etc/resolv.conf.netconfig ...
2015-12-04T22:36:39.175849-05:00 xps NetworkManager[853]: <info> (p5p1): carrier now ON (device state 20)
2015-12-04T22:36:39.176945-05:00 xps NetworkManager[853]: <info> (p5p1): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Note DNS does not actually work via DHCP, the only reason I can access anything is because of the manual entry in resolv.conf
systemctl status NetworkManager:
NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
Active: active (running) since Fri 2015-12-04 19:42:14 EST; 3h 0min ago
Main PID: 853 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
├─ 853 /usr/sbin/NetworkManager --no-daemon
└─6731 /sbin/dhclient -d -sf /usr/lib/nm-dhcp-client.action -pf /var/run/dhclient-wlp3s0.pid -lf /var/lib/NetworkManager/dhclient-8b75935f-1643-4d6...
If I turn off wifi and leave the ethernet plugged in, the last line disappears.
This is problematic
2015-12-04T22:36:39.176945-05:00 xps NetworkManager[853]: <info> (p5p1): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
More details about your ethernet hardware could be useful
/usr/sbin/hwinfo --netcard