233
edits
Changes
Jump to navigation
Jump to search
Line 30:
Line 30: − + − 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. Line 43:
Line 37: − + Line 64:
Line 58: −
→Network configuration
There is a traffic shaper, but it may have trouble shaping 6to4 traffic.
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
Bender is globally accessible through public, static IPv4 address.
The virbr0 bridge is created by libvirt on startup with <code>/etc/libvirt/qemu/networks/default.xml</code>.
The virbr0 bridge is created by libvirt on startup with <code>/etc/libvirt/qemu/networks/default.xml</code>.
ip addr add 2002:5395:9edc:1::1/64 dev virbr0
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
To automatically configure network and on the guests, Bender also runs radvd, the IPv6 Routing Advertisement
daemon. The contents of <code>/etc/radvd.conf</code> are:
daemon. The contents of <code>/etc/radvd.conf</code> are:
Guests simply need to be configured to accept IPv6 routing advertisements. The DNS must be assigned manually.
Guests simply need to be configured to accept IPv6 routing advertisements. The DNS must be assigned manually.
== Hosted VMs ==
== Hosted VMs ==