I have a computer on my lan running radvd, advertising an ipv6 /64. All my computers receive the advertisements and automatically configure their IP address. The problem is that my Xen server can''t ping or connect to any (with ping6, of course) other ipv6 addresses. It is able to ping and connect to ipv4 addresses. It can ping it''s own ipv6 address, but not any of the other ipv6 addresses on the lan. Other computers can ping the Xen server via ipv6. I''ve tried making iptables accept everything, but it still doesnt work. I am fairly certain that the problem definitely has to do with xen and the interfaces that it creates. Does anyone have any idea how to fix it? I''m really not sure where to begin, so any thoughts or pointers would be appreciated. For reference, here''s the output of "ip -6 route" from a lan computer where ipv6 is working fine: fe80::/64 dev eth0 metric 256 expires 21279594sec mtu 1280 advmss 1220 metric 10 4294967295 ff00::/8 dev eth0 metric 256 expires 21279594sec mtu 1280 advmss 1220 metric 10 4294967295 default via fe80::2e0:4cff:feaa:4eef dev eth0 proto kernel metric 1024 expires 1657sec mtu 1280 advmss 1220 metric 10 64 unreachable default dev lo proto none metric -1 error -101 advmss 1220 metric 10 255 And here''s the output of "ip -6 route" from my xen server: 2001:5c0:911e::/64 dev peth0 proto kernel metric 256 expires 21355494sec mtu 1280 advmss 1220 metric 10 4294967295 2001:5c0:911e::/64 dev xenbr0 proto kernel metric 256 expires 21474726sec mtu 1280 advmss 1220 metric 10 4294967295 2001:5c0:911e::/64 dev eth0 proto kernel metric 256 expires 21474726sec mtu 1280 advmss 1220 metric 10 4294967295 fe80::/64 dev xenbr0 metric 256 expires -119341sec mtu 1280 advmss 1220 metric 10 4294967295 fe80::/64 dev vif0.0 metric 256 expires -119341sec mtu 1500 advmss 1220 metric 10 4294967295 fe80::/64 dev peth0 metric 256 expires -119341sec mtu 1280 advmss 1220 metric 10 4294967295 fe80::/64 dev vif4.0 metric 256 expires -118883sec mtu 1500 advmss 1220 metric 10 4294967295 fe80::/64 dev eth0 metric 256 expires -790sec mtu 1280 advmss 1220 metric 10 4294967295 ff00::/8 dev xenbr0 metric 256 expires -119341sec mtu 1280 advmss 1220 metric 10 4294967295 ff00::/8 dev vif0.0 metric 256 expires -119341sec mtu 1500 advmss 1220 metric 10 4294967295 ff00::/8 dev peth0 metric 256 expires -119341sec mtu 1280 advmss 1220 metric 10 4294967295 ff00::/8 dev vif4.0 metric 256 expires -118883sec mtu 1500 advmss 1220 metric 10 4294967295 ff00::/8 dev eth0 metric 256 expires -790sec mtu 1280 advmss 1220 metric 10 4294967295 default via fe80::2e0:4cff:feaa:4eef dev xenbr0 proto kernel metric 1024 expires 1690sec mtu 1280 advmss 1220 metric 10 64 default via fe80::2e0:4cff:feaa:4eef dev eth0 proto kernel metric 1024 expires 1690sec mtu 1280 advmss 1220 metric 10 64 unreachable default dev lo proto none metric -1 error -101 advmss 1220 metric 10 255 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Removing the ipv6 routes from peth0 and xenbr0 seem to fix the problem. I used the following commands: ip -6 route del 2001:5c0:911e::/64 dev xenbr0 ip -6 route del 2001:5c0:911e::/64 dev peth0 I''m not sure why they are given routes in the first place. I''ll disable autoconfiguration on those devices to see if that fixes it. If anyone has any suggestions, let me know. On 7/27/06, Andrew Yates <andrewyates@gmail.com> wrote:> I have a computer on my lan running radvd, advertising an ipv6 /64. > All my computers receive the advertisements and automatically > configure their IP address. > The problem is that my Xen server can''t ping or connect to any (with > ping6, of course) other ipv6 addresses. It is able to ping and connect > to ipv4 addresses. It can ping it''s own ipv6 address, but not any of > the other ipv6 addresses on the lan. Other computers can ping the Xen > server via ipv6. I''ve tried making iptables accept everything, but it > still doesnt work. > > I am fairly certain that the problem definitely has to do with xen and > the interfaces that it creates. Does anyone have any idea how to fix > it? I''m really not sure where to begin, so any thoughts or pointers > would be appreciated. > > For reference, here''s the output of "ip -6 route" from a lan computer > where ipv6 is working fine: > fe80::/64 dev eth0 metric 256 expires 21279594sec mtu 1280 advmss > 1220 metric 10 4294967295 > ff00::/8 dev eth0 metric 256 expires 21279594sec mtu 1280 advmss > 1220 metric 10 4294967295 > default via fe80::2e0:4cff:feaa:4eef dev eth0 proto kernel metric > 1024 expires 1657sec mtu 1280 advmss 1220 metric 10 64 > unreachable default dev lo proto none metric -1 error -101 advmss > 1220 metric 10 255 > > And here''s the output of "ip -6 route" from my xen server: > 2001:5c0:911e::/64 dev peth0 proto kernel metric 256 expires > 21355494sec mtu 1280 advmss 1220 metric 10 4294967295 > 2001:5c0:911e::/64 dev xenbr0 proto kernel metric 256 expires > 21474726sec mtu 1280 advmss 1220 metric 10 4294967295 > 2001:5c0:911e::/64 dev eth0 proto kernel metric 256 expires > 21474726sec mtu 1280 advmss 1220 metric 10 4294967295 > fe80::/64 dev xenbr0 metric 256 expires -119341sec mtu 1280 advmss > 1220 metric 10 4294967295 > fe80::/64 dev vif0.0 metric 256 expires -119341sec mtu 1500 advmss > 1220 metric 10 4294967295 > fe80::/64 dev peth0 metric 256 expires -119341sec mtu 1280 advmss > 1220 metric 10 4294967295 > fe80::/64 dev vif4.0 metric 256 expires -118883sec mtu 1500 advmss > 1220 metric 10 4294967295 > fe80::/64 dev eth0 metric 256 expires -790sec mtu 1280 advmss 1220 > metric 10 4294967295 > ff00::/8 dev xenbr0 metric 256 expires -119341sec mtu 1280 advmss > 1220 metric 10 4294967295 > ff00::/8 dev vif0.0 metric 256 expires -119341sec mtu 1500 advmss > 1220 metric 10 4294967295 > ff00::/8 dev peth0 metric 256 expires -119341sec mtu 1280 advmss > 1220 metric 10 4294967295 > ff00::/8 dev vif4.0 metric 256 expires -118883sec mtu 1500 advmss > 1220 metric 10 4294967295 > ff00::/8 dev eth0 metric 256 expires -790sec mtu 1280 advmss 1220 > metric 10 4294967295 > default via fe80::2e0:4cff:feaa:4eef dev xenbr0 proto kernel metric > 1024 expires 1690sec mtu 1280 advmss 1220 metric 10 64 > default via fe80::2e0:4cff:feaa:4eef dev eth0 proto kernel metric > 1024 expires 1690sec mtu 1280 advmss 1220 metric 10 64 > unreachable default dev lo proto none metric -1 error -101 advmss > 1220 metric 10 255 >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Andrew On Thu, Jul 27, 2006 at 12:16:57PM -0400, Andrew Yates wrote:> Removing the ipv6 routes from peth0 and xenbr0 seem to fix the problem. > I used the following commands: > ip -6 route del 2001:5c0:911e::/64 dev xenbr0 > ip -6 route del 2001:5c0:911e::/64 dev peth0 > I''m not sure why they are given routes in the first place. I''ll > disable autoconfiguration on those devices to see if that fixes it. If > anyone has any suggestions, let me know.I also had problems using IPv6. After a domU bootup it took some random time (up to 2 hours) to start the configured addresses to work. If I configured the ips after bootup by hand (ifconfig) they worked fine. After some tcpdumping I noticed that the incoming packets went to a different MAC address than the outgoing came from. I then gave the virtual machine a static MAC address, and from then on it started working without any manual configuration. Maybe this helps you and kind regards Flavio Curti -- http://no-way.org/~fcu/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I also had problems using IPv6. After a domU bootup it took some random > time (up to 2 hours) to start the configured addresses to work. > > If I configured the ips after bootup by hand (ifconfig) they worked > fine. > > After some tcpdumping I noticed that the incoming packets went to a > different MAC address than the outgoing came from. > > I then gave the virtual machine a static MAC address, and from then on > it started working without any manual configuration.Would you mind pasting the networking part of your domU''s config file? I''d like to see exactly how you have it setup. Thanks, Andrew _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Andrew On Tue, Aug 01, 2006 at 12:43:55AM -0400, Andrew Yates wrote:> >I also had problems using IPv6. After a domU bootup it took some random > >time (up to 2 hours) to start the configured addresses to work. > > > >If I configured the ips after bootup by hand (ifconfig) they worked > >fine. > > > >After some tcpdumping I noticed that the incoming packets went to a > >different MAC address than the outgoing came from. > > > >I then gave the virtual machine a static MAC address, and from then on > >it started working without any manual configuration. > Would you mind pasting the networking part of your domU''s config file? > I''d like to see exactly how you have it setup.Sure: vif= [ ''mac=aa:00:00:00:00:12, bridge=xen-br17''] In the domU i disabled autoconfig however it does work using autoconfig, I just don''t like the random addresses it gets: curti@egli:~$ cat /etc/sysctl.conf net.ipv6.conf.default.autoconf = 0 (you have to make sure the ipv6 module is loaded when the sysctls get set) the network config is then made the debian way using /etc/network/interfaces: auto eth0 iface eth0 inet6 static address 4567:123:22::d netmask 64 gateway 4567:123:22::1 Kind regards and hth Flavio Curti -- http://no-way.org/~fcu/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hello Andrew On Tue, Aug 01, 2006 at 12:43:55AM -0400, Andrew Yates wrote:> >I also had problems using IPv6. After a domU bootup it took some random > >time (up to 2 hours) to start the configured addresses to work. > > > >If I configured the ips after bootup by hand (ifconfig) they worked > >fine. > > > >After some tcpdumping I noticed that the incoming packets went to a > >different MAC address than the outgoing came from. > > > >I then gave the virtual machine a static MAC address, and from then on > >it started working without any manual configuration. > Would you mind pasting the networking part of your domU''s config file? > I''d like to see exactly how you have it setup.Sure: vif= [ ''mac=aa:00:00:00:00:12, bridge=xen-br17''] In the domU i disabled autoconfig however it does work using autoconfig, I just don''t like the random addresses it gets: curti@egli:~$ cat /etc/sysctl.conf net.ipv6.conf.default.autoconf = 0 (you have to make sure the ipv6 module is loaded when the sysctls get set) the network config is then made the debian way using /etc/network/interfaces: auto eth0 iface eth0 inet6 static address 4567:123:22::d netmask 64 gateway 4567:123:22::1 Kind regards and hth Flavio Curti -- http://no-way.org/~fcu/ _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Sure: > > vif= [ ''mac=aa:00:00:00:00:12, bridge=xen-br17''] > > In the domU i disabled autoconfig however it does work using autoconfig, > I just don''t like the random addresses it gets: > > curti@egli:~$ cat /etc/sysctl.conf > net.ipv6.conf.default.autoconf = 0 > > (you have to make sure the ipv6 module is loaded when the sysctls get > set) > > the network config is then made the debian way using > /etc/network/interfaces: > > auto eth0 > iface eth0 inet6 static > address 4567:123:22::d > netmask 64 > gateway 4567:123:22::1 > > Kind regards and hth > > Flavio CurtiExcellent. I was specifying the IPs in the network config, but I''ll try this instead. Thanks! _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users