You are not logged in.
Hello. At a coffee shop and seeing some weird behavior.
I can't ping IPv4 addresses.
$ ping -c 1 8.8.8.8
ping: connect: La red es inaccesible
I can, however, ping IPv6 addresses just fine.
$ ping -c 1 2001:4860:4860::8888
PING 2001:4860:4860::8888(2001:4860:4860::8888) 56 data bytes
64 bytes from 2001:4860:4860::8888: icmp_seq=1 ttl=47 time=25.9 ms
--- 2001:4860:4860::8888 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 25.879/25.879/25.879/0.000 ms
Buut, looks like I can curl IPv4 addresses. Also, Firefox works 100% fine.
$ curl -sL http://ipv4.tlund.se | head -n 1
<!DOCTYPE html>
Here's my ip addr output.
$ ip addr
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
inet6 ::1/128 scope host
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 9c:b6:d0:96:26:6d brd ff:ff:ff:ff:ff:ff
inet6 2620:10d:c096:157::bc6/128 scope global dynamic noprefixroute
valid_lft 252138sec preferred_lft 187338sec
inet6 2620:10d:c096:157:90ec:ec09:afa3:ccb/64 scope global dynamic noprefixroute
valid_lft 119sec preferred_lft 119sec
inet6 fe80::6250:f110:f1dd:7112/64 scope link noprefixroute
valid_lft forever preferred_lft forever
Also, Spotify (aur) thinks there is no internet connection, even though there definitely is.
Anyone else run into similar issues? I'm using only NetworkManager for DHCP and DNS.
Last edited by 1ptb3b (2020-01-23 22:08:58)
Offline
Off the top of my head it looks as though you don't have an ipv4 address but you do have an ipv6 address.
That page you curled to supports both 4 and 6.
On that page are links that you can test specific to ipv4 or ipv6.
Last edited by Zod (2020-01-22 21:09:01)
Offline
I'm using only NetworkManager for DHCP and DNS.
Please post a complete system journal and see https://wiki.archlinux.org/index.php/Ne … HCP_client (NM recently changed their [edit: internal] dhcp4 implementation base and there're multiple issues reported with every update since then…)
Last edited by seth (2020-01-22 21:24:14)
Online
Here's the journalctl -t NetworkManager dump.
NetworkManager (version 1.22.4-1) is starting... (for the first time)
Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
manager[0x55a7e9d080f0]: monitoring kernel firmware directory '/lib/firmware'.
dns-mgr[0x55a7e9ce6240]: init: dns=default,systemd-resolved rc-manager=symlink
manager[0x55a7e9d080f0]: rfkill: Wi-Fi hardware radio set enabled
manager[0x55a7e9d080f0]: rfkill: WWAN hardware radio set enabled
Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-bluetooth.so)
Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-ovs.so)
Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-wwan.so)
Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-wifi.so)
Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-team.so)
Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-adsl.so)
manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
manager: Networking is enabled by state file
dhcp-init: Using DHCP client 'internal'
settings: Loaded settings plugin: keyfile (internal)
device (lo): carrier: link connected
manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
device (wlp2s0): driver supports Access Point (AP) mode
manager: (wlp2s0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/2)
rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.6/0000:02:00.0/ieee80211/phy0/rfkill1) (driver ath10k_pci)
ovsdb: No se pudo conectar: No existe el fichero o el directorio
device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
device (wlp2s0): set-hw-addr: set MAC address to BA:88:92:02:89:19 (scanning)
supplicant: wpa_supplicant running
device (wlp2s0): supplicant interface state: init -> starting
sup-iface[0x55a7e9d12930,wlp2s0]: supports 5 scan SSIDs
device (wlp2s0): supplicant interface state: starting -> ready
Wi-Fi P2P device controlled by interface wlp2s0 created
manager: (p2p-dev-wlp2s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/3)
device (p2p-dev-wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
device (p2p-dev-wlp2s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
sup-iface: failed to cancel p2p connect: P2P cancel failed
policy: auto-activating connection 'fbguest' (d97a5f90-25e9-4182-958d-3ecb335aee27)
device (wlp2s0): Activation: starting connection 'fbguest' (d97a5f90-25e9-4182-958d-3ecb335aee27)
device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
manager: NetworkManager state is now CONNECTING
device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
device (wlp2s0): Activation: (wifi) access point 'fbguest' has security, but secrets are required.
device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
device (wlp2s0): Activation: (wifi) connection 'fbguest' has security, and secrets exist. No new secrets needed.
Config: added 'ssid' value 'fbguest'
Config: added 'scan_ssid' value '1'
Config: added 'auth_alg' value 'OPEN'
Config: added 'psk' value '<hidden>'
device (wlp2s0): supplicant interface state: ready -> disconnected
device (p2p-dev-wlp2s0): supplicant management interface state: ready -> disconnected
device (wlp2s0): supplicant interface state: disconnected -> inactive
device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> inactive
device (wlp2s0): supplicant interface state: inactive -> scanning
device (p2p-dev-wlp2s0): supplicant management interface state: inactive -> scanning
device (wlp2s0): supplicant interface state: scanning -> authenticating
device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating
device (wlp2s0): supplicant interface state: authenticating -> associating
device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating
device (wlp2s0): supplicant interface state: associating -> completed
device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "fbguest"
device (p2p-dev-wlp2s0): supplicant management interface state: associating -> completed
device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
dhcp6 (wlp2s0): option dhcp6_domain_search => 'corp.tfbnw.net dhcp.thefacebook.com facebook.com fb.com tfbnw.net thefacebook.com'
dhcp6 (wlp2s0): option dhcp6_name_servers => '2001:4860:4860::64 2001:4860:4860::6464'
dhcp6 (wlp2s0): option ip6_address => '2620:10d:c096:157::bc6'
dhcp6 (wlp2s0): state changed unknown -> bound
device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
manager: NetworkManager state is now CONNECTED_LOCAL
manager: NetworkManager state is now CONNECTED_SITE
policy: set 'fbguest' (wlp2s0) as default for IPv6 routing and DNS
device (wlp2s0): Activation: successful, device activated.
manager: startup complete
manager: NetworkManager state is now CONNECTED_GLOBAL
agent-manager: agent[3661f1a3e3cd00d0,:1.105/org.gnome.Shell.NetworkAgent/1000]: agent registered
dhcp4 (wlp2s0): request timed out
dhcp4 (wlp2s0): state changed unknown -> timeout
policy: set 'fbguest' (wlp2s0) as default for IPv6 routing and DNS
Yeah, was reading the wiki. I'm going to experiment with other DHCP/DNS clients.
Offline
dhcp4 (wlp2s0): request timed out
dhcp4 (wlp2s0): state changed unknown -> timeout
You don't have an IPv4 address.
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Ooookay. Well, I switched out the DHCP and DNS clients. Buuut, nothing changed.
journalctl -t NetworkManager
NetworkManager (version 1.22.4-1) is starting... (for the first time)
Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf) (etc: dhcp-client.conf, dns.conf)
bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
manager[0x559d77a4e0f0]: monitoring kernel firmware directory '/lib/firmware'.
dns-mgr[0x559d77a2c240]: init: dns=systemd-resolved rc-manager=symlink, plugin=systemd-resolved
Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-bluetooth.so)
Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-ovs.so)
Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-wwan.so)
Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-wifi.so)
Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-team.so)
Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.22.4-1/libnm-device-plugin-adsl.so)
manager: Networking is enabled by state file
dhcp-init: Using DHCP client 'dhclient'
settings: Loaded settings plugin: keyfile (internal)
device (lo): carrier: link connected
manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
manager: startup complete
device (wlan0): driver supports Access Point (AP) mode
manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/2)
device (wlan0): interface index 2 renamed iface from 'wlan0' to 'wlp2s0'
device (wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
device (wlp2s0): set-hw-addr: set MAC address to 46:49:93:FD:DC:0E (scanning)
supplicant: wpa_supplicant running
device (wlp2s0): supplicant interface state: init -> starting
sup-iface[0x559d77a59120,wlp2s0]: supports 5 scan SSIDs
device (wlp2s0): supplicant interface state: starting -> ready
Wi-Fi P2P device controlled by interface wlp2s0 created
manager: (p2p-dev-wlp2s0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/3)
device (p2p-dev-wlp2s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
sup-iface: failed to cancel p2p connect: P2P cancel failed
device (p2p-dev-wlp2s0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
device (wlp2s0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
policy: auto-activating connection 'fbguest' (d97a5f90-25e9-4182-958d-3ecb335aee27)
device (wlp2s0): Activation: starting connection 'fbguest' (d97a5f90-25e9-4182-958d-3ecb335aee27)
device (wlp2s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
manager: NetworkManager state is now CONNECTING
device (wlp2s0): set-hw-addr: reset MAC address to 9C:B6:D0:96:26:6D (preserve)
device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
device (wlp2s0): Activation: (wifi) access point 'fbguest' has security, but secrets are required.
device (wlp2s0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
device (wlp2s0): state change: need-auth -> prepare (reason 'none', sys-iface-state: 'managed')
device (wlp2s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
device (wlp2s0): Activation: (wifi) connection 'fbguest' has security, and secrets exist. No new secrets needed.
Config: added 'ssid' value 'fbguest'
Config: added 'scan_ssid' value '1'
Config: added 'bgscan' value 'simple:30:-70:86400'
Config: added 'key_mgmt' value 'WPA-PSK WPA-PSK-SHA256 FT-PSK'
Config: added 'auth_alg' value 'OPEN'
Config: added 'psk' value '<hidden>'
device (wlp2s0): supplicant interface state: ready -> disconnected
device (p2p-dev-wlp2s0): supplicant management interface state: ready -> disconnected
device (wlp2s0): supplicant interface state: disconnected -> inactive
device (p2p-dev-wlp2s0): supplicant management interface state: disconnected -> inactive
device (wlp2s0): supplicant interface state: inactive -> scanning
device (p2p-dev-wlp2s0): supplicant management interface state: inactive -> scanning
device (wlp2s0): supplicant interface state: scanning -> authenticating
device (p2p-dev-wlp2s0): supplicant management interface state: scanning -> authenticating
device (wlp2s0): supplicant interface state: authenticating -> associating
device (p2p-dev-wlp2s0): supplicant management interface state: authenticating -> associating
device (wlp2s0): supplicant interface state: associating -> completed
device (wlp2s0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "fbguest"
device (p2p-dev-wlp2s0): supplicant management interface state: associating -> completed
device (wlp2s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
dhcp4 (wlp2s0): dhclient started with pid 1004
agent-manager: agent[f95b33e8265fe63a,:1.104/org.gnome.Shell.NetworkAgent/1000]: agent registered
dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
dhcp6 (wlp2s0): dhclient started with pid 1198
dhcp6 (wlp2s0): valid_lft 259200
dhcp6 (wlp2s0): preferred_lft 194400
dhcp6 (wlp2s0): address 2620:10d:c096:157::a20
dhcp6 (wlp2s0): nameserver '2001:4860:4860::64'
dhcp6 (wlp2s0): nameserver '2001:4860:4860::6464'
dhcp (wlp2s0): domain search 'corp.tfbnw.net.'
dhcp (wlp2s0): domain search 'dhcp.thefacebook.com.'
dhcp (wlp2s0): domain search 'facebook.com.'
dhcp (wlp2s0): domain search 'fb.com.'
dhcp (wlp2s0): domain search 'tfbnw.net.'
dhcp (wlp2s0): domain search 'thefacebook.com.'
dhcp6 (wlp2s0): option dad_wait_time => '0'
dhcp6 (wlp2s0): option dhcp6_client_id => '0:4:e8:64:7a:86:29:c5:12:ce:be:e7:83:8b:aa:5c:62:9'
dhcp6 (wlp2s0): option dhcp6_domain_search => 'corp.tfbnw.net. dhcp.thefacebook.com. facebook.com. fb.com. tfbnw.net. thefacebook.com.'
dhcp6 (wlp2s0): option dhcp6_name_servers => '2001:4860:4860::64 2001:4860:4860::6464'
dhcp6 (wlp2s0): option dhcp6_server_id => '0:1:0:1:25:24:de:59:0:50:56:ae:50:df'
dhcp6 (wlp2s0): option iaid => 'd0:96:26:6d'
dhcp6 (wlp2s0): option ip6_address => '2620:10d:c096:157::a20'
dhcp6 (wlp2s0): option ip6_prefixlen => '128'
dhcp6 (wlp2s0): option life_starts => '1579730564'
dhcp6 (wlp2s0): option max_life => '259200'
dhcp6 (wlp2s0): option preferred_life => '194400'
dhcp6 (wlp2s0): option rebind => '0'
dhcp6 (wlp2s0): option renew => '0'
dhcp6 (wlp2s0): option requested_dhcp6_client_id => '1'
dhcp6 (wlp2s0): option requested_dhcp6_domain_search => '1'
dhcp6 (wlp2s0): option requested_dhcp6_name_servers => '1'
dhcp6 (wlp2s0): option starts => '1579730564'
dhcp6 (wlp2s0): state changed unknown -> bound, event ID="d0:96:26:6d|1579730564"
device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
manager: NetworkManager state is now CONNECTED_LOCAL
manager: NetworkManager state is now CONNECTED_SITE
policy: set 'fbguest' (wlp2s0) as default for IPv6 routing and DNS
device (wlp2s0): Activation: successful, device activated.
manager: NetworkManager state is now CONNECTED_GLOBAL
dhcp4 (wlp2s0): request timed out
dhcp4 (wlp2s0): state changed unknown -> timeout
dhcp4 (wlp2s0): state changed timeout -> fail
This is my dhclient config.
$ cat /etc/dhclient.conf
interface "wlp2s0" {
send dhcp-client-identifier 9c:b6:d0:96:26:6d;
}
Could I be missing something in my config? Or could this be a router configuration error?
Last edited by 1ptb3b (2020-01-22 23:00:23)
Offline
Please post the complete system journal, not some filter.
"sudo journalctl -b", the presented output notably lacks dhclient messages but also general context.
Did you first try w/o the dhclient.conf ?
Also check "sudo nmap --script broadcast-dhcp-discover" and yes: restarting consumer routers is a solution to many things ;-)
Online
Okay, here you go. The whole enchilada.
$ sudo journalctl --boot
# Turns out the complete system journal log is 3MB. I had trouble uploading it to arch
# forums and pastebin was too small. So I uploaded it to Google Drive.
# https://drive.google.com/file/d/1DZjP5xY2SgvvcaYQ4myll1Gv47XErNBq/view?usp=sharing
Additionally, I thought maybe it would be helpful to see the running units.
$ sudo systemctl list-units | grep "loaded active running"
init.scope loaded active running System and Service Manager
session-3.scope loaded active running Session 3 of user jaime
accounts-daemon.service loaded active running Accounts Service
bolt.service loaded active running Thunderbolt system service
colord.service loaded active running Manage, Install and Generate Color Profiles
dbus.service loaded active running D-Bus System Message Bus
gdm.service loaded active running GNOME Display Manager
lvm2-lvmetad.service loaded active running LVM2 metadata daemon
NetworkManager.service loaded active running Network Manager
polkit.service loaded active running Authorization Manager
rtkit-daemon.service loaded active running RealtimeKit Scheduling Policy Service
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-resolved.service loaded active running Network Name Resolution
systemd-timesyncd.service loaded active running Network Time Synchronization
systemd-udevd.service loaded active running udev Kernel Device Manager
udisks2.service loaded active running Disk Manager
upower.service loaded active running Daemon for power management
user@1000.service loaded active running User Manager for UID 1000
wpa_supplicant.service loaded active running WPA supplicant
dbus.socket loaded active running D-Bus System Message Bus Socket
lvm2-lvmetad.socket loaded active running LVM2 metadata daemon socket
systemd-journald-audit.socket loaded active running Journal Audit Socket
systemd-journald-dev-log.socket loaded active running Journal Socket (/dev/log)
systemd-journald.socket loaded active running Journal Socket
systemd-udevd-control.socket loaded active running udev Control Socket
systemd-udevd-kernel.socket loaded active running udev Kernel Socket
> Did you first try without the dhclient.conf?
I tried both with and without dhclient.conf, but there was no difference.
Here's the nmap output. It's interesting...
$ sudo nmap --script broadcast-dhcp-discover
Starting Nmap 7.80 ( https://nmap.org ) at 2020-01-23 10:20 PST
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 10.33 seconds
When I ran this same nmap command at home, I got back an IP offer. But seems like I can't find a DHCP server at this coffee shop?
Last edited by 1ptb3b (2020-01-23 18:42:07)
Offline
The nmap result suggests that the "coffee shop" doesn't provide IPv4, you'll need a gateway for domains w/o IPv6, eg. https://www.sixxs.net/tools/gateway/
Online
All right. I guess I'll call it. I'm going to say they only configured their DHCP server for IPv6 only.
Thanks everyone. Good practice debugging!
Offline
Maybe the coffee shop has a NAT64 setup, so you could try DNS64: https://developers.google.com/speed/pub … docs/dns64
Edit: Yes, the DNS servers NetworkManager received are exactly those google DNS64 servers. That is why nslookup / curl to ipv4-only domains is working while direct ping is not possible.
You should be able to manually translate ipv4 addresses to theNAT64 format like this
64:ff9b::8.8.8.8
Last edited by progandy (2020-01-23 23:42:57)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline