MUNET beginner questions

[aaronzhang194]

Hi,

For the two hosts topology in the example, I tried the interactive shell command "ping":

munet> h1 shi ping 10.0.1.1
PING 10.0.1.1 (10.0.1.1) 56(84) bytes of data.
64 bytes from 10.0.1.1: icmp_seq=1 ttl=64 time=0.023 ms
64 bytes from 10.0.1.1: icmp_seq=2 ttl=64 time=0.023 ms
64 bytes from 10.0.1.1: icmp_seq=3 ttl=64 time=0.057 ms
64 bytes from 10.0.1.1: icmp_seq=4 ttl=64 time=0.059 ms
64 bytes from 10.0.1.1: icmp_seq=5 ttl=64 time=0.056 ms
64 bytes from 10.0.1.1: icmp_seq=6 ttl=64 time=0.055 ms
64 bytes from 10.0.1.1: icmp_seq=7 ttl=64 time=0.054 ms
64 bytes from 10.0.1.1: icmp_seq=8 ttl=64 time=0.056 ms
64 bytes from 10.0.1.1: icmp_seq=9 ttl=64 time=0.059 ms
64 bytes from 10.0.1.1: icmp_seq=10 ttl=64 time=0.071 ms
64 bytes from 10.0.1.1: icmp_seq=11 ttl=64 time=0.056 ms
^C64 bytes from 10.0.1.1: icmp_seq=12 ttl=64 time=0.057 ms
64 bytes from 10.0.1.1: icmp_seq=13 ttl=64 time=0.056 ms
^C^C64 bytes from 10.0.1.1: icmp_seq=14 ttl=64 time=0.058 ms

But I can't get out of it. ^C does not do it.
What could I do to break out of it?

Thanks.
Aaron

[liambrady]

Hey Aaron,

This probably is some sort of bug with how signals are being processed/passed by munet when running commands from the munet CLI. However, you can accomplish the same task by directly opening a shell in h1 and then starting your ping.

e.g:

munet> term h1
h1# ping 10.0.1.1

Note that this approach requires you to either be running inside a tmux session (recommended, but you have to run munet with sudo -E) or have xterm installed.

[aaronzhang194]

That worked!
I had tried "term" before, but it did not work until you pointed out to install xterm/tmux.
Thanks!