[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] RESOLVED: Broadcom NetXtreme II (DELL 1950)

  • To: Xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Fajar A. Nugraha" <fajar@xxxxxxxxxxxx>
  • Date: Wed, 10 Oct 2007 09:25:59 +0700
  • Delivery-date: Mon, 15 Oct 2007 03:37:01 -0700
  • List-id: Xen user discussion <xen-users.lists.xensource.com>
  • Openpgp: url=http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x418D88CB

Stefan de Konink wrote:
> Ok there are several issues with bridging:
> *STUPIDNESS* You cannot set an IP address on the endpoint of a NIC. If
> you want to manipulate a random subnet trough the bridge you should set
> the bridge with an IP address in this subnet and not one of the 'to be
> bridged' IP addresses.

> So
> eth1:  ----  bridge  ---- tap0:
> and NOT:
> eth1: ---- bridge ---- tap0:
This is how linux bridge works.
Solaris bridge uses a different bridging configration, in which you put
IP address on the NIC.

What I like to do is this :
eth1 --- bridge --- tap0,vif0.1


That is :
- disabled Xen's network-bridge script
- put vif0.1 on the bridge
- setup ip address on veth1

vif0.1 and veth1 is created by xen's netloop driver (loaded by xend. I
also added it to /etc/modprobe.conf). I prefer this setup because :
- there's no IP address on the bridge
- All networking setup is done by redhat's standard config files.



Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.