marionnet-dev team mailing list archive

[Franck Butelle <723439@xxxxxxxxxxxxxxxxxx>]

May be the first question is: do we need to be able to run multiple instances of marionnet 
on the same machine? If the answer is no, the daemon (anyway unique) must block in some way creation of new 
instances. If the answer is yes, the above requirement is mandatory.
Actually, addresses used are 172.23.x.y for the virtual machines
and 172.23.0.254 for the host. We can use other class B private addresses from 172.16 to 172.31.
Of course it may be a problem if the user choose the same kind of address for one of its network,
since it must be fixed before user's choice -- this is the price of the magic !
Ghostifiy interface for marionnet management/display is a nice idea to help beginners to start using marionnet,
but I think there is at least a need of an explicit warning at the virtual machine level (may be in /etc/motd).

-- 
You received this bug notification because you are a member of
marionnet-dev, which is subscribed to marionnet.
https://bugs.launchpad.net/bugs/723439

Title:
  Same ip addresses for several virtual hosts when two marionnet are
  running

Status in Marionnet - A virtual network laboratory:
  New

Bug description:
  When several marionnet are running on the same machine, the same ip
  address on interface eth42 may be given to differents virtual machines
  (for example if you save a marionnet project, make a copy and open
  this copy with another marionnet).

  It would be great if for example marionnet-daemon had a list of all
  the ip address already used and when marionnet opens a project, it
  check this list and possibly change the ips addresses of the new
  virtual machines.