Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

[Partially Solved] Bullseye: Generic Cloud Image: IPv6 broken

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
bkmetzler
Posts: 1
Joined: 2021-08-17 17:23

[Partially Solved] Bullseye: Generic Cloud Image: IPv6 broken

#1 Post by bkmetzler »

I've run into an issue where IPv6 seems to be broken on the generic Bullseye amd64 qcow2 image.
https://cdimage.debian.org/images/cloud ... md64.qcow2

When booting up with cloud-init, it seems to populate /etc/network/interfaces properly, but I am unable to ping either to or out of the instance via IPv6.

Upon investigation I see that the output of 'ip -6 route show' differ.

Debian 10:

Code: Select all

::1 dev lo proto kernel metric 256 pref medium
2001:XXXX:XXXX:XXXX::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth1 proto kernel metric 256 pref medium
Debian 11:

Code: Select all

::1 dev lo proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth1 proto kernel metric 256 pref medium
Any thoughts on why and how to get cloud-init to add the missing line?

Thanks in advance,
-Brian

Update 1:
Looking at the journalctl logs for networking.service, it is unable to bring up the primary network interface (eth0).

Code: Select all

Aug 17 17:48:20 bmetzler-debian11vendor-test ifup[1022]: RTNETLINK answers: File exists
Aug 17 17:48:20 bmetzler-debian11vendor-test ifup[1011]: ifup: failed to bring up eth0

Code: Select all

Aug 17 18:45:50 bmetzler-debian11vendor-test systemd[1]: Stopped Raise network interfaces.
Aug 17 18:45:50 bmetzler-debian11vendor-test systemd[1]: Starting Raise network interfaces...
Aug 17 18:45:50 bmetzler-debian11vendor-test ifup[743]: /etc/network/if-pre-up.d/cloud_inet6: 12: IF_TRY_DHCP: parameter not set
Aug 17 18:45:50 bmetzler-debian11vendor-test ifup[742]: run-parts: /etc/network/if-pre-up.d/cloud_inet6 exited with return code 2
Aug 17 18:45:50 bmetzler-debian11vendor-test ifup[700]: ifup: failed to bring up eth0
Aug 17 18:45:50 bmetzler-debian11vendor-test systemd[1]: networking.service: Main process exited, code=exited, status=1/FAILURE
Aug 17 18:45:50 bmetzler-debian11vendor-test systemd[1]: networking.service: Failed with result 'exit-code'.
Aug 17 18:45:50 bmetzler-debian11vendor-test systemd[1]: Failed to start Raise network interfaces.
Update 2:
I think this might be a duplicate of https://unix.stackexchange.com/question ... ch-file-or

Update 3:
The networking was not properly being set with the 'latest' linked image. The latest daily build does have that fixed.
https://salsa.debian.org/cloud-team/deb ... 84fe804f0c

Unfortunately, this still doesn't fix my issue of not being able to ping via ipv6. Still getting a "Destination unreachable: Address unreachable" when using 'ping -6 google.com'.

Update 4:
The default IPv6 route was not being added. Added the default route in manually, and everything works properly.

Code: Select all

ip -6 route add default dev eth0 via fe80::def
Now the question is, why isn't that default route being added in Debian 11, when it was in the Debian 10 image.
Last edited by bkmetzler on 2021-08-20 13:42, edited 1 time in total.

Post Reply