Connection to WiFi Extender has no Internet access since upgrading to Mint 19

Georgepie · 09-06-2018, 10:09 AM

Just upgraded my desktop to Linux Mint 19 from 18.3 .
Use a WiFI range extender because the router WiFi signal is not very strong and therefore performance is poor.
When I connect to the range extender WiFi, very strong signal, the browsers (Firefox, Chrome) say no Internet connection.
If I connect directly to the router WiFi , two bars signal at best, the Internet connection works fine , except that it is a bit slow.
Note 1: All this set up was working fine in Mint 18.3 before the upgrade.
Note 2: next to the Linux desktop, I have a Windows 10 laptop that connects to the Wifi extender without any Internet issues .

ferrari · 09-06-2018, 07:33 PM

Compare the following for the case when your connected via the extender vs direct to the AP router...

Code:

iwconfig wlan0

Code:

ip a

Code:

ip r

Code:

sudo grep -i name /etc/resolv.conf

BTW, if using NetworkManager, all this information can be go with the single command...

Code:

nmcli

Post the details here if you're not sure of their significance for each case.

Georgepie · 09-06-2018, 09:58 PM

iwconfig wlan0

Extender: wlan0: error fetching interface information: Device not found
Direct: wlan0 No such device

ip a

Extender:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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
2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether c4:a8:1d:80:0f:43 brd ff:ff:ff:ff:ff:ff
inet6 2001:1970:549c:a600:4999:3ada:d509:3f2e/64 scope global dynamic noprefixroute
valid_lft 3599sec preferred_lft 3599sec
inet6 fe80::3cba:80f0:91a9:58b0/64 scope link noprefixroute
valid_lft forever preferred_lft forever

Direct:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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
2: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether c4:a8:1d:80:0f:43 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.22/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp2s0
valid_lft 3520sec preferred_lft 3520sec
inet6 2001:1970:549c:a600:c835:2132:22a4:6328/64 scope global temporary dynamic
valid_lft 3599sec preferred_lft 3599sec
inet6 2001:1970:549c:a600:f9be:1184:d955:4ada/64 scope global dynamic mngtmpaddr noprefixroute
valid_lft 3599sec preferred_lft 3599sec
inet6 fe80::7980:1e6e:60cd:7467/64 scope link noprefixroute
valid_lft forever preferred_lft forever
10: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UNKNOWN group default qlen 100
link/none
inet 10.41.0.42 peer 10.41.0.41/32 scope global tun0
valid_lft forever preferred_lft forever

ip r

Extender: <blank>
Direct:

0.0.0.0/1 via 10.41.0.41 dev tun0
default via 192.168.0.1 dev wlp2s0 proto dhcp metric 20600
10.41.0.1 via 10.41.0.41 dev tun0
10.41.0.41 dev tun0 proto kernel scope link src 10.41.0.42
128.0.0.0/1 via 10.41.0.41 dev tun0
169.254.0.0/16 dev wlp2s0 scope link metric 1000
185.92.26.101 via 192.168.0.1 dev wlp2s0
192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.22 metric 600

sudo grep -i name /etc/resolv.conf

Extender: nameserver 127.0.0.53
Direct: nameserver 10.41.0.1

ferrari · 09-06-2018, 10:31 PM

Ok, you're not getting a DHCP-assigned IP address when connecting via the extender. How is your network configuration defined for the extender? Are you using NetworkManager or some other utility?

Georgepie · 09-06-2018, 11:25 PM

I used the utility served from the range extender itself. Selected my 2.4 and 5Ghz networks from my router and entered their passwords. Chose not to clone the settings, so the new networks have different SSIDs and passwords.
What puzzles me is that this setup was working with 18.3 and is currently working for the Windows laptop. Thank you.

ferrari · 09-06-2018, 11:36 PM

I'm not talking about your extender configuration though, I'm referring to your desktop network configuration. You could always examine the pertinent logs. Again, please tell us which network management tool you're using here. Network Manager, Wicd,....?

Georgepie · 09-07-2018, 06:06 AM

I use Network Manager.

Georgepie · 09-07-2018, 12:50 PM

I checked the NM logs using :

journalctl -f -u NetworkManager

Noticed a couple of things:

the Direct Connection (SSID: CB38DFD79DA3) issues a "Config: added 'auth_alg' value 'OPEN'" while activating the connection. The Extender Connection does not.
Also, the Direct Connection issues a DHCPREQUEST to start the process of obtaining the IP address.
The Extender Connection (SSID: Amped_REC33A_5.0) issues a DHCPDISCOVER on wlp2s0 , that eventually times out.

See details below.

====================== DIRECT CONNECTION ===================================

Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.2544] device (wlp2s0): disconnecting for new activation request.
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.2545] device (wlp2s0): state change: activated -> deactivating (reason 'new-activation', sys-iface-state: 'managed')
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.2546] manager: NetworkManager state is now DISCONNECTING
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.2603] audit: op="connection-activate" uuid="b3c553b9-a16a-4352-a885-28b39222bf4f" name="CB38DFD79DA3" pid=1784 uid=1000 result="success"
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.2607] device (wlp2s0): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.2618] dhcp6 (wlp2s0): canceled DHCP transaction
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.2706] manager: NetworkManager state is now DISCONNECTED
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.2714] device (wlp2s0): Activation: starting connection 'CB38DFD79DA3' (b3c553b9-a16a-4352-a885-28b39222bf4f)
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.2732] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.2734] manager: NetworkManager state is now CONNECTING
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.2746] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.4793] device (wlp2s0): Activation: (wifi) access point 'CB38DFD79DA3' has security, but secrets are required.
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.4794] device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.4800] sup-iface[0x5591e0584220,wlp2s0]: wps: type pbc start...
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <warn> [1536336802.4814] sup-iface[0x5591e0584220,wlp2s0]: connection disconnected (reason -3)
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.4815] device (wlp2s0): supplicant interface state: completed -> disconnected
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.4857] device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.4865] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.4868] device (wlp2s0): Activation: (wifi) connection 'CB38DFD79DA3' has security, and secrets exist. No new secrets needed.
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.4868] Config: added 'ssid' value 'CB38DFD79DA3'
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.4869] Config: added 'scan_ssid' value '1'
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.4869] Config: added 'bgscan' value 'simple:30:-80:86400'
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.4869] Config: added 'key_mgmt' value 'WPA-PSK'
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.4869] Config: added 'auth_alg' value 'OPEN'
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.4869] Config: added 'psk' value '<hidden>'
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.5124] device (wlp2s0): supplicant interface state: disconnected -> authenticating
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.5219] device (wlp2s0): supplicant interface state: authenticating -> associating
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.5310] device (wlp2s0): supplicant interface state: associating -> associated
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.5446] device (wlp2s0): supplicant interface state: associated -> 4-way handshake
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.5598] device (wlp2s0): supplicant interface state: 4-way handshake -> completed
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.5599] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'CB38DFD79DA3'.
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.5600] device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.5620] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Sep 07 12:13:22 roger-Mint NetworkManager[826]: <info> [1536336802.5644] dhcp4 (wlp2s0): dhclient started with pid 20426
Sep 07 12:13:22 roger-Mint dhclient[20426]: DHCPREQUEST of 192.168.0.22 on wlp2s0 to 255.255.255.255 port 67 (xid=0x4e1ec02)
Sep 07 12:13:23 roger-Mint dhclient[20426]: DHCPACK of 192.168.0.22 from 192.168.0.1
Sep 07 12:13:23 roger-Mint NetworkManager[826]: <info> [1536336803.1427] dhcp4 (wlp2s0): address 192.168.0.22
Sep 07 12:13:23 roger-Mint NetworkManager[826]: <info> [1536336803.1427] dhcp4 (wlp2s0): plen 24 (255.255.255.0)
Sep 07 12:13:23 roger-Mint NetworkManager[826]: <info> [1536336803.1427] dhcp4 (wlp2s0): gateway 192.168.0.1
Sep 07 12:13:23 roger-Mint NetworkManager[826]: <info> [1536336803.1428] dhcp4 (wlp2s0): lease time 3600
Sep 07 12:13:23 roger-Mint NetworkManager[826]: <info> [1536336803.1428] dhcp4 (wlp2s0): hostname 'roger-Mint'
Sep 07 12:13:23 roger-Mint NetworkManager[826]: <info> [1536336803.1428] dhcp4 (wlp2s0): nameserver '24.226.1.93'
Sep 07 12:13:23 roger-Mint NetworkManager[826]: <info> [1536336803.1428] dhcp4 (wlp2s0): nameserver '24.226.10.193'
Sep 07 12:13:23 roger-Mint NetworkManager[826]: <info> [1536336803.1428] dhcp4 (wlp2s0): state changed unknown -> bound
Sep 07 12:13:23 roger-Mint NetworkManager[826]: <info> [1536336803.1487] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 07 12:13:23 roger-Mint NetworkManager[826]: <info> [1536336803.1506] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 07 12:13:23 roger-Mint NetworkManager[826]: <info> [1536336803.1515] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 07 12:13:23 roger-Mint NetworkManager[826]: <info> [1536336803.1517] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 07 12:13:23 roger-Mint dhclient[20426]: bound to 192.168.0.22 -- renewal in 1707 seconds.
Sep 07 12:13:23 roger-Mint NetworkManager[826]: <info> [1536336803.1601] manager: NetworkManager state is now CONNECTED_SITE
Sep 07 12:13:23 roger-Mint NetworkManager[826]: <info> [1536336803.1603] policy: set 'CB38DFD79DA3' (wlp2s0) as default for IPv4 routing and DNS
Sep 07 12:13:23 roger-Mint NetworkManager[826]: <info> [1536336803.1607] device (wlp2s0): Activation: successful, device activated.
Sep 07 12:13:24 roger-Mint NetworkManager[826]: <info> [1536336804.8903] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Sep 07 12:13:24 roger-Mint NetworkManager[826]: <info> [1536336804.8926] dhcp6 (wlp2s0): dhclient started with pid 20535
Sep 07 12:13:24 roger-Mint NetworkManager[826]: <info> [1536336804.8938] policy: set 'CB38DFD79DA3' (wlp2s0) as default for IPv6 routing and DNS
Sep 07 12:13:25 roger-Mint dhclient[20535]: XMT: Info-Request on wlp2s0, interval 980ms.
Sep 07 12:13:26 roger-Mint dhclient[20535]: XMT: Info-Request on wlp2s0, interval 2050ms.
Sep 07 12:13:26 roger-Mint dhclient[20535]: RCV: Reply message on wlp2s0 from fe80::5e8f:e0ff:fe30:1a59.
Sep 07 12:13:26 roger-Mint NetworkManager[826]: <info> [1536336806.8447] dhcp6 (wlp2s0): nameserver '2001:1970:c06e:c0::94'
Sep 07 12:13:26 roger-Mint NetworkManager[826]: <info> [1536336806.8448] dhcp6 (wlp2s0): nameserver '2001:1970:c06e:c0::93'
Sep 07 12:13:26 roger-Mint NetworkManager[826]: <info> [1536336806.8448] dhcp6 (wlp2s0): nameserver '2001:1970:c0c0:6ec0::194'
Sep 07 12:13:26 roger-Mint NetworkManager[826]: <info> [1536336806.8448] dhcp6 (wlp2s0): state changed unknown -> bound
Sep 07 12:13:26 roger-Mint NetworkManager[826]: <info> [1536336806.8478] dhcp6 (wlp2s0): client pid 20535 exited with status 0
Sep 07 12:13:26 roger-Mint NetworkManager[826]: <info> [1536336806.8479] dhcp6 (wlp2s0): state changed bound -> done

========================== EXTENDER CONNECTION ===============================

Sep 07 12:15:53 roger-Mint NetworkManager[826]: <info> [1536336953.4592] manager: NetworkManager state is now CONNECTED_GLOBAL
Sep 07 12:18:27 roger-Mint NetworkManager[826]: <info> [1536337107.2759] device (wlp2s0): state change: activated -> deactivating (reason 'user-requested', sys-iface-state: 'managed')
Sep 07 12:18:27 roger-Mint NetworkManager[826]: <info> [1536337107.2761] manager: NetworkManager state is now DISCONNECTING
Sep 07 12:18:27 roger-Mint NetworkManager[826]: <info> [1536337107.2818] audit: op="device-disconnect" interface="wlp2s0" ifindex=2 pid=1784 uid=1000 result="success"
Sep 07 12:18:27 roger-Mint NetworkManager[826]: <info> [1536337107.2823] device (wlp2s0): state change: deactivating -> disconnected (reason 'user-requested', sys-iface-state: 'managed')
Sep 07 12:18:27 roger-Mint NetworkManager[826]: <info> [1536337107.2992] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP client pid 20426
Sep 07 12:18:27 roger-Mint NetworkManager[826]: <info> [1536337107.2992] dhcp4 (wlp2s0): state changed bound -> done
Sep 07 12:18:27 roger-Mint NetworkManager[826]: <info> [1536337107.2996] dhcp6 (wlp2s0): canceled DHCP transaction
Sep 07 12:18:27 roger-Mint NetworkManager[826]: <info> [1536337107.3013] manager: NetworkManager state is now DISCONNECTED
Sep 07 12:18:27 roger-Mint NetworkManager[826]: <warn> [1536337107.3227] sup-iface[0x5591e0584220,wlp2s0]: connection disconnected (reason -3)
Sep 07 12:18:27 roger-Mint NetworkManager[826]: <info> [1536337107.3228] device (wlp2s0): supplicant interface state: completed -> disconnected
Sep 07 12:18:37 roger-Mint NetworkManager[826]: <info> [1536337117.9909] device (wlp2s0): Activation: starting connection 'Amped_REC33A_5.0 1' (fe54f6cb-0bba-4735-9206-d0393ae4438b)
Sep 07 12:18:37 roger-Mint NetworkManager[826]: <info> [1536337117.9911] audit: op="connection-activate" uuid="fe54f6cb-0bba-4735-9206-d0393ae4438b" name="Amped_REC33A_5.0 1" pid=1784 uid=1000 result="success"
Sep 07 12:18:37 roger-Mint NetworkManager[826]: <info> [1536337117.9912] device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 07 12:18:37 roger-Mint NetworkManager[826]: <info> [1536337117.9914] manager: NetworkManager state is now CONNECTING
Sep 07 12:18:37 roger-Mint NetworkManager[826]: <info> [1536337117.9918] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 07 12:18:37 roger-Mint NetworkManager[826]: <info> [1536337117.9921] device (wlp2s0): Activation: (wifi) access point 'Amped_REC33A_5.0 1' has security, but secrets are required.
Sep 07 12:18:37 roger-Mint NetworkManager[826]: <info> [1536337117.9922] device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
Sep 07 12:18:37 roger-Mint NetworkManager[826]: <info> [1536337117.9923] sup-iface[0x5591e0584220,wlp2s0]: wps: type pbc start...
Sep 07 12:18:37 roger-Mint NetworkManager[826]: <info> [1536337117.9962] device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
Sep 07 12:18:37 roger-Mint NetworkManager[826]: <info> [1536337117.9968] device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Sep 07 12:18:37 roger-Mint NetworkManager[826]: <info> [1536337117.9972] device (wlp2s0): Activation: (wifi) connection 'Amped_REC33A_5.0 1' has security, and secrets exist. No new secrets needed.
Sep 07 12:18:37 roger-Mint NetworkManager[826]: <info> [1536337117.9973] Config: added 'ssid' value 'Amped_REC33A_5.0'
Sep 07 12:18:37 roger-Mint NetworkManager[826]: <info> [1536337117.9973] Config: added 'scan_ssid' value '1'
Sep 07 12:18:37 roger-Mint NetworkManager[826]: <info> [1536337117.9973] Config: added 'bgscan' value 'simple:30:-80:86400'
Sep 07 12:18:37 roger-Mint NetworkManager[826]: <info> [1536337117.9973] Config: added 'key_mgmt' value 'WPA-PSK'
Sep 07 12:18:37 roger-Mint NetworkManager[826]: <info> [1536337117.9973] Config: added 'psk' value '<hidden>'
Sep 07 12:18:38 roger-Mint NetworkManager[826]: <info> [1536337118.0134] device (wlp2s0): supplicant interface state: disconnected -> scanning
Sep 07 12:18:40 roger-Mint NetworkManager[826]: <info> [1536337120.6515] device (wlp2s0): supplicant interface state: scanning -> authenticating
Sep 07 12:18:40 roger-Mint NetworkManager[826]: <info> [1536337120.6579] device (wlp2s0): supplicant interface state: authenticating -> associating
Sep 07 12:18:40 roger-Mint NetworkManager[826]: <info> [1536337120.6693] device (wlp2s0): supplicant interface state: associating -> completed
Sep 07 12:18:40 roger-Mint NetworkManager[826]: <info> [1536337120.6693] device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'Amped_REC33A_5.0'.
Sep 07 12:18:40 roger-Mint NetworkManager[826]: <info> [1536337120.6695] device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Sep 07 12:18:40 roger-Mint NetworkManager[826]: <info> [1536337120.6699] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Sep 07 12:18:40 roger-Mint NetworkManager[826]: <info> [1536337120.6721] dhcp4 (wlp2s0): dhclient started with pid 20793
Sep 07 12:18:40 roger-Mint dhclient[20793]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 3 (xid=0x656d8d43)
Sep 07 12:18:42 roger-Mint NetworkManager[826]: <info> [1536337122.4723] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
Sep 07 12:18:42 roger-Mint NetworkManager[826]: <info> [1536337122.4746] dhcp6 (wlp2s0): dhclient started with pid 20799
Sep 07 12:18:43 roger-Mint dhclient[20799]: XMT: Info-Request on wlp2s0, interval 1070ms.
Sep 07 12:18:43 roger-Mint dhclient[20793]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 3 (xid=0x656d8d43)
Sep 07 12:18:43 roger-Mint dhclient[20799]: RCV: Reply message on wlp2s0 from fe80::5e8f:e0ff:fe30:1a59.
Sep 07 12:18:43 roger-Mint NetworkManager[826]: <info> [1536337123.4021] dhcp6 (wlp2s0): nameserver '2001:1970:c06e:c0::94'
Sep 07 12:18:43 roger-Mint NetworkManager[826]: <info> [1536337123.4022] dhcp6 (wlp2s0): nameserver '2001:1970:c06e:c0::93'
Sep 07 12:18:43 roger-Mint NetworkManager[826]: <info> [1536337123.4022] dhcp6 (wlp2s0): nameserver '2001:1970:c0c0:6ec0::194'
Sep 07 12:18:43 roger-Mint NetworkManager[826]: <info> [1536337123.4022] dhcp6 (wlp2s0): state changed unknown -> bound
Sep 07 12:18:43 roger-Mint NetworkManager[826]: <info> [1536337123.4046] dhcp6 (wlp2s0): client pid 20799 exited with status 0
Sep 07 12:18:43 roger-Mint NetworkManager[826]: <info> [1536337123.4047] dhcp6 (wlp2s0): state changed bound -> done
Sep 07 12:18:44 roger-Mint NetworkManager[826]: <info> [1536337124.0191] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Sep 07 12:18:44 roger-Mint NetworkManager[826]: <info> [1536337124.0196] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Sep 07 12:18:44 roger-Mint NetworkManager[826]: <info> [1536337124.0199] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Sep 07 12:18:44 roger-Mint NetworkManager[826]: <info> [1536337124.0200] manager: NetworkManager state is now CONNECTED_LOCAL
Sep 07 12:18:44 roger-Mint NetworkManager[826]: <info> [1536337124.0237] manager: NetworkManager state is now CONNECTED_SITE
Sep 07 12:18:44 roger-Mint NetworkManager[826]: <info> [1536337124.0239] policy: set 'Amped_REC33A_5.0 1' (wlp2s0) as default for IPv6 routing and DNS
Sep 07 12:18:44 roger-Mint NetworkManager[826]: <info> [1536337124.0242] device (wlp2s0): Activation: successful, device activated.
Sep 07 12:18:46 roger-Mint dhclient[20793]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 6 (xid=0x656d8d43)
Sep 07 12:18:52 roger-Mint dhclient[20793]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 20 (xid=0x656d8d43)
Sep 07 12:19:12 roger-Mint dhclient[20793]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 7 (xid=0x656d8d43)
Sep 07 12:19:14 roger-Mint NetworkManager[826]: <info> [1536337154.3691] connectivity: (wlp2s0) timed out
Sep 07 12:19:19 roger-Mint dhclient[20793]: DHCPDISCOVER on wlp2s0 to 255.255.255.255 port 67 interval 15 (xid=0x656d8d43)
Sep 07 12:19:26 roger-Mint NetworkManager[826]: <warn> [1536337166.3688] dhcp4 (wlp2s0): request timed out
Sep 07 12:19:26 roger-Mint NetworkManager[826]: <info> [1536337166.3689] dhcp4 (wlp2s0): state changed unknown -> timeout
Sep 07 12:19:26 roger-Mint NetworkManager[826]: <info> [1536337166.3853] dhcp4 (wlp2s0): canceled DHCP transaction, DHCP client pid 20793
Sep 07 12:19:26 roger-Mint NetworkManager[826]: <info> [1536337166.3853] dhcp4 (wlp2s0): state changed timeout -> done

ferrari · 09-07-2018, 04:28 PM

Clearly DHCP traffic is not making it to/from DHCP server. I can only think that the extender is the cause of the issue here. Is it using WDS? Is the Windows machine connected at the same time?

Just in case this is relevant
http://www.tomshardware.com/answers/...d-devices.html

ferrari · 09-07-2018, 04:36 PM

What brand/model is the extender?

Georgepie · 09-07-2018, 08:25 PM

The extender is an Amped REC33A . Precisely the article you mentioned it's about an Amped extender, however from 4 years ago.

I'll do a bit more research about the use of WDS and also will make sure that the Windows laptop it's not using the Extender, although it was working always at the same time when I had 18.3 installed.

Georgepie · 09-08-2018, 06:13 PM

There is no mention of WDS in the Extender or Router (Arris cable modem/router) , so I decided to reset the Extender.
Changed the Extender SSIDs to make sure no other devices that may have been connected would be able to connect .

But the issue only got more weird. Now, SOME domains work: Facebook, Yahoo Mail, Google Search, Google Maps , CNN are the main examples.
However, when I click on a link that would take me to another application it will give me the "Unable to connect" message.

Then I connected to the Extender from the Windows laptop and it worked perfectly . Didn't make any difference in the Mint Desktop .
Incidentally, I can't connect to this forum if I am using the Extender .

Another anomaly I noted, can't access the Router (192.168.0.1) from the Desktop.

ferrari · 09-08-2018, 06:22 PM

Ok, but that reads like a possible name resolution issue to investigate now.

Is Mint using dnsmasq perhaps?
https://unix.stackexchange.com/quest...isable-dnsmasq

Code:

grep name /etc/resolv.conf

Georgepie · 09-08-2018, 06:36 PM

grep name /etc/resolv.conf

nameserver 127.0.0.53

There is no entry in /etc/NetworkManager/NetworkManager.conf for dnsmasq .

Also tried killall dnsmasq and it replied "no process found"

ferrari · 09-09-2018, 01:42 AM

Ok, it's likely that systemd-resolved is in use as described here...

http://manpages.ubuntu.com/manpages/...tc/resolv.conf

What is /etc/resolv.conf linked to?

Code:

ls -la /etc/resolv.conf

There's a bug report here... (but I'm not sure of its significance)...
https://github.com/systemd/systemd/issues/7009

Quote:

currently, there are two ways to set up your /etc/resolv.conf when using resolved. Either by symlinking it to /run/systemd/resolve/resolv.conf in which case all upstream DNS information (i.e. servers as well as DNS search lists) learnt by resolved is propagated to clients reading /etc/resolv.conf.

alternatively, /etc/resolv.conf can be linked to the static file /usr/lib/systemd/resolv.conf which lists only 127.0.0.53 as DNS server and no search lists at all.