WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] Constructor code in MAC address does matter ?

To: Jean-Christophe Guillain <jcg@xxxxxxxxxx>
Subject: Re: [Xen-users] Constructor code in MAC address does matter ?
From: Derrik Pates <demon@xxxxxxxxxxxxx>
Date: Mon, 15 Aug 2005 14:36:19 -0400
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 15 Aug 2005 18:34:44 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20050815110915.5E9F826D31@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <20050815110915.5E9F826D31@xxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
On Mon, Aug 15, 2005 at 01:09:15PM +0200, Jean-Christophe Guillain wrote:
> 
> I observed a strange networking behaviour of my Debian virtual host in 
> function of the MAC address I use. It seems that when I use an existing 
> constructor code, networking works without any problem, but is impossible 
> in the other case...
> Ex. :
> - vif = [ 'mac=aa:00:00:00:00:55, bridge=xen-br0' ] -> no problem
> - vif = [ 'mac=df:00:00:00:00:55, bridge=xen-br0' ] -> the bridge does not 
> transmit my packets apparently. No DHCP possible, and when I used a static 
> address I can't ping the bridge from the guest... 

Yes, this actually makes sense. Bit 0 of the first hex byte of the MAC
address indicates the packet is going to a broadcast address, but in a
source MAC address, it's nonsensical. I'm not surprised other TCP stacks
would squash it. Provide a MAC address that doesn't have that bit set.
(I.e., de:00:00:00:00:55 should work; df:00:00:00:00:55 won't.)

Note that this has nothing to do with the domain builder, and everything
to do with the behavior of Ethernet networking.

-- 
Derrik Pates
demon@xxxxxxxxxxxxx

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

<Prev in Thread] Current Thread [Next in Thread>