1,764
edits
Changes
Jump to navigation
Jump to search
Line 23:
Line 23: − + − an IPv6 /64 subnet (6to4).+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + − Develer has a 10mbit up/downlink and asks to limit bandwidth usage from hosted services. − There is a traffic shaper, but it may have trouble shaping IPv6 connections.
no edit summary
== Network configuration ==
== Network configuration ==
Bender is globally accessible through public, static IPv4 as well as
Develer has a 10mbit up/downlink and asks to limit bandwidth usage from hosted services.
There is a traffic shaper, but it may have trouble shaping 6to4 traffic.
Bender is globally accessible through public, static IPv4 as well as the 6to4 subnet associated
to it: 2002:5395:9edc::/48.
The tun6to4 interface on bender is assigned the globally visible address 2002:5395:9edc::1.
The subnet 2002:5395:9edc:1::/64 of our 6to4 net is assigned to the bridge virbr0, which binds together
several virtual interfaces connected to the libvirt guests. With this network setup, IPv6 routing works
naturally, without the need to add any special routing rules on bender.
The virbr0 bridge is created by libvirt on startup with <code>/etc/libvirt/qemu/networks/default.xml</code>.
Libvirt does not yet support assigning IPv6 addresses to bridges, therefore we do this in <code>/etc/rc.local</code>:
ip addr add 2002:5395:9edc:1::1/64 dev virbr0
To automatically configure network and on the gursts, Bender also runs radvd, the IPv6 Routing Advertisement
daemon. The contents of <code>/etc/radvd.conf</code> are:
interface virbr0
{
IgnoreIfMissing on;
AdvSendAdvert on;
MinRtrAdvInterval 30;
MaxRtrAdvInterval 100;
AdvDefaultPreference low;
AdvHomeAgentFlag off;
#bernie: subnet 1 of our /48 6to4 on Develer Consiagnet
prefix 2002:5395:9edc:1::1/64
{
AdvOnLink on;
AdvAutonomous on;
};
};
Guests simply need to be configured to accept IPv6 routing advertisements. The DNS must be assigned manually.
== Hosted VMs ==
== Hosted VMs ==