'I started Mininet, after generating xterm, encountered a connection that was rejected [closed]

I opened the mininet after running the following command:

$sudo mn -x

The following command was run in the switch window of Xterm:

$dpctl dump-flows tcp:127.0.0.1:6634

The following error arises:

dpctl: failed to send packet to switch: Connection refused

I do not know what the problem is.



Solution 1:[1]

try this command,

sudo ovs-ofctl dump-flows tcp:127.0.0.1:6634

for More info

Solution 2:[2]

It may be port:6634 didn't connect to any switch, but is instead used by the controller.

Connecting to remote controller at 127.0.0.1:6653

You should use the next one port after the controller eg. controller is at 6653, so try port 6654

You should use:

$ dpctl dump-flows tcp:127.0.0.1:6654

if you have 2 switches you can also use

dpctl dump-flows tcp:127.0.0.1:6655

Solution 3:[3]

The problem is because of the port number. startup Mininet in verbose mode and look at the passive listening ports for the switches when they’re created

running Mininet in verbose:

sudo mn -v debug

search for the line like this:

0*** c0 : ('echo A | telnet -e A 127.0.0.1 6653',)

Replace port# in:

$dpctl dump-flows tcp:127.0.0.1:6634

with:

$dpctl dump-flows tcp:127.0.0.1:6653

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 Jose Kj
Solution 2 Joshua T
Solution 3 reza_srt