ma 4. marrask. 2024 klo 14.39 Athanasius (deb...@miggy.org) kirjoitti: > > On Sat, Nov 02, 2024 at 02:36:36PM +0200, Martin-Éric Racine wrote: > > la 2. marrask. 2024 klo 14.32 Athanasius (deb...@miggy.org) kirjoitti: > > > > > > On Sat, Nov 02, 2024 at 02:22:54PM +0200, Martin-Éric Racine wrote: > > > > Btw, I assume that you are the one who filed > > > > (https://github.com/NetworkConfiguration/dhcpcd/issues/100) upstream? > > > > > > Yes. > > > > Upstream has marked the issue as fixed. > > > > Anyhow, as I stated in my previous reply, if dhcpcd is used as an > > ifupdown backend via /etc/network/interfaces (i.e. only > > bin:dhcpcd-base is installed, not bin:dhcpcd) , it should run the > > ifup-d scripts the same way as dhclient did. > > OK, so I decided to check that on my system. > > 12:23:32 0$ dpkg -l dhcpc\* > Desired=Unknown/Install/Remove/Purge/Hold > | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Name Version Architecture Description > +++-==============-==================-============-============================> > un dhcpcd <none> <none> (no description available) > ii dhcpcd-base 1:10.1.0-1~bpo12+1 amd64 DHCPv4 and DHCPv6 > dual-stack> > un dhcpcd5 <none> <none> (no description available) > > root@emilia:/etc/network; > 12:24:57 0$ cat interfaces > # This file describes the network interfaces available on your system > # and how to activate them. For more information, see interfaces(5). > > source /etc/network/interfaces.d/* > > # The loopback network interface > auto lo > iface lo inet loopback > 12:25:20 0$ grep -Ev '^[#]' interfaces.d/lan0 > auto lan0 > iface lan0 inet dhcp > > > iface lan0 inet6 dhcp
Comment out the inet6 line. Does it work better now? Martin-Éric
