[artix-general] [atix-general][s6] dhcpcd upgrade from yesterday (9.2.0-1 -> 9.3.1-1) breaks network connectivity

epektasis rptnix at amerytel.net
Wed Oct 28 19:26:06 CET 2020


On Wed, Oct 28, 2020 at 12:14:07PM -0600, Javier via artix-general wrote:
> Hello !
> 
> Yesterday's artix upgrade to 9.3.1-1 made my system unable to connect to internet.  I'm using s6 as the init+supervisor system, however I'm not sure if s6 related at all...
> 
> See an example from the dhcpcd log when things go well for the wired interface:
> 
> > 2020-10-27 09:03:13.869956263  dhcpcd-9.2.0 starting
> > 2020-10-27 09:03:13.879800273  dev: loaded udev
> > 2020-10-27 09:03:13.881029666  DUID 00:04:59:12:9a:dd:f0:4f:11:e5:b9:11:62:cb:f2:00:40:19
> > 2020-10-27 09:03:14.026207066  in-wireless-0: starting wpa_supplicant
> > 2020-10-27 09:03:14.416922259  no interfaces have a carrier
> > 2020-10-27 09:03:14.624504233  in-wired-0: waiting for carrier
> > 2020-10-27 09:03:14.624513121  in-wireless-0: waiting for carrier
> > 2020-10-27 09:03:14.624515598  in-wireless-0: carrier acquired
> > 2020-10-27 09:03:14.632753120  in-wireless-0: IAID 00:bb:a5:3f
> > 2020-10-27 09:03:14.633079060  in-wireless-0: adding address fe80::55a:5374:22a4:4ce2
> > 2020-10-27 09:03:14.633083352  in-wireless-0: carrier lost
> > 2020-10-27 09:03:14.660219526  in-wireless-0: deleting address fe80::55a:5374:22a4:4ce2
> > 2020-10-27 09:03:18.137935449  in-wireless-0: carrier acquired
> > 2020-10-27 09:03:18.139197166  in-wireless-0: connected to Access Point `sanctuary'
> > 2020-10-27 09:03:18.147796420  in-wireless-0: IAID 00:bb:a5:3f
> > 2020-10-27 09:03:18.147802890  in-wireless-0: adding address fe80::19db:fef7:609f:47ff
> > 2020-10-27 09:03:18.263813925  in-wireless-0: soliciting an IPv6 router
> > 2020-10-27 09:03:19.402400033  in-wireless-0: rebinding lease of 192.168.0.24
> > 2020-10-27 09:03:19.644613342  in-wireless-0: Router Advertisement from fe80::1
> > 2020-10-27 09:03:19.644802937  in-wireless-0: adding default route via fe80::1
> > 2020-10-27 09:03:19.657035056  in-wireless-0: requesting DHCPv6 information
> > 2020-10-27 09:03:20.747816742  in-wireless-0: REPLY6 received from fe80::1
> > 2020-10-27 09:03:20.747824363  in-wireless-0: refresh in 86400 seconds
> > 2020-10-27 09:03:24.402209561  in-wireless-0: DHCP lease expired
> > 2020-10-27 09:03:24.413276276  in-wireless-0: soliciting a DHCP lease
> > 2020-10-27 09:03:24.830652588  in-wired-0: carrier acquired
> > 2020-10-27 09:03:24.840584702  in-wired-0: IAID fd:a9:93:88
> > 2020-10-27 09:03:24.840591981  in-wired-0: adding address fe80::ae2b:a054:4551:ee66
> > 2020-10-27 09:03:25.065260761  in-wired-0: rebinding lease of 192.168.0.16
> > 2020-10-27 09:03:25.203570739  in-wired-0: soliciting an IPv6 router
> > 2020-10-27 09:03:26.260790434  in-wired-0: Router Advertisement from fe80::1
> > 2020-10-27 09:03:26.260798242  in-wired-0: adding default route via fe80::1
> > 2020-10-27 09:03:26.294797913  in-wired-0: requesting DHCPv6 information
> > 2020-10-27 09:03:26.532352407  in-wireless-0: offered 192.168.0.24 from 192.168.0.1
> > 2020-10-27 09:03:26.615673549  in-wired-0: probing address 192.168.0.16/24
> > 2020-10-27 09:03:26.712230315  in-wireless-0: probing address 192.168.0.24/24
> > 2020-10-27 09:03:27.351498115  in-wired-0: REPLY6 received from fe80::1
> > 2020-10-27 09:03:27.351512179  in-wired-0: refresh in 86400 seconds
> > 2020-10-27 09:03:30.957113321  in-wired-0: leased 192.168.0.16 for 259200 seconds
> > 2020-10-27 09:03:30.957999941  in-wired-0: adding route to 192.168.0.0/24
> > 2020-10-27 09:03:30.958096069  in-wired-0: adding default route via 192.168.0.1
> > 2020-10-27 09:03:31.259857632  in-wireless-0: leased 192.168.0.24 for 259200 seconds
> > 2020-10-27 09:03:31.261634923  in-wireless-0: adding route to 192.168.0.0/24
> > 2020-10-27 09:03:31.261755045  in-wireless-0: adding default route via 192.168.0.1
> 
> The logs for Today with current dhcpcd version (9.3.1-1):
> 
> > 2020-10-28 11:32:40.049433743  dhcpcd-9.3.1 starting
> > 2020-10-28 11:32:40.058365491  dev: loaded udev
> > 2020-10-28 11:32:40.059291853  DUID 00:04:59:12:9a:dd:f0:4f:11:e5:b9:11:62:cb:f2:00:40:19
> > 2020-10-28 11:32:40.212571619  in-wireless-0: starting wpa_supplicant
> > 2020-10-28 11:32:40.600666932  no interfaces have a carrier
> > 2020-10-28 11:32:40.600941554  ps_ctl_listen: read: Success
> > 2020-10-28 11:36:02.941921111  dhcpcd_signal_cb: write: Connection refused
> > 2020-10-28 11:36:02.990960188  main: control_open: Connection refused
> 
> It doesn't show nothing else.  I do have the wpa_supplicant hook enabled:
> 
> % ls -l /usr/lib/dhcpcd/dhcpcd-hooks/10-wpa_supplicant                                                                                                         
> lrwxrwxrwx 1 root root 45 Oct  3 14:51 /usr/lib/dhcpcd/dhcpcd-hooks/10-wpa_supplicant -> ../../../share/dhcpcd/hooks/10-wpa_supplicant
> 
> But I removed it, and restarted dhcpcd, and even rebooted the machine, and still no connection.  My dhcpcd.conf is almost the same as the vanilla from stock:
> 
> > % 'grep' '^[ \t]*[^#]' /etc/dhcpcd.conf                                                                                                                        
> > hostname
> > duid
> > persistent
> > vendorclassid
> > option domain_name_servers, domain_name, domain_search
> > option classless_static_routes
> > option interface_mtu
> > option host_name
> > option ntp_servers
> > option rapid_commit
> > require dhcp_server_identifier
> > slaac private
> > noipv4ll
> > timeout 50
> 
> By reverting back to the prior version, 9.2.0-1, I got things back to normal:
> 
> > 2020-10-28 11:56:01.969880459  dhcpcd-9.2.0 starting
> > 2020-10-28 11:56:01.970929130  dev: loaded udev 
> > 2020-10-28 11:56:01.971065511  DUID 00:04:59:12:9a:dd:f0:4f:11:e5:b9:11:62:cb:f2:00:40:19
> > 2020-10-28 11:56:02.010037446  in-wireless-0: connected to Access Point `sanctuary'
> > 2020-10-28 11:56:02.202507297  in-wired-0: waiting for carrier
> > 2020-10-28 11:56:02.202628779  in-wireless-0: IAID 00:bb:a5:3f
> > 2020-10-28 11:56:02.206314308  in-wireless-0: adding address fe80::19db:fef7:609f:47ff
> > 2020-10-28 11:56:02.364994148  in-wireless-0: rebinding lease of 192.168.0.24
> > 2020-10-28 11:56:03.059838820  in-wireless-0: soliciting an IPv6 router
> > 2020-10-28 11:56:03.504530156  in-wireless-0: Router Advertisement from fe80::1
> > 2020-10-28 11:56:03.504542110  in-wireless-0: adding default route via fe80::1
> > 2020-10-28 11:56:03.520061745  in-wireless-0: requesting DHCPv6 information
> > 2020-10-28 11:56:04.593207041  in-wireless-0: REPLY6 received from fe80::1
> > 2020-10-28 11:56:04.593242286  in-wireless-0: refresh in 86400 seconds
> > 2020-10-28 11:56:06.845352738  in-wireless-0: probing address 192.168.0.24/24
> > 2020-10-28 11:56:11.608911648  in-wireless-0: leased 192.168.0.24 for 259200 seconds
> > 2020-10-28 11:56:11.611791616  in-wireless-0: adding route to 192.168.0.0/24
> > 2020-10-28 11:56:11.612516674  in-wireless-0: adding default route via 192.168.0.1
> > 2020-10-28 11:56:16.183005554  in-wired-0: carrier acquired
> > 2020-10-28 11:56:16.191543443  in-wired-0: IAID fd:a9:93:88
> > 2020-10-28 11:56:16.191551951  in-wired-0: adding address fe80::ae2b:a054:4551:ee66
> > 2020-10-28 11:56:17.035790462  in-wired-0: soliciting an IPv6 router
> > 2020-10-28 11:56:17.520913584  in-wired-0: Router Advertisement from fe80::1
> > 2020-10-28 11:56:17.523315183  in-wired-0: adding default route via fe80::1
> > 2020-10-28 11:56:17.565570851  in-wired-0: requesting DHCPv6 information
> > 2020-10-28 11:56:18.187051807  in-wired-0: rebinding lease of 192.168.0.16
> > 2020-10-28 11:56:18.240924167  in-wired-0: probing address 192.168.0.16/24
> > 2020-10-28 11:56:18.626356218  in-wired-0: REPLY6 received from fe80::1
> > 2020-10-28 11:56:18.626413187  in-wired-0: refresh in 86400 seconds
> > 2020-10-28 11:56:23.080211500  in-wired-0: leased 192.168.0.16 for 259200 seconds
> > 2020-10-28 11:56:23.083105375  in-wired-0: adding route to 192.168.0.0/24
> > 2020-10-28 11:56:23.083141845  in-wired-0: adding default route via 192.168.0.1
> 
> Is there something wrong with dhcpcd version 9.3.1-1, or something missing from dhcpcd-s6 after the upgrade?  Or something new is required that I'm missing to get dhcpcd 9.3.1-1 working?
> 
> Thanks !
> 
> -- 
> Javier
> 

I don't think the problem is with dhcpcd because I upgraded to that version
last night (and booted up this morning) and my networking presented no
troubles.  But then, I do not use wireless.
	E.




More information about the artix-general mailing list