Your message dated Sun, 02 Mar 2014 18:42:06 +0000 with message-id <[email protected]> and subject line Bug#740517: Removed package(s) from unstable has caused the Debian Bug report #682216, regarding document about VLAN configuration on dom0 to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 682216: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682216 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: src:xen-api Severity: wishlist I've tried to configure VLAN using XCP + openvswitch using Wheezy, though it's still not fully working, I think VLAN configuration on dom0 can be better documented. It's fair easy to configure VLAN in Debian. First you need to ensure that your physical switch is in trunk mode, which means it will pass all kinds of VLAN tagged network flow, and add corresponding VLAN tag to the ports that connect to your server. This is the basic of a working VLAN. Next you need to install vconfig package to the system, either by using apt-get if the host machine is able to access network, or by transferring the files in other means if your VLAN enabled link makes it unable to download a file. Then make changes to /etc/network/interface as following: # The loopback network interface auto lo iface lo inet loopback auto eth0.100 iface eth0.100 inet manual vlan_raw_device eth0 # The primary network interface auto xenbr0 iface xenbr0 inet static bridge_ports eth0.100 bridge_stp on address 192.168.1.120 netmask 255.255.255.128 gateway 192.168.1.1 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 8.8.8.8 dns-search example.com This will make xenbr0 bridged to eth0.100, which means VLAN tag 100 on eth0. There is no need to write about iface eth0, neither bring those devices up explicitly, as the network will be brought up in a dependency based manner. In this very example, VLAN 100 was configured as the default tag on the physical switch, which means everything no tagged will be tagged as 100. But you are free to use other VLAN for the device as long as you have added the VLANs to corresponding ports on your physical switch. Finally you can continue with what we already have in README.Debian, to configure the PIFs using `xe pif-reconfigure-ip` of your physical devices, namely eth0. I have tested with two physical NICs in this manner and it works fine for dom0. But I still cannot make network available because of another problem (very likely to be a bug, but I still need some debugging to confirm). If you are using openvswitch, you can start a VM when created from a template, and boot the installer from a network URL with no problem, just like you don't have VLAN when using openvswitch. -- Regards, Aron Xu
--- End Message ---
--- Begin Message ---Version: 1.3.2-15+rm Dear submitter, as the package xen-api has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/740517 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Luca Falavigna (the ftpmaster behind the curtain)
--- End Message ---
