Re: bridging to multiple ip addresses.

--===============1789586268==
Content-Type: multipart/signed; micalg="pgp-sha1";
	protocol="application/pgp-signature";
	boundary="=-Qa18qx+h1DqipanX9xhq"


--=-Qa18qx+h1DqipanX9xhq
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, 2011-12-06 at 17:42 +1300, Steve Holdoway wrote:
> Hi folks,
>=20
> I'm working on making more than one of my KVM virtual machines visible
> on separate IP addresses.
>=20
> I'm happy with an ethernet interface having multiple IP adresses, but am
> looking for decent documentation on how to do this for br0 instead, so
> that traffic over the bridge can be routed to different vms according to
> IP address.
>=20
> I try googling, but am instantly deluged with dire warnings about level
> 2 loops and other similar instances of certain fatality.
>=20
> Is it just as simple as setting up network definitions for br0, br1, br2
> with the specific IP addresses, all bridging to eth0?


Essentially, create a bridge and add the ethernet interface of the host
to it using the regular distribution methods.

Then when you configure the KVM VMs, set them to use the bridge as their
source.

(Unless I've miss-understood the question and you're trying to do some
fancy stuff with address translation or something?)


> Any decent documentation on how to do this would be gratefully received.

Assuming you're doing it via libvirt, the documentation online is pretty
good:

Documentation on the KVM configuration:
http://libvirt.org/formatdomain.html#elementsNICS

Documentation on virtual networks:
http://libvirt.org/formatnetwork.html

(if you're just adding the VMs to a bridge, you won't need to do any of
the virtual network stuff, but there will always be a default virbr0
virtual network with libvirt, even if it's unused).

regards,
jethro


--=20
Jethro Carr
www.jethrocarr.com
www.amberdms.com

--=-Qa18qx+h1DqipanX9xhq
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEABECAAYFAk7d5GwACgkQDpNWragKym8s2QCfSq49HpfCbvQBObaiX3p+PZ0U
fAkAoIA8CYiT4NPZTSYEpKrQpQrLWqB1
=I2AH
-----END PGP SIGNATURE-----

--=-Qa18qx+h1DqipanX9xhq--



--===============1789586268==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
NZLUG mailing list [email protected]
http://www.linux.net.nz/cgi-bin/mailman/listinfo/nzlug

--===============1789586268==--