Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - mininet

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: mininet 2.2.1-4

Git Clone URL: https://aur-dev.archlinux.org/mininet.git (read-only)
Package Base: mininet
Description: Process-based network emulator (stable branch)
Upstream URL: https://github.com/mininet/mininet/
Licenses: custom
Submitter: pedromj
Maintainer: pedromj
Last Packager: pedromj
Votes: 8
Popularity: 0.187487
First Submitted: 2014-11-07 17:38
Last Updated: 2015-10-01 10:01

Latest Comments

1 2 Next › Last »

cemsbr commented on 2016-08-10 17:11

# systemctl enable ovsdb-server.service
The unit files have no installation config (WantedBy, RequiredBy, Also, Alias
settings in the [Install] section, and DefaultInstance for template units).
This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
1) A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
2) A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
3) A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
4) In case of template units, the unit is meant to be enabled with some
instance name specified.

SAL9000 commented on 2016-06-28 07:22

Please backport mininet commit 96ea536 [1] into this package, in order to fix an issue caused by mininet's interaction with systemd (see mininet issue #565 [2]).

[1] https://github.com/mininet/mininet/commit/96ea5367dbea7b77e6b7454c1de85b30b7ba7035

[2] https://github.com/mininet/mininet/issues/565

martinjlowm commented on 2016-05-07 10:17

It should be noted by @jetm's contribution that the post install message seems to include a mistake. ovsdb-server is enabled twice and ovs-vswitchd is started twice.

Both ovsdb-server and ovs-vswitchd should be enabled and started afterwards.

This mistake got my attention after @francozappa's issue Mininet/626 on GitHub (https://github.com/mininet/mininet/issues/626)

To sum it up, the correct sequence is:

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

pedromj commented on 2015-10-01 10:01

I've updated the package. Please test it.

jetm commented on 2015-09-30 17:54

@glindste: Thanks! With your suggestions mininet runs as it's expected.


To avoid these errors, I would put openvswitch as a required dependency (non optional). Also, I would show a message after installation saying ovsdb-server.service and ovs-vswitchd.service are needed to be executed before call 'sudo mn' or I would enable them.

For a post installation message you can take an example on virtio-win AUR package. Look in virtio-win.install file.

For start the required services, I think with just execute these will be OK:

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

If you need help with AUR package, let me know. I can send you a Git patch.


glindste commented on 2015-09-30 17:06

Ok, solved it now. After installing openvswitch, start BOTH ovsdb-server.service and ovs-vswitchd.service. Then 'sudo mn' should run fine.

glindste commented on 2015-09-30 17:02

@jetm: I had the same problem, but if I install openvswitch (optional dependency) it doesn't crash. However if I run 'sudo mn' it gets stuck at starting the switch, don't know why.

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

jetm commented on 2015-09-18 16:35

@pedromj: Installation was good, but calling nm fails with this message:
$ sudo nm
*** Creating network
*** Adding controller
*** Adding hosts:
h1 h2
*** Adding switches:
Caught exception. Cleaning up...

OSError: [Errno 2] No such file or directory
*** Removing excess controllers/ofprotocols/ofdatapaths/pings/noxes
killall controller ofprotocol ofdatapath ping nox_core lt-nox_core ovs-openflowd ovs-controller udpbwtest mnexec ivs 2> /dev/null
killall -9 controller ofprotocol ofdatapath ping nox_core lt-nox_core ovs-openflowd ovs-controller udpbwtest mnexec ivs 2> /dev/null
pkill -9 -f "sudo mnexec"
*** Removing junk from /tmp
rm -f /tmp/vconn* /tmp/vlogs* /tmp/*.out /tmp/*.log
*** Removing old X11 tunnels
*** Removing excess kernel datapaths
ps ax | egrep -o 'dp[0-9]+' | sed 's/dp/nl:/'
*** Removing OVS datapaths
ovs-vsctl --timeout=1 list-br
/bin/sh: ovs-vsctl: command not found
ovs-vsctl --timeout=1 list-br
/bin/sh: ovs-vsctl: command not found
*** Removing all links of the pattern foo-ethX
ip link show | egrep -o '([-_.[:alnum:]]+-eth[[:digit:]]+)'
ip link show
*** Killing stale mininet node processes
pkill -9 -f mininet:
*** Shutting down stale tunnels
pkill -9 -f Tunnel=Ethernet
pkill -9 -f .ssh/mn
rm -f ~/.ssh/mn/*
*** Cleanup complete.

pedromj commented on 2015-09-07 18:05

Done, please test. Thank you.

jetm commented on 2015-08-18 19:36

Hi @pedromj,

Could you change PKGBUILD to get mininet binary releases instead of using Git?

The mininet binary releases are in https://github.com/mininet/mininet/releases and you can get them with https://github.com/mininet/mininet/archive/VERSION.tar.gz, e.g.: https://github.com/mininet/mininet/archive/2.2.1.tar.gz

I cannot install this package because my current corporate Internet is through a proxy/firewall with git:// protocol blocked. Other people with similar Internet setup could have same issue.