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

[Xen-bugs] [Bug 722] changing MAC address makes VM unreachable



http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=722


tfreeman@xxxxxxxxxxx changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




------- Comment #1 from tfreeman@xxxxxxxxxxx  2006-08-07 10:51 -------
Solved this, the random MACs being generated (by non-Xen software) in the
non-working case were not unicast.

As outlined here: 

http://wiki.xensource.com/xenwiki/XenNetworking

"Ensure you choose a unicast address.  That is, one with the low bit of the
first octet set to zero. For example, an address starting aa: is OK but ab: is
not. It is best to keep to the range of addresses declared to be "locally
assigned" (rather than allocated globally to hardware vendors). These have the
second lowest bit set to one in the first octet. For example, aa: is OK, a8:
isn't.

In summary, an address of the following form should be OK:
XY:XX:XX:XX:XX:XX

where X is any hexadecimal digit, and Y is one of 2, 6, A or E"


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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


 


Rackspace

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