Bug#636508: Bug #636508
I've replaced netmask 64 with netmask 56 and it works perfectly now. Very odd that a wrong netmask causes this kind of malfunctioning of the entire networking, but glad it has been resolved! Thanks a bunch. On Fri, Aug 5, 2011 at 4:12 PM, Guus Sliepen wrote: > On Fri, Aug 05, 2011 at 03:44:41PM +0200, Wouter van Eekelen wrote: > > > Here is the output of all networking related commands I could think of. > > Please do not attach this information to the bug report since it contains > > private information. > > Ok. I think the problem is that ifup fails to bring up the interface > completely, a subsequent ifdown then doesn't do anything, and that means it > doesn't properly bring down the bond interface: > > > root@web1:~# ifdown bond0 > > ifdown: interface bond0 not configured > > root@web1:~# ifconfig bond0 down > > root@web1:~# ifup bond0 > > SIOCADDRT: No route to host > > Failed to bring up bond0. > > Notice the error message: "No route to host". I think the problem is in > this > part of your interfaces file (first 48 bits of the addresses are replaced > by > Xs): > > > # The primary network interface (IPv6) > > iface bond0 inet6 static > > address :::1::1 > > netmask 64 > > gateway ::::1 > > Notice however that the gateway address has ::1 after the last X, while the > interface address has :1::1 after the last X. That means the gateway > address > is not contained in the :::1::/64 subnet, and therefore there > is no > route to the gateway address. To work around it, you can replace the > gateway > option with: > >up /sbin/ip route add default via ::::1 dev bond0 onlink > > Why it works at boot time, I have no idea... > > -- > Met vriendelijke groet / with kind regards, > Guus Sliepen >
Bug#636508: Processed: Bug#636508: base: IPv6 + Bonding: many unexpected results
I'm using an up to date Squeeze 6.0.2, the version of ifenslave-2.6 is 1.1.0-17 On Fri, Aug 5, 2011 at 3:34 PM, Guus Sliepen wrote: > On Fri, Aug 05, 2011 at 03:08:15PM +0200, Wouter van Eekelen wrote: > > > That's odd, I would expect my configuration to work - since it's one for > > inet and inet6. > > What you are telling me sounds like a workaround instead of the correct > way > > of doing this. > > Hm, I tested it and it appears to work fine. I guess my own information is > outdated! > > Can you show me the output of the ifconfig and route commands as I > suggested, > and also copy&paste any output from the ifup and ifdown commands? > > -- > Met vriendelijke groet / with kind regards, > Guus Sliepen >
Bug#636508: Processed: Bug#636508: base: IPv6 + Bonding: many unexpected results
Dear Guus, That's odd, I would expect my configuration to work - since it's one for inet and inet6. What you are telling me sounds like a workaround instead of the correct way of doing this. Regardless, could you tell me which exact configuration I should use? I don't want to mess this up. Regards, Wouter van Eekelen On Fri, Aug 5, 2011 at 2:56 PM, Amaya wrote: > Hey Gus > > Thanks so much for looking into this. > > -- > .''`. Trouble always comes at the wrong time > : :' : > `. `' > `- Proudly running Debian GNU/Linux >
Bug#636508: base: Network configuration with IPv6 + Bonding gives many unexpected results
Package: base Severity: important Tags: squeeze I'm using this network configuration for IPv6 + bonding, but it isn't working as it should. I've replaced the IP addresses with xx.xx.xx.xx because this is a private system. # The loopback network interface auto lo iface lo inet loopback # The primary network interface (IPv4) auto bond0 iface bond0 inet static address xx.xx.xx.xx netmask 255.255.255.0 gateway xx.xx.xx.xx slaves eth0 eth1 bond_mode balance-tlb bond_miimon 100 bond_downdelay 200 bond_updelay 200 # The primary network interface (IPv6) iface bond0 inet6 static address :::1::1 netmask 64 gateway ::::1 up /sbin/ifconfig bond0 inet6 add :::1::2 up /sbin/ifconfig bond0 inet6 add :::1::3 up /sbin/ifconfig bond0 inet6 add :::1::4 up /sbin/ifconfig bond0 inet6 add :::1::5 up /sbin/ifconfig bond0 inet6 add :::1::6 up /sbin/ifconfig bond0 inet6 add :::1::7 up /sbin/ifconfig bond0 inet6 add :::1::8 up /sbin/ifconfig bond0 inet6 add :::1::9 up /sbin/ifconfig bond0 inet6 add :::1::10 up /sbin/ifconfig bond0 inet6 add :::1::11 up /sbin/ifconfig bond0 inet6 add :::1::12 up /sbin/ifconfig bond0 inet6 add :::1::13 up /sbin/ifconfig bond0 inet6 add :::1::14 up /sbin/ifconfig bond0 inet6 add :::1::15 up /sbin/ifconfig bond0 inet6 add :::1::16 up /sbin/ifconfig bond0 inet6 add :::1::17 up /sbin/ifconfig bond0 inet6 add :::1::18 up /sbin/ifconfig bond0 inet6 add :::1::19 up /sbin/ifconfig bond0 inet6 add :::1::20 When I reboot, everything is pinging besides the additional IPv6 addresses (the 'up /sbin/ifconfig' lines). When running these lines (without the 'up' bit) on SSH they all start pinging and work fine. Besides this, all networking related commands completely break networking and require a reboot. When I do '/etc/init.d/networking stop', all networking stops, but the bond0 device stays in ifconfig (not pinging) When I then do '/etc/init.d/networking start', all devices are added to ifconfig again, but still nothing pings When I then do 'ifup bond0', it says 'bond0 is not a configured device' When I do 'ifconfig bond0 down' it goes down and is gone from ifconfig When I do 'ifconfig bond0 up' it comes back in ifconfig and is not working So the two problems are that I need to keep rebooting for network changes and manually adding the additional IPv6 addresses. -- System Information: Debian Release: 6.0.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
