You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Calling methods on a Mininet instance (e.g. ping, pingAll, etc.) should result in a warning or an error if the net has not been started.
Actual Behavior:
Commands e.g. ping silently fail when Mininet instance is not started
Detailed Steps to Reproduce the Behavior:
from mininet.topo import MinimalTopo
from mininet.net import Mininet
from mininet.cli import CLI
topo = MinimalTopo()
net = Mininet(topo)
# net.start()
net.pingAll()
CLI(net)
The pingAll() gets stuck on h1 when net.start() is not called. If the line is removed and the ping command is tried through the CLI, the same thing happens.
Additional Information:
This is one of those obvious errors where people are supposed to start the network before running it, but it's also a very simple QoL fix that can save a lot of time if this error does occur. I ran into this issue and spent a few days trying to fix my topology rather than my initialization script because I didn't realize I had accidentally removed the net.start() when refactoring my code. A message like "Warning: Mininet instance has not been initialized. Did you call start()?" or an error would have saved a lot of time.
The text was updated successfully, but these errors were encountered:
Expected/Desired Behavior:
Calling methods on a Mininet instance (e.g. ping, pingAll, etc.) should result in a warning or an error if the net has not been started.
Actual Behavior:
Commands e.g. ping silently fail when Mininet instance is not started
Detailed Steps to Reproduce the Behavior:
The
pingAll()
gets stuck on h1 whennet.start()
is not called. If the line is removed and the ping command is tried through the CLI, the same thing happens.Additional Information:
This is one of those obvious errors where people are supposed to start the network before running it, but it's also a very simple QoL fix that can save a lot of time if this error does occur. I ran into this issue and spent a few days trying to fix my topology rather than my initialization script because I didn't realize I had accidentally removed the
net.start()
when refactoring my code. A message like "Warning: Mininet instance has not been initialized. Did you call start()?" or an error would have saved a lot of time.The text was updated successfully, but these errors were encountered: