On Thursday, 01-08-2024 at 02:54 Łukasz Kalamłacki wrote:
> Hi,
>
>
> I did further test on VirtualBox and on KVM.
>
> VirtualBox on Linux somehow blocks IPv6 in bridged mode of the network
> configuration, so I created VM on KVM in bridged mode of the network
>
> brctl addbr bri0
>
> brctl addif bri0 eth1
>
> ifconfig bri0 up
>
> connected cable rj45, because we cannot add to the bridge wlan iface
>
>
> and after adding:
>
> auto enp8s0
>
> iface enp8s0 inet dhcp
>
> iface enp8s0 inet6 dhcp
>
> to /etc/network/interfaces
>
>
> and added to /etc/apt/sources.list removing all other lines
>
> deb http://deb.debian.org/debian/ sid main non-free-firmware
> deb-src http://deb.debian.org/debian/ sid main non-free-firmware
>
>
> and I did
>
> apt update
>
> apt full-upgrade
>
>
> and everything works surprisingly.
>
>
> But right now I have other issue with the system where previously I did
> the update wrong way, because on that machine ipv6 still does not work
> and after deleting everything besides sid from sources.lists and executing
>
> apt update
>
> apt full-upgrade
>
> ipv6 fails.
>
> Do you have solution for me?
Sadly not one that you want and need.
These two suggestions are how I have tried to update.
1) Back up data, reinstall with a format of the hard drive to make a clean
installation, then restore data.
2) (I do not know if this works, but) Back up data, reinstall without a format
of the hard drive to install the specific OS files and configurations, then
restore data.
3) (Hopefully someone has a useful suggestion better than my above suggestions,
can anyone make useful suggestions?.
I have always used suggestion 1) of a clean installation and setting up
everything again. Time consuming and painful. Teaches me to be careful and
check before doing any changes to my servers (well, most of the time. It has
been a while since i have destroyed a server).
One reason I like Virtual Machines is I can take a copy, shutdown the original,
load up the copy, make my changes, and if all goes well, then I can blow away
the copy, take another copy as a version backup, then make updates to the
original production copy and run this into the future.
The version backup is because I am paranoid about loosing a functioning server.
But all of this is only possible if you have plenty of space to have multiple
copies of your server VMs, and if running up the test server does not get
updated with production data that is important and which cannot be added to the
production server later on after you completed the testing.
If all your data is in the home folder, it is great if you can have the /home
on a separate partition, so you can do a reinstall while formatting the /
(root) partition, while not formatting the /home partition. But this has to be
the configuration of your server before there are any issues. And many systems
have configuration and data outside of the /home folder.
George.
>
>
> Best regards,
>
> Łukasz
>
> On 31.07.2024 12:51, George at Clug wrote:
> > Łukasz,
> >
> > I wanted to do another try, but this time stay with the initial Debian
> > installation, that is not alter /etc/network/interfaces file.
> >
> > So this time I just built Bookworm, then upgraded to Sid.
> >
> > Good news is I still cannot replicate your issue. Hopefully the issue
> > was because of the non sid sources.
> >
> > All the best with your fault finding, and thanks for the fun of
> > running up a couple of VMs. I really enjoy how VMs make testing easy.
> >
> > Below is my checking after building the Bookworm VM, to upgrading to
> > sid, and then checking once again.
> >
> > George.
> >
> > # cat /etc/network/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
> >
> > # The primary network interface
> > allow-hotplug enp1s0
> > iface enp1s0 inet dhcp
> >
> >
> > # ip -6 a
> > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
> > inet6 ::1/128 scope host noprefixroute
> > valid_lft forever preferred_lft forever
> > 2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
> > inet6 fe80::5054:ff:fe95:9109/64 scope link
> > valid_lft forever preferred_lft forever
> >
> >
> > # journalctl | grep -i ipv6
> > Jul 31 20:06:07 debsid1 kernel: Segment Routing with IPv6
> > Jul 31 20:06:07 debsid1 kernel: In-situ OAM (IOAM) with IPv6
> > Jul 31 20:06:07 debsid1 kernel: mip6: Mobile IPv6
> >
> > ===============================================================================
> > # nano /etc/apt/sources.list
> >
> > deb https://ftp.debian.org/debian/ sid contrib main non-free
> > non-free-firmware
> > # deb-src https://ftp.debian.org/debian/ sid contrib main non-free
> > non-free-firmware
> >
> > # apt update && apt full-upgrade -y
> > # systemctl reboot
> >
> > # cat /etc/network/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
> >
> > # The primary network interface
> > allow-hotplug enp1s0
> > iface enp1s0 inet dhcp
> >
> >
> >
> > # ip -6 a
> > 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
> > inet6 ::1/128 scope host noprefixroute
> > valid_lft forever preferred_lft forever
> > 2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
> > inet6 fe80::5054:ff:fe95:9109/64 scope link proto kernel_ll
> > valid_lft forever preferred_lft forever
> >
> >
> > # journalctl | grep -i ipv6
> > Jul 31 20:06:07 debsid1 kernel: Segment Routing with IPv6
> > Jul 31 20:06:07 debsid1 kernel: In-situ OAM (IOAM) with IPv6
> > Jul 31 20:06:07 debsid1 kernel: mip6: Mobile IPv6
> > Jul 31 20:41:06 debsid1 kernel: Segment Routing with IPv6
> > Jul 31 20:41:06 debsid1 kernel: In-situ OAM (IOAM) with IPv6
> > Jul 31 20:41:06 debsid1 kernel: mip6: Mobile IPv6
> >
> >
> >
> > On Wednesday, 31-07-2024 at 18:15 Łukasz Kalamłacki wrote:
> >
> > Hi,
> >
> > Are you able to reproduce at your side? You can verify this on
> > VirtualBox even without DHCPv6 server. In normal circumstances you
> > should get timeout on dhclient but the BUG causes that Debian
> > should end immediately without timeout and with the error
> > mentioned in the first post in syslog.
> > So are you able to reproduce at your side?
> >
> > Best regards,
> > Łukasz
> >
> > śr., 31 lip 2024 o 10:06 George at Clug <c...@goproject.info>
> > napisał(a):
> >
> > Łukasz,
> >
> >
> > I wonder if the issue is that you are missing
> > "non-free-firmware" which provides the non-free drivers for
> > things like sound, network and WiFI devices?
> >
> > (Hopefully you only have 'sid' sources and no sources for
> > other versions, for example 'bookworm' or 'backports')
> >
> > It could help to at least add "non-free-firmware" even if
> > there is another issue?
> >
> >
> > https://gist.github.com/hakerdefo/124a37ca927018f8b52a72e316d160fa#file-sources-list
> >
> > <https://gist.github.com/hakerdefo/124a37ca927018f8b52a72e316d160fa#file-sources-list>
> > Debian Sid (Unstable) complete sources.list
> > deb https://ftp.debian.org/debian/
> > <https://ftp.debian.org/debian/> sid contrib main non-free
> > non-free-firmware
> > # deb-src https://ftp.debian.org/debian/
> > <https://ftp.debian.org/debian/> sid contrib main non-free
> > non-free-firmware
> >
> > Uncomment the deb-src line, if you want to enable the source
> > repos.
> >
> > George.
> >
> >
> > On Wednesday, 31-07-2024 at 16:33 Łukasz Kalamłacki wrote:
> > > Hi,
> > >
> > > I added only this to sources list:
> > >
> > > deb http://deb.debian.org/debian/
> > <http://deb.debian.org/debian/> sid main contrib non-free
> > >
> > > and nothing else
> > >
> > > Best regards,
> > > Łukasz
> > >
> > > śr., 31 lip 2024 o 00:50 George at Clug
> > <c...@goproject.info> napisał(a):
> > >
> > > >
> > > >
> > > > On Wednesday, 31-07-2024 at 06:01 Łukasz Kalamłacki wrote:
> > > > > Hello,
> > > > >
> > > > >
> > > > > I detected and issue with Debian SID and DHCP for IPv6.
> > > > >
> > > > >
> > > > > In my network I use DHCPv6 server which works fine on
> > stable versions of
> > > > > Debian or Trixie but when I add to sources.list sid
> > source and do update
> > > >
> > > > Please let us know what you have added and also what you
> > have in
> > > > "sources.list sid source"
> > > >
> > > > Did you add something (or change?) something to
> > /etc/apt/sources.list ?
> > > >
> > > > Did you change anything else?
> > > >
> > > > George.
> > > >
> > > >
> > > >
> > > > > and upgrade I get and error that:
> > > > >
> > > > > "Link local ipv6 for interface is not configured" in
> > syslog and
> > > > > systemctl is reporting failed networking service and
> > only ipv4
> > > > > addressing is available.
> > > > >
> > > > >
> > > > > configuration in /etc/network/interfaces
> > > > >
> > > > > auto enp0s3
> > > > >
> > > > > iface enp0s3 inet dhcp
> > > > >
> > > > > iface enp0s3 inet6 dhcp
> > > > >
> > > > >
> > > > > What is interesting when the system is already running I
> > can do:
> > > > >
> > > > > dhclient -6 enp0s3
> > > > >
> > > > > and I get ipv6 address correctly
> > > > >
> > > > >
> > > > > The problem is reproducible on Virtualbox: just install
> > testing Debian
> > > > > and add sid to source.list and do update/upgrade in apt.
> > > > >
> > > > >
> > > > > The issue is very strange because during upgrade to SID
> > I do not see
> > > > > installation of any networking packages.
> > > > >
> > > > >
> > > > > What do you think?
> > > > >
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Łukasz
> > > > >
> > > > >
> > > >
> > > >
> > >
> >
