You are not logged in.

Pages: 1

#1 2019-05-14 00:33:43

_JZA_
Member
Registered: 2014-08-28
Posts: 32

Issues resolving for ipv4 sites

I have this situation where I am able to locate sites that have IPV6 support like Google, Facebook, Youtube, even this forum, but failed on IPv4 only sites like Twitter and others.

I have done some journalctl and get the following:

May 13 19:31:06 kudu NetworkManager[765]: <info>  [1557793866.0216] manager: NetworkManager state is now CONNECTED_GLOBAL
May 13 19:31:06 kudu nm-dispatcher[18622]: req:4 'connectivity-change': new request (0 scripts)
May 13 19:31:06 kudu nm-dispatcher[18622]: req:4 'connectivity-change': completed: no scripts
May 13 19:31:06 kudu dhcpcd[26321]: wlp3s0: Router Advertisement from fe80::1
May 13 19:31:06 kudu dhcpcd[26321]: wlp3s0: adding address 2806:10a6:b:6354:8008:8e40:80c8:af8c/64
May 13 19:31:06 kudu dhcpcd[26321]: wlp3s0: adding route to 2806:10a6:b:6354::/64
May 13 19:31:06 kudu dhcpcd[26321]: wlp3s0: adding default route via fe80::1
May 13 19:31:06 kudu dhcpcd[26321]: wlp3s0: soliciting a DHCPv6 lease
May 13 19:31:06 kudu dhcpcd[26321]: wlp3s0: REPLY6 received from fe80::1
May 13 19:31:06 kudu dhcpcd[26321]: wlp3s0: adding address 2806:10a6:b:6354:f8cb:e06d:b79:abf3/128
May 13 19:31:06 kudu dhcpcd[26321]: wlp3s0: renew in 54000, rebind in 69120, expire in 86400 seconds
May 13 19:31:09 kudu NetworkManager[765]: <info>  [1557793869.6551] policy: set 'Dispositivos' (wlp3s0) as default for IPv6 routing and DNS
May 13 19:31:09 kudu NetworkManager[765]: <info>  [1557793869.7330] dhcp6 (wlp3s0): activation: beginning transaction (timeout in 45 seconds)
May 13 19:31:09 kudu NetworkManager[765]: <warn>  [1557793869.7331] device (wlp3s0): failure to start DHCPv6: failed to start client: Address already in use
May 13 19:31:09 kudu dhcpcd[26321]: wlp3s0: pid 0 deleted address 2806:10a6:b:6354:8008:8e40:80c8:af8c/64
May 13 19:31:09 kudu dhcpcd[26321]: wlp3s0: pid 0 deleted address 2806:10a6:b:6354:f8cb:e06d:b79:abf3/128
May 13 19:31:10 kudu dhcpcd[26321]: wlp3s0: leased 192.168.1.106 for 30 seconds
May 13 19:31:10 kudu dhcpcd[26321]: wlp3s0: adding route to 192.168.1.0/24
May 13 19:31:10 kudu dhcpcd[26321]: wlp3s0: adding default route via 192.168.1.65
May 13 19:31:12 kudu dhcpcd[26321]: wlp3s0: pid 765 deleted default route via fe80::1
May 13 19:31:12 kudu kdeconnectd[1051]: kdeconnect.core: Broadcasting identity packet
May 13 19:31:12 kudu systemd[1]: NetworkManager-dispatcher.service: Succeeded.

Last edited by _JZA_ (2019-05-14 00:35:22)

Offline

#2 2019-05-14 06:18:09

seth
Member
Registered: 2012-09-03
Posts: 51,240

Re: Issues resolving for ipv4 sites

I'm not sure whether you've DNS or routing issues (because hte log indicates neither) but w/ NM and dhcpcd you're running at least two concurrent network managing services.

Post the output of

systemctl list-unit-files --state=enabled

and then pick one service and disable the other two.

NM seems to only operate DHCPv6, if you (tried to) make it use dhcpcd instead of the internal dhcp client, please elaborate on the intended setup and also post a complete journal, not random excerpts.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2019-05-16 05:41:19

_JZA_
Member
Registered: 2014-08-28
Posts: 32

Re: Issues resolving for ipv4 sites

I get the following:

$ systemctl list-unit-files --state=enabled
UNIT FILE                                   STATE  
autovt@.service                             enabled
bluetooth.service                           enabled
dbus-org.bluez.service                      enabled
dbus-org.freedesktop.ModemManager1.service  enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
display-manager.service                     enabled
getty@.service                              enabled
haveged.service                             enabled
lightdm.service                             enabled
ModemManager.service                        enabled
NetworkManager-dispatcher.service           enabled
NetworkManager.service                      enabled
sshd.service                                enabled
systemd-timesyncd.service                   enabled
remote-fs.target                            enabled

16 unit files listed.

I looked for dhcpd but it was disabled, even thought journalctl -f shows

May 16 00:50:50 kudu dbus-daemon[772]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.14' (uid=0 pid=773 comm="/usr/bin/NetworkManager --no-daemon ")
May 16 00:50:50 kudu systemd[1]: Starting Network Manager Script Dispatcher Service...
May 16 00:50:50 kudu dbus-daemon[772]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
May 16 00:50:50 kudu systemd[1]: Started Network Manager Script Dispatcher Service.
May 16 00:50:50 kudu audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 16 00:50:50 kudu nm-dispatcher[20020]: req:1 'dhcp4-change' [wlp3s0]: new request (0 scripts)
May 16 00:50:50 kudu nm-dispatcher[20020]: req:1 'dhcp4-change' [wlp3s0]: completed: no scripts
May 16 00:50:50 kudu kernel: audit: type=1130 audit(1557985850.192:505): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 16 00:51:00 kudu systemd[1]: NetworkManager-dispatcher.service: Succeeded.
May 16 00:51:00 kudu audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 16 00:51:00 kudu kernel: audit: type=1131 audit(1557985860.358:506): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 16 00:51:04 kudu NetworkManager[773]: <info>  [1557985864.6513] dhcp4 (wlp3s0):   address 192.168.1.106
May 16 00:51:04 kudu NetworkManager[773]: <info>  [1557985864.6513] dhcp4 (wlp3s0):   plen 24
May 16 00:51:04 kudu NetworkManager[773]: <info>  [1557985864.6514] dhcp4 (wlp3s0):   expires in 30 seconds (at 1557985894)
May 16 00:51:04 kudu NetworkManager[773]: <info>  [1557985864.6514] dhcp4 (wlp3s0):   nameserver '192.168.1.65'
May 16 00:51:04 kudu NetworkManager[773]: <info>  [1557985864.6514] dhcp4 (wlp3s0):   router 192.168.1.65
May 16 00:51:04 kudu NetworkManager[773]: <info>  [1557985864.6515] dhcp4 (wlp3s0):   mtu 576
May 16 00:51:04 kudu NetworkManager[773]: <info>  [1557985864.6551] dhcp4 (wlp3s0): state changed bound -> bound
May 16 00:51:04 kudu dbus-daemon[772]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.14' (uid=0 pid=773 comm="/usr/bin/NetworkManager --no-daemon ")
May 16 00:51:04 kudu systemd[1]: Starting Network Manager Script Dispatcher Service...
May 16 00:51:04 kudu dbus-daemon[772]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
May 16 00:51:04 kudu systemd[1]: Started Network Manager Script Dispatcher Service.
May 16 00:51:04 kudu audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 16 00:51:04 kudu nm-dispatcher[20047]: req:1 'dhcp4-change' [wlp3s0]: new request (0 scripts)
May 16 00:51:04 kudu kernel: audit: type=1130 audit(1557985864.678:507): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 16 00:51:04 kudu nm-dispatcher[20047]: req:1 'dhcp4-change' [wlp3s0]: completed: no scripts
May 16 00:51:15 kudu systemd[1]: NetworkManager-dispatcher.service: Succeeded.

Last edited by _JZA_ (2019-05-16 05:52:05)

Offline

#4 2019-05-16 07:20:03

seth
Member
Registered: 2012-09-03
Posts: 51,240

Re: Issues resolving for ipv4 sites

That's the NM internal dhcp client, ie. you don't invoke dhcpcd from NM (or at least in that section, there's actually no trace of dhcpcd at all this time)
Please post a complete journal, "sudo journalct -b"

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#5 2019-05-16 07:30:55

_JZA_
Member
Registered: 2014-08-28
Posts: 32

Re: Issues resolving for ipv4 sites

The whole output is  too long to handle even for pastebin  16k lines
https://pastebin.com/0EzTCCMR

Last edited by _JZA_ (2019-05-16 07:31:32)

Offline

#6 2019-05-16 07:36:28

seth
Member
Registered: 2012-09-03
Posts: 51,240

Re: Issues resolving for ipv4 sites

Try 

sudo journalctl -b | curl -F 'f:1=<-' ix.io

There's again no trace of dhcpcd in that log (did you explicitly start it before the first log output?) but you get 30 second leases every 15 seconds! so something very fishy is going on here.

https://wiki.archlinux.org/index.php/Ne … HCP_client
But we need to determine whether this happens because there's interference from another dhcp client.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#7 2019-05-16 07:57:03

_JZA_
Member
Registered: 2014-08-28
Posts: 32

Re: Issues resolving for ipv4 sites

Nothing comes back from that command. 

$ sudo journalctl -b | curl -F 'f:1=<-' ix.io
curl: (7) Failed to connect to ix.io port 80: Connection timed out

I did a search on the 'complete log' also without catching it.

I do have that package:

$ locate dhcpcd
/etc/dhcpcd.conf
/usr/bin/dhcpcd
/usr/lib/dhcpcd
/usr/lib/dhcpcd/dev
/usr/lib/dhcpcd/dhcpcd-hooks
/usr/lib/dhcpcd/dhcpcd-run-hooks
/usr/lib/dhcpcd/dev/udev.so
/usr/lib/dhcpcd/dhcpcd-hooks/01-test
/usr/lib/dhcpcd/dhcpcd-hooks/02-dump
/usr/lib/dhcpcd/dhcpcd-hooks/20-resolv.conf
/usr/lib/dhcpcd/dhcpcd-hooks/30-hostname
/usr/lib/netctl/dhcp/dhcpcd
/usr/lib/systemd/system/dhcpcd.service
/usr/lib/systemd/system/dhcpcd@.service
/usr/share/dhcpcd
/usr/share/dhcpcd/hooks
/usr/share/dhcpcd/hooks/10-wpa_supplicant
/usr/share/dhcpcd/hooks/15-timezone
...
$ locate dhclient
/usr/lib/netctl/dhcp/dhclient
/usr/share/bash-completion/completions/dhclient
/usr/share/lxc/hooks/dhclient
/usr/share/lxc/hooks/dhclient-script

Last edited by _JZA_ (2019-05-16 07:59:49)

Offline

#8 2019-05-16 08:04:29

_JZA_
Member
Registered: 2014-08-28
Posts: 32

Re: Issues resolving for ipv4 sites

I did manually disabled NetworkManager-dispatcher.service to see if that fixed it but no change.

Offline

#9 2019-05-16 08:15:40

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,740

Re: Issues resolving for ipv4 sites

Read the links you are pointed to. You have to create a config file to make NetworkManager switch which dhcp client it uses.

Offline

#10 2019-05-16 08:24:00

_JZA_
Member
Registered: 2014-08-28
Posts: 32

Re: Issues resolving for ipv4 sites

Right I put the dhclient on the conf.d folder for Network manager and restarted the connection but still no change. Even pings and alternative loads, the journalctl -f has become less verbosed but still shows:

May 16 03:23:00 kudu dbus-daemon[772]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service not found.
May 16 03:23:15 kudu NetworkManager[773]: <info>  [1557994995.1122] dhcp4 (wlp3s0):   address 192.168.1.106
May 16 03:23:15 kudu NetworkManager[773]: <info>  [1557994995.1123] dhcp4 (wlp3s0):   plen 24
May 16 03:23:15 kudu NetworkManager[773]: <info>  [1557994995.1123] dhcp4 (wlp3s0):   expires in 30 seconds (at 1557995025)
May 16 03:23:15 kudu NetworkManager[773]: <info>  [1557994995.1123] dhcp4 (wlp3s0):   nameserver '192.168.1.65'
May 16 03:23:15 kudu NetworkManager[773]: <info>  [1557994995.1124] dhcp4 (wlp3s0):   router 192.168.1.65
May 16 03:23:15 kudu NetworkManager[773]: <info>  [1557994995.1124] dhcp4 (wlp3s0):   mtu 576
May 16 03:23:15 kudu NetworkManager[773]: <info>  [1557994995.1127] dhcp4 (wlp3s0): state changed bound -> bound
May 16 03:23:15 kudu dbus-daemon[772]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.14' (uid=0 pid=773 comm="/usr/bin/NetworkManager --no-daemon ")
May 16 03:23:15 kudu dbus-daemon[772]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service not found.
May 16 03:23:28 kudu NetworkManager[773]: <info>  [1557995008.7377] dhcp4 (wlp3s0):   address 192.168.1.106
May 16 03:23:28 kudu NetworkManager[773]: <info>  [1557995008.7377] dhcp4 (wlp3s0):   plen 24
May 16 03:23:28 kudu NetworkManager[773]: <info>  [1557995008.7378] dhcp4 (wlp3s0):   expires in 30 seconds (at 1557995038)
May 16 03:23:28 kudu NetworkManager[773]: <info>  [1557995008.7378] dhcp4 (wlp3s0):   nameserver '192.168.1.65'
May 16 03:23:28 kudu NetworkManager[773]: <info>  [1557995008.7378] dhcp4 (wlp3s0):   router 192.168.1.65
May 16 03:23:28 kudu NetworkManager[773]: <info>  [1557995008.7379] dhcp4 (wlp3s0):   mtu 576
May 16 03:23:28 kudu NetworkManager[773]: <info>  [1557995008.7382] dhcp4 (wlp3s0): state changed bound -> bound
May 16 03:23:28 kudu dbus-daemon[772]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.14' (uid=0 pid=773 comm="/usr/bin/NetworkManager --no-daemon ")
May 16 03:23:28 kudu dbus-daemon[772]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service not found.
May 16 03:23:42 kudu NetworkManager[773]: <info>  [1557995022.2566] dhcp4 (wlp3s0):   address 192.168.1.106
May 16 03:23:42 kudu NetworkManager[773]: <info>  [1557995022.2567] dhcp4 (wlp3s0):   plen 24
May 16 03:23:42 kudu NetworkManager[773]: <info>  [1557995022.2567] dhcp4 (wlp3s0):   expires in 30 seconds (at 1557995052)
May 16 03:23:42 kudu NetworkManager[773]: <info>  [1557995022.2567] dhcp4 (wlp3s0):   nameserver '192.168.1.65'
May 16 03:23:42 kudu NetworkManager[773]: <info>  [1557995022.2568] dhcp4 (wlp3s0):   router 192.168.1.65
May 16 03:23:42 kudu NetworkManager[773]: <info>  [1557995022.2568] dhcp4 (wlp3s0):   mtu 576
May 16 03:23:42 kudu NetworkManager[773]: <info>  [1557995022.2570] dhcp4 (wlp3s0): state changed bound -> bound
May 16 03:23:42 kudu dbus-daemon[772]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.14' (uid=0 pid=773 comm="/usr/bin/NetworkManager --no-daemon ")
May 16 03:23:42 kudu dbus-daemon[772]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit dbus-org.freedesktop.nm-dispatcher.service not found.

Offline

#11 2019-05-16 08:27:39

seth
Member
Registered: 2012-09-03
Posts: 51,240

Re: Issues resolving for ipv4 sites

Restarting the connection won't do, you've to restart the NM service.
In the new log, NM is still not using dhclient and you still have those whacko short leases.

Also re-enable the dispatcher and stop poking around.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB