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

Re: [Xen-users] IPs jumping around on domU?


  • To: p <p@xxxxxxxx>
  • From: "SLB Xen Dev" <xendev@xxxxxxxxxxxxxxxx>
  • Date: Fri, 23 Mar 2007 12:59:50 -0400
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Fri, 23 Mar 2007 09:58:55 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:references:x-google-sender-auth; b=Ct8qbSmo+zsZ0Jb1b71gnfFZsjmKD3OwJYlzLs78sD3mNl3ETtIWd2VU95kWDfhI8Q+lJYZM9TU3WJb+E8pM9Car8ndbWMO+pD4DRlm/hIKiKWSvON7WtFzE4zqCWLQb2+QKDuCbeS0H4mTZB2cofJiJ4ftC9AWYTJZIJD37LyU=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I had the same problem.  I don't know how debian/ubuntu handles it, but my solution under CentOS involved setting the mac addresses in the domU.cfg, and then matching those mac addresses in the interface config files.  That way even if the interfaces are initialized in a different order, they still end up going to the right bridges.

Also, does debian really allow multiple gateways?  RHEL doesn't, but it didn't matter to me since the other bridges were private networks.

On 3/23/07, p <p@xxxxxxxx> wrote:
Hi all,

I have a domU with three interfaces using a bridged setup, but the
packages seem to arrice randomly on the interfaces in domU.
dom0 and domU are Ubuntu 6.10.

domU.cfg:
...
vif = [
'ip=88.198.X.A,bridge=xenbr0','ip=88.198.X.B,bridge=xenbr0','ip=88.198.X.C ,bridge=xenbr0'
]
...

domU log generated by iptables:

Mar 23 14:55:45 machine kernel: IN=eth2 OUT= MAC=... SRC="">DST=88.198.X.A LEN=48 TOS=0x00 PREC=0x00 TTL=115 ID=5282 DF PROTO=TCP
SPT=10777 DPT=80 WINDOW=16384 RES=0x00 SYN URGP=0
Mar 23 14:55:19 machine kernel: IN=eth1 OUT= MAC=... SRC="">DST=88.198.X.B LEN=60 TOS=0x00 PREC=0x00 TTL=48 ID=8818 PROTO=TCP
SPT=28026 DPT=80 WINDOW=65535 RES=0x00 SYN URGP=0
Mar 23 14:55:22 machine kernel: IN=eth2 OUT= MAC=... SRC=""
DST=88.198.X.C LEN=52 TOS=0x00 PREC=0x00 TTL=48 ID=9268 PROTO=TCP
SPT=27828 DPT=80 WINDOW=65535 RES=0x00 ACK FIN URGP=0

domU /etc/network/interfaces:

auto lo
iface lo inet loopback

# device: eth0
auto eth0
iface eth0 inet static
address 88.198.X.A
        broadcast 88.198.Y.Y
        netmask 255.255.255.248
        gateway 88.198.Y.Y
# device: eth1
auto eth1
iface eth1 inet static
address 88.198.X.B
        broadcast 88.198.Y.Y
        netmask 255.255.255.248
        gateway 88.198.Y.Y
# device: eth2
auto eth2
iface eth2 inet static
address 88.198.X.C
        broadcast 88.198.Y.Y
        netmask 255.255.255.248
        gateway 88.198.Y.Y
---

Why isn't eth0  used at all in domU?


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users



--
Puer Misellus Triste
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

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