Package Details: mininet 2.3.0-1

Git Clone URL: (read-only, click to copy)
Package Base: mininet
Description: Emulator for rapid prototyping of Software Defined Networks
Upstream URL:
Keywords: mininet openflow sdn
Licenses: custom
Submitter: pedromj
Maintainer: kyechou
Last Packager: kyechou
Votes: 15
Popularity: 0.144789
First Submitted: 2014-11-07 17:38 (UTC)
Last Updated: 2021-02-18 16:52 (UTC)

Latest Comments

1 2 3 Next › Last »

mroethke commented on 2019-07-03 10:10 (UTC)

I seems mininet needs cgcreate out of libcgroup, can you please add that to the dependencies?

Tomaash commented on 2019-02-18 20:45 (UTC)

Package xbitmaps probably should be an optional dependency because MiniEdit crashes without it.

ecklm commented on 2018-10-09 08:10 (UTC)

I have sent you a patch in email. Could you please apply that?

pedromj commented on 2018-05-07 06:45 (UTC)

I have updated to "2.2.2", please test it. Thank you.

Percee commented on 2017-11-07 14:53 (UTC)

To be able to use xterm h1 inside the cli, one should install the package xorg-xhost first

cemsbr commented on 2016-08-10 17:11 (UTC)

# 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 (UTC)

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] [2]

martinjlowm commented on 2016-05-07 10:17 (UTC)

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 ( 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 (UTC)

I've updated the package. Please test it.

jetm commented on 2015-09-30 17:54 (UTC)

@glindste: Thanks! With your suggestions mininet runs as it's expected. @pedromj: 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. Regards.