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

[Xen-users] Extrange behaviour in arp with xen 3.0.3 from etch


  • To: debian-user <debian-user@xxxxxxxxxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Javier Barroso <javibarroso@xxxxxxxxx>
  • Date: Fri, 8 May 2009 10:14:08 +0200
  • Cc:
  • Delivery-date: Mon, 11 May 2009 06:59:42 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=P7Iv8FGo4V4UuDx7+5g+qT4j4eh5J2FLl2k1ggi2eJ175E7XgbOhn6NovQ0b6EB6LH q4I6zJUT/RJLst6OEnNWDPUj634PFdyttgOsB/Cd9rAq50WsWihUL4DDkoi7HebZTOnZ FOAN87V8HdfA+skVJdwThNVYbSJshBFHTxXPc=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello,

I have a etch xen server with a virtual machine with 2 network
interfaces configured. Every interface has a different mac, and inside
the host has a different ip.

However I can see with tcpdump and arpwatch (I discover this because
arpwatch told me), about the two ips has the two macs.

I asked it in xen chat channel, but I hadn't got response.

itsm:~# ip add
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP qlen 1000
    link/ether 00:16:3e:7c:64:e0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.110.54/16 brd 192.168.255.255 scope global eth0
    inet6 fe80::216:3eff:fe7c:64e0/64 scope link
       valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP qlen 1000
    link/ether 00:16:3e:7c:64:e1 brd ff:ff:ff:ff:ff:ff
    inet 192.168.100.4/16 brd 192.168.255.255 scope global eth1
    inet6 fe80::216:3eff:fe7c:64e1/64 scope link
       valid_lft forever preferred_lft forever



# grep vif /mnt/xen-itsm/itsm.cfg
vif         = [
'mac=00:16:3E:7C:64:E0,bridge=br-lan','mac=00:16:3E:7C:64:E1,bridge=br-lan']

# tcpdump
08:42:47.760980 arp reply 192.168.110.54 is-at 00:16:3e:7c:64:e0 (oui Unknown)
08:42:47.760993 arp reply 192.168.110.54 is-at 00:16:3e:7c:64:e1 (oui Unknown)

myotherhostwhereihaveinstalledarpwatch # tcpdump
09:40:48.679264 ARP, Reply 192.168.100.4 is-at 00:16:3e:7c:64:e0 (oui
Unknown), length 42
09:40:48.679275 ARP, Reply 192.168.100.4 is-at 00:16:3e:7c:64:e1 (oui
Unknown), length 42


# xm list | grep itsm
itsm                                      30      512     1 -b----   5933.0

# brctl show
bridge name     bridge id               STP enabled     interfaces
...
br-lan          8000.001b244d6b2f       no              vlan192
                                                        vif30.0
                                                        vif30.1
...

Do you have any clue about this issue ?

Thank you

_______________________________________________
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®.