On 19.01.2014 14:37, Marcus Sorensen wrote:
You probably need an IP address on the physical network that you're
running vxlan on, since this host needs to communicate with other
hosts to send vxlan packets. Where prevously you could just bring up a
bridge on an ethernet interface with no config, you can put all of
your hosts on one untagged vlan, give them all ip addresses, and then
the vxlan networks will flow over that. You can also use your
physical interface name for the traffic label, if you have no other
need for that bridge.
It looks like there's been a bit of documentation checked in for 4.3,
so there should be at least some published along with the release of
the feature, and here are some links to the design docs and such. I
haven't reviewed the docs in detail.
http://www.slideshare.net/haeenajp/asfccc2013-toshiaki-release
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Linux+native+VXLAN+support+on+KVM+hypervisor
Thanks a lot, Marcus. I did not expect I needed an IP on that
interface, too used with the old vlans.
I'll try to fix my setup.
Lucian
--
Sent from the Delta quadrant using Borg technology!
Nux!
www.nux.ro
