Bug #287

Network leases over 128.0.0.0 get wrong MAC address

Added by Ariel Garcia over 10 years ago. Updated over 10 years ago.

Status:ClosedStart date:07/20/2010
Priority:HighDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Resolution:fixed Pull request:
Affected Versions:

Description

Creating a new network with the template

===================================
NAME = "PUBLIC"
TYPE = FIXED
BRIDGE = br0

LEASES = [ IP="141.52.208.195"]
LEASES = [ IP="141.52.208.194"]
LEASES = [ IP="141.52.208.193"]
LEASES = [ IP="141.52.208.192"]
LEASES = [ IP="141.52.208.191"]
LEASES = [ IP="141.52.208.190"] ===================================

results in the following leases information with IDENTICAL MAC addresses!

========================================
VIRTUAL NETWORK TEMPLATE
BRIDGE=br0
LEASES=[ IP=141.52.208.195 ]
LEASES=[ IP=141.52.208.194 ]
LEASES=[ IP=141.52.208.193 ]
LEASES=[ IP=141.52.208.192 ]
LEASES=[ IP=141.52.208.191 ]
LEASES=[ IP=141.52.208.190 ]
NAME=PUBLIC
TYPE=FIXED

LEASES INFORMATION
LEASE=[ IP=141.52.208.190, MAC=02:00:7f:ff:ff:ff, USED=1, VID=0 ]
LEASE=[ IP=141.52.208.191, MAC=02:00:7f:ff:ff:ff, USED=1, VID=5 ]
LEASE=[ IP=141.52.208.192, MAC=02:00:7f:ff:ff:ff, USED=1, VID=6 ]
LEASE=[ IP=141.52.208.193, MAC=02:00:7f:ff:ff:ff, USED=1, VID=7 ]
LEASE=[ IP=141.52.208.194, MAC=02:00:7f:ff:ff:ff, USED=1, VID=8 ]
LEASE=[ IP=141.52.208.195, MAC=02:00:7f:ff:ff:ff, USED=0, VID=-1 ] ==========================

This doesn´t happen if the assigned IP addresses lie below 128.0.0.0!!

Also trying to assign MAC fixed addresses in the network template shows the same problem when the THIRD octet (CC in AA:BB:CC:DD:EE:FF) exceeds 127=0x7F.

Associated revisions

Revision 7e92b75b
Added by Ruben S. Montero over 10 years ago

bug #287: Fixed wrong size for leases in mysql

Revision 9cc4c3de
Added by Abel Coronado over 3 years ago

B #5133 Solved bug in storage size when update vm template (#287)

History

#1 Updated by Ariel Garcia over 10 years ago

This refers to OpenNebula 1.6, as checked out from the GIT repo on 19/7/2010.

#2 Updated by Ruben S. Montero over 10 years ago

  • Status changed from New to Closed
  • Resolution set to fixed

Thanks!!!

This was because a wrong size in the network leases when using MySQL. Fix has been applied to master. THANK YOU FOR THE TESTING!

#3 Updated by Ariel Garcia over 10 years ago

Hola Ruben, that was fast, thanks a lot!! Updated the mysql table field by hand, it worked :-)

Also available in: Atom PDF