Hello List, I have a problem/question for understanding. I have on my server (debian wheezy) 3 virtual systems running on xen with own IPv4 addresses. Form my hoster I got an IPv6 subnet, but I don''t really know how to add it. Is it enought to add an address of it in the /etc/network/interfaces of the virtual systems? Or must I set up routing for Xen and how does it works together with bridging? Which settings I had to change? And am I able to set up an system only with Ipv6? (I have IPv6) Hopefully that you can help me. Regards Thore
Thore wrote:>I have a problem/question for understanding. >I have on my server (debian wheezy) 3 virtual systems running on xen >with own IPv4 addresses. >Form my hoster I got an IPv6 subnet, but I don''t really know how to add it. >Is it enought to add an address of it in the /etc/network/interfaces of >the virtual systems? >Or must I set up routing for Xen and how does it works together with >bridging? >Which settings I had to change? >And am I able to set up an system only with Ipv6? >(I have IPv6)These are mostly not really Xen questions, more a general networking issue. The first question is, how does the hoster present your networking ? And how is your Xen networking set up ? If (for example) your hoster presents you an ethernet cable, with your own IP range and a gateway address for their router; and you are using bridging on Xen; then it will simply be a case of configuring an IPv6 address on each box. Configuring IPv6 can be done several ways, and that depends on how the routers are configured. At it''s simplest, the router(s) will advertise themselves and your devices can self-assign an address - auto configuration which should "just work". For hosting, you probably want to manually configure IPv6 addresses so they are fixed.
Am 06.02.2013 13:00, schrieb Simon Hobson:> Thore wrote: >> I have a problem/question for understanding. >> I have on my server (debian wheezy) 3 virtual systems running on xen >> with own IPv4 addresses. >> Form my hoster I got an IPv6 subnet, but I don''t really know how to add it. >> Is it enought to add an address of it in the /etc/network/interfaces of >> the virtual systems? >> Or must I set up routing for Xen and how does it works together with >> bridging? >> Which settings I had to change? >> And am I able to set up an system only with Ipv6? >> (I have IPv6) > > > These are mostly not really Xen questions, more a general networking issue. > > The first question is, how does the hoster present your networking ? And how is your Xen networking set up ? > > If (for example) your hoster presents you an ethernet cable, with your own IP range and a gateway address for their router; and you are using bridging on Xen; then it will simply be a case of configuring an IPv6 address on each box. > Configuring IPv6 can be done several ways, and that depends on how the routers are configured. At it''s simplest, the router(s) will advertise themselves and your devices can self-assign an address - auto configuration which should "just work". For hosting, you probably want to manually configure IPv6 addresses so they are fixed.I have a xenbr0 auto xenbr0 iface xenbr0 inet static address 1.2.3.4 netmask 255.255.255.255 gateway 2.3.4.5 bridge_ports eth0 Like this is my bridge configuration. Some time before I set this in my /etc/network/interfaces #iface eth0 inet6 static # address 2a01:4f8:140:1:2 # netmask 64 # gateway fe80::1 At the moment it is inaktive. I have 3 IPv4 Adresses, no Subnet. The server has only an eth0. And if it helps it is hosted by hetzner regards Thore
Thore wrote:>I have a xenbr0Then there is nothing Xen-specific to set up>Some time before I set this in my /etc/network/interfaces >#iface eth0 inet6 static ># address 2a01:4f8:140:1:2 ># netmask 64 ># gateway fe80::1fe80 addresses are self-assigned link-local, and you probably don''t have an fe80::1 on the network. You need to set both a valid address and gateway. 2a01:4f8:140:1:2 is not a valid IPv6 address - is there a typo there (too few groups, is there a :: missing) ? The gateway might be configured by Route Advertisement broadcasts, or it might be configured manually - what does your hoster tell you to use ?>At the moment it is inaktive. >I have 3 IPv4 Adresses, no Subnet.Actually, you will have a subnet, but most likely you have 3 IPs from a larger subnet shared with other hosting clients.
Am 06.02.2013 17:42, schrieb Simon Hobson:> Thore wrote: >> I have a xenbr0 > Then there is nothing Xen-specific to set up > >> Some time before I set this in my /etc/network/interfaces >> #iface eth0 inet6 static >> # address 2a01:4f8:140:1:2 >> # netmask 64 >> # gateway fe80::1 > fe80 addresses are self-assigned link-local, and you probably don''t have an fe80::1 on the network. You need to set both a valid address and gateway. 2a01:4f8:140:1:2 is not a valid IPv6 address - is there a typo there (too few groups, is there a :: missing) ? > The gateway might be configured by Route Advertisement broadcasts, or it might be configured manually - what does your hoster tell you to use ? > >> At the moment it is inaktive. >> I have 3 IPv4 Adresses, no Subnet. > Actually, you will have a subnet, but most likely you have 3 IPs from a larger subnet shared with other hosting clients. > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-usersHetzner says: ## /etc/network/interfaces example Hetzner root server # Loopback-Adapter auto lo iface lo inet loopback # LAN interface auto eth0 iface eth0 inet static # Main IP address of the server address 192.168.0.250 # Netmask 255.255.255.255 (/32) independent from the # real subnet size (e.g. /27) netmask 255.255.255.255 # explicit host route to the gateway gateway 192.168.0.1 pointopoint 192.168.0.1 iface eth0 inet6 static # Main IPv6 Address of the server address 2a01:4f8:61:20e1::2 netmask 64 gateway fe80::1 when I change it to my adresses, it would work, but how can I set it up for the domU''s? I think I had to enable the script in the xend config. but what else I had to change? Add the address in the .cfg file? I read that xen is able to use both. But can I only use the xenbr0 or need I another bridge and another interface for the domU? regards Thore
Hello, On Wednesday 06 February 2013 23:31:14 Thore wrote:> when I change it to my adresses, it would work, but how can I set it up > for the domU''s?Think one moment what you would do with a real physical network: You have the cable from Hetzner, plug it into a switch, to which you would now connect all your hosts. As all hosts are part of the same broadcast domain, you would configure all hosts with the same gateway, netmask, but different host addresses. No back to virtualization: The cabel is eth0: is has no address on it''s own. Your physical switch is now virtual and done by the Linux kernel on dom0 as br0. As the bridge and the dom0 are the same, this is the only difference: you configure the dom0 address on the bridge (and not on some bridge-to-dom0 dummy interface as it was done in one of the first releases of Xen) dom0:> # LAN interface > auto eth0Change eth0 -> br0> iface eth0 inet staticChange eth0 -> br0> # Main IP address of the server > address 192.168.0.250 > # Netmask 255.255.255.255 (/32) independent from the > # real subnet size (e.g. /27) > netmask 255.255.255.255 > # explicit host route to the gateway > gateway 192.168.0.1 > pointopoint 192.168.0.1Add " bridge_ports eth0" Add " bridge_fd 0" is you know the consequences> iface eth0 inet6 staticChange eth0 -> br0> # Main IPv6 Address of the server > address 2a01:4f8:61:20e1::2 > netmask 64 > gateway fe80::1For the domUs you use the original configuration without the br0->eth0 rename: There you get a virtual cable, where one end is already plugged in the virtual switch (vif${dom}.${iface}) by Xend and the other end is now your domUs interface eth0.> I think I had to enable the script in the xend config.Disable them: The current way is to use the mechanism provided by your Distribution, which for Debian is to edit /etc/network/interfaces. /etc/xen/xend-config.sxp: #(network-script network-bridge) This disabled xend from creating the bridge itself (vif-script vif-bridge) This tells Xend to plugin your domUs into the bridge.> Add the address in the .cfg file?That''s more confusing than anything else: the IP address there is only used to setup anti-spoofing rules, the real IP configuration happens inside your domUs, since they receive all broadcast traffic. There you only specify the bridge vif = [ ''..., bridge=br0, ...'' ]> But can I only use the xenbr0 or need I another bridge and another > interface for the domU?In the past Xen did the xenbridge-dance itself to create one default bridge xenbr0 (later eth0), into which the interface eth0 (later peth0) was plugged in. Sincerely Philipp -- Philipp Hahn Open Source Software Engineer hahn@univention.de Univention GmbH be open. fon: +49 421 22 232- 0 Mary-Somerville-Str.1 D-28359 Bremen fax: +49 421 22 232-99 http://www.univention.de/