Arch linux post-installation and ovs

[francozappa]

Hi all,

I've installed from AUR mininet 2.2.1-4 and the required dependencies.
Then I've found these set of commands from the post-install script

  # systemctl enable ovsdb-server.service
  # systemctl start ovs-vswitchd.service
  # systemctl enable ovsdb-server.service
  # systemctl start ovs-vswitchd.service

I think that they are wrong and should be substituted with:

  # systemctl enable ovs-vswitchd.service
  # systemctl start ovs-vswitchd.service

Because once I start and enable ovs-vswitchd I can see both services that are running typing
a command like systemctl |grep ovs.

Even if I executed, what I think, are the correct commands when I type sudo mn the program
is struck at:

*** Creating network
*** Adding controller
*** Adding hosts:
h1 h2 
*** Adding switches:
s1 
*** Adding links:
(h1, s1) (h2, s1) 
*** Configuring hosts
h1 h2 
*** Starting controller
c0 
*** Starting 1 switches
s1 ...

Can you help me with that ? I think that the problem is related with the database.

I'd really like to develop using my host OS (manjaro-linux)
rather than a VM.

Thanks !

[martinjlowm]

Hi,

Yes, that is obviously a mistake in the post install script. I have notified the mininet AUR package maintainer.

About your startup script getting stuck. What is the systemctl status output from ovsdb-server and ovs-vswitchd?

[francozappa]

Hi @martinjlowm

here is the output of systemctl (I've removed some whitespaces):

ovs-vswitchd.service    loaded active running   Open vSwitch Daemon
ovsdb-server.service    loaded active running   Open vSwitch Database Server

here is the output of systemctl status:

ovs-vswitchd.service
       │ │ └─1991 /usr/sbin/ovs-vswitchd --pidfile=/run/openvswitch/ovs-vswitchd.pid
ovsdb-server.service
       │ │ └─1979 /usr/sbin/ovsdb-server --remote=punix:/var/run/openvswitch/db.sock --pidfile=/run/openvswitch/ovsdb-server.pid

[francozappa]

Hi @martinjlowm

Are there any updates regarding Arch linux mininet pkg?

Cheers

[jcmartins]

nope :(

[martinjlowm]

@francozappa: No, there's nothing new :(

I apologise for not answering back in June.

Your status output looks fine.

Do you have the courage to debug Mininet's start up process? You can either use pdb or look for "Starting switches" in the Python library files and step-wise print to see exactly where it gets stuck.

[matclab]

I manages to have mininet working on arch linux by:

• loading openvswitch module: sudo modprobe openvswitch
• providing the missing controller executable: sudo ln -s /usr/bin/ovs-testcontroller /usr/bin/controller

Hope this helps