pingall problem

1,410 views

Skip to first unread message

Syed Naveed Abbas Rizvi

unread,

Jun 19, 2013, 4:23:34 PM6/19/13

to routeflo...@googlegroups.com

hello friends

i am new to route flow and i am going through the rftest2 tutorial. But i am getting 100% loss on pingall.

I am running mininet vm on virtual box on the same machine as routeflow. please guide me to solve this problem.

rizvi@rizvi-SDN:~/RouteFlow/rftest$ sudo ./rftest2

-> Starting rftest2

-> Stopping and resetting LXC VMs...

rfvmF is not running

rfvmB is not running

rfvmC is not running

rfvmD is not running

-> Deleting (previous) run data...

MongoDB shell version: 2.0.4

connecting to: db

false

-> Setting up the management bridge (lxcbr0)...

-> Setting up MongoDB...

mongodb stop/waiting

mongodb start/running, process 10949

.-> Configuring the virtual machines...

-> Starting the virtual machines...

-> Starting the controller and RFPRoxy...

/home/rizvi/RouteFlow

INFO:rfproxy:RFProxy running.

INFO:core:POX 0.1.0 (betta) is up.

-> Starting RFServer...

-> Starting the control plane network (dp0 VS)...

INFO:openflow.of_01:[None 1] closed

---

This test is up and running.

Start Mininet:

$ sudo mn --custom mininet/custom/topo-4sw-4host.py --topo=rftest2

--controller=remote,ip=[host address],port=6633 --pre=ipconf

Replace [host address] with the address of this host's interface

connected to the Mininet VM.

Then try pinging everything:

mininet> pingall

You can stop this test by pressing CTRL+C.

---

INFO:openflow.of_01:[76-73-72-66-76-73|29286 2] connected

INFO:openflow.topology:Switch 76-73-72-66-76-73|29286 connected

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=1)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=2)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=3)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=4)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=5)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=6)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=7)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=8)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=9)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=10)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=11)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=12)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=13)

INFO:rfserver:Configuring RFVS (dp_id=0x7266767372667673)

INFO:rfproxy:routemod sent to datapath (dp_id=0x7266767372667673)

INFO:rfserver:Registering client port as idle (vm_id=0x2b0b0b0b0b0, vm_port=1, eth_addr=02:b1:b1:b1:b1:b1)

INFO:rfserver:Registering client port as idle (vm_id=0x2b0b0b0b0b0, vm_port=2, eth_addr=02:b2:b2:b2:b2:b2)

INFO:rfserver:Registering client port as idle (vm_id=0x2b0b0b0b0b0, vm_port=3, eth_addr=02:b3:b3:b3:b3:b3)

INFO:rfserver:Registering client port as idle (vm_id=0x2f0f0f0f0f0, vm_port=1, eth_addr=02:f1:f1:f1:f1:f1)

INFO:rfserver:Registering client port as idle (vm_id=0x2f0f0f0f0f0, vm_port=2, eth_addr=02:f2:f2:f2:f2:f2)

INFO:rfserver:Registering client port as idle (vm_id=0x2f0f0f0f0f0, vm_port=3, eth_addr=02:f3:f3:f3:f3:f3)

INFO:rfserver:Registering client port as idle (vm_id=0x2c0c0c0c0c0, vm_port=1, eth_addr=02:c1:c1:c1:c1:c1)

INFO:rfserver:Registering client port as idle (vm_id=0x2c0c0c0c0c0, vm_port=2, eth_addr=02:c2:c2:c2:c2:c2)

INFO:rfserver:Registering client port as idle (vm_id=0x2c0c0c0c0c0, vm_port=3, eth_addr=02:c3:c3:c3:c3:c3)

INFO:rfserver:Registering client port as idle (vm_id=0x2d0d0d0d0d0, vm_port=1, eth_addr=02:d1:d1:d1:d1:d1)

INFO:rfserver:Registering client port as idle (vm_id=0x2d0d0d0d0d0, vm_port=2, eth_addr=02:d2:d2:d2:d2:d2)

INFO:rfserver:Registering client port as idle (vm_id=0x2d0d0d0d0d0, vm_port=3, eth_addr=02:d3:d3:d3:d3:d3)

INFO:rfserver:Registering client port as idle (vm_id=0x2d0d0d0d0d0, vm_port=4, eth_addr=02:d4:d4:d4:d4:d4)

Aleksandr Vilchinskii

unread,

Jun 19, 2013, 4:40:14 PM6/19/13

to routeflo...@googlegroups.com

Hi,

Just to clarify. Have you replaced the [host address] with the IP address to access the host from inside the VM in the command calling mininet? Is it possible to ping the VM with mininet from your host?

Best regards,

Aleksandr Vilchinskii

Syed Naveed Abbas Rizvi

unread,

Jun 24, 2013, 2:31:12 PM6/24/13

to routeflo...@googlegroups.com

Dear Aleksandar

Thanks for the reply now I can run the pingall in mininet VM with 100% reachability. I was not using the correct host IP for controller. I also figured out that after running rftest1 we need to manually remove rfvm1 because it uses the same mac addr as rfvmA. Therefore rfvmA is not going to start due to this.

I also tried to use the mininet that is installed on my host (not VM) to run with rftest2 with host ip 127.0.0.1, but Im getting 100% packet loss, can you comment on this?

rizvi@rizvi-SDN:~$ sudo mn --custom ~/mininet/custom/topo-4sw-4host.py --topo=rftest2 --controller=remote,ip=127.0.0.1,port=6633 --pre=ipconf

*** Creating network

*** Adding controller

*** Adding hosts:

h1 h2 h3 h4

*** Adding switches:

s5 s6 s7 s8

*** Adding links:

(h1, s5) (h2, s6) (h3, s7) (h4, s8) (s5, s6) (s5, s7) (s5, s8) (s6, s8) (s7, s8)

*** Configuring hosts

h1 h2 h3 h4

*** Starting CLI:

error reading file ipconf

*** Starting controller

*** Starting 4 switches

s5 s6 s7 s8

*** Starting CLI:

mininet> pingall

*** Ping: testing ping reachability

h1 -> X X X

h2 -> X X X

h3 -> X X X

h4 -> X X X

*** Results: 100% dropped (12/12 lost)

mininet> pingall

*** Ping: testing ping reachability

h1 -> X X X

h2 -> X X X

h3 -> X X X

h4 -> X X X

*** Results: 100% dropped (12/12 lost)

here is the rftest2 log:

rizvi@rizvi-SDN:~/RouteFlow/rftest$ sudo ./rftest2

-> Starting rftest2

-> Stopping and resetting LXC VMs...

rfvmA is not running

rfvmB is not running

rfvmC is not running

rfvmD is not running

-> Deleting (previous) run data...

MongoDB shell version: 2.0.4

connecting to: db

false

-> Setting up the management bridge (lxcbr0)...

-> Setting up MongoDB...

mongodb stop/waiting

mongodb start/running, process 24156

INFO:rfserver:Configuring RFVS (dp_id=0x7266767372667673)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=4)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=5)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=6)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=7)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=8)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=9)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=10)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=11)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=12)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=13)

INFO:rfproxy:Registering datapath port (dp_id=0x7266767372667673, dp_port=14)

INFO:rfproxy:routemod sent to datapath (dp_id=0x7266767372667673)

INFO:rfserver:Registering client port as idle (vm_id=0x2a0a0a0a0a0, vm_port=1, eth_addr=02:a1:a1:a1:a1:a1)

INFO:rfserver:Registering client port as idle (vm_id=0x2a0a0a0a0a0, vm_port=2, eth_addr=02:a2:a2:a2:a2:a2)

INFO:rfserver:Registering client port as idle (vm_id=0x2a0a0a0a0a0, vm_port=3, eth_addr=02:a3:a3:a3:a3:a3)

INFO:rfserver:Registering client port as idle (vm_id=0x2a0a0a0a0a0, vm_port=4, eth_addr=02:a4:a4:a4:a4:a4)

INFO:openflow.of_01:[00-00-00-00-00-05 3] connected

INFO:openflow.topology:Switch 00-00-00-00-00-05 connected

INFO:rfproxy:Registering datapath port (dp_id=0x5, dp_port=1)

INFO:rfproxy:Registering datapath port (dp_id=0x5, dp_port=2)

INFO:rfproxy:Registering datapath port (dp_id=0x5, dp_port=3)

INFO:rfproxy:Registering datapath port (dp_id=0x5, dp_port=4)

INFO:openflow.of_01:[00-00-00-00-00-08 5] connected

INFO:openflow.topology:Switch 00-00-00-00-00-08 connected

INFO:rfproxy:Registering datapath port (dp_id=0x8, dp_port=1)

INFO:rfproxy:Registering datapath port (dp_id=0x8, dp_port=2)

INFO:rfproxy:Registering datapath port (dp_id=0x8, dp_port=3)

INFO:rfproxy:Registering datapath port (dp_id=0x8, dp_port=4)

INFO:openflow.of_01:[00-00-00-00-00-06 6] connected

INFO:rfserver:Asking client for mapping message for port (vm_id=0x2a0a0a0a0a0, vm_port=1)

INFO:rfserver:Registering datapath port and associating to client port (dp_id=0x5, dp_port=1, vm_id=0x2a0a0a0a0a0, vm_port=1)

INFO:openflow.topology:Switch 00-00-00-00-00-06 connected

INFO:rfproxy:Registering datapath port (dp_id=0x6, dp_port=1)

INFO:rfproxy:Registering datapath port (dp_id=0x6, dp_port=2)

INFO:rfproxy:Registering datapath port (dp_id=0x6, dp_port=3)

INFO:openflow.of_01:[00-00-00-00-00-07 4] connected

INFO:openflow.topology:Switch 00-00-00-00-00-07 connected

INFO:rfproxy:Registering datapath port (dp_id=0x7, dp_port=1)

INFO:rfproxy:Registering datapath port (dp_id=0x7, dp_port=2)

INFO:rfproxy:Registering datapath port (dp_id=0x7, dp_port=3)

INFO:rfserver:Configuring datapath (dp_id=0x5)

INFO:rfserver:Asking client for mapping message for port (vm_id=0x2a0a0a0a0a0, vm_port=2)

INFO:rfserver:Registering datapath port and associating to client port (dp_id=0x5, dp_port=2, vm_id=0x2a0a0a0a0a0, vm_port=2)

INFO:rfproxy:routemod sent to datapath (dp_id=0x5)

INFO:rfserver:Configuring datapath (dp_id=0x5)

INFO:rfproxy:routemod sent to datapath (dp_id=0x5)

INFO:rfserver:Asking client for mapping message for port (vm_id=0x2a0a0a0a0a0, vm_port=3)

INFO:rfserver:Registering datapath port and associating to client port (dp_id=0x5, dp_port=3, vm_id=0x2a0a0a0a0a0, vm_port=3)

INFO:rfserver:Configuring datapath (dp_id=0x5)

INFO:rfserver:Asking client for mapping message for port (vm_id=0x2a0a0a0a0a0, vm_port=4)

INFO:rfserver:Registering datapath port and associating to client port (dp_id=0x5, dp_port=4, vm_id=0x2a0a0a0a0a0, vm_port=4)

INFO:rfserver:Registering datapath port as idle (dp_id=0x8, dp_port=1)

INFO:rfserver:Configuring datapath (dp_id=0x8)

INFO:rfserver:Registering datapath port as idle (dp_id=0x8, dp_port=2)

INFO:rfserver:Configuring datapath (dp_id=0x8)

INFO:rfserver:Registering datapath port as idle (dp_id=0x8, dp_port=3)

INFO:rfproxy:Received mapping packet (vm_id=0x2a0a0a0a0a0, vm_port=1, vs_id=8243406406160905843, vs_port=1)

INFO:rfproxy:routemod sent to datapath (dp_id=0x5)

INFO:rfproxy:routemod sent to datapath (dp_id=0x8)

INFO:rfserver:Configuring datapath (dp_id=0x8)

INFO:rfserver:Registering datapath port as idle (dp_id=0x8, dp_port=4)

INFO:rfserver:Registering datapath port as idle (dp_id=0x6, dp_port=1)

INFO:rfserver:Configuring datapath (dp_id=0x6)

INFO:rfserver:Registering datapath port as idle (dp_id=0x6, dp_port=2)

INFO:rfserver:Configuring datapath (dp_id=0x6)

INFO:rfserver:Registering datapath port as idle (dp_id=0x6, dp_port=3)

INFO:rfserver:Registering datapath port as idle (dp_id=0x7, dp_port=1)

INFO:rfproxy:Received mapping packet (vm_id=0x2a0a0a0a0a0, vm_port=2, vs_id=8243406406160905843, vs_port=2)

INFO:rfproxy:Received mapping packet (vm_id=0x2a0a0a0a0a0, vm_port=3, vs_id=8243406406160905843, vs_port=3)

INFO:rfserver:Configuring datapath (dp_id=0x7)

INFO:rfserver:Registering datapath port as idle (dp_id=0x7, dp_port=2)

INFO:rfserver:Configuring datapath (dp_id=0x7)

INFO:rfserver:Registering datapath port as idle (dp_id=0x7, dp_port=3)

INFO:rfserver:Mapping client-datapath association (vm_id=0x2a0a0a0a0a0, vm_port=1, dp_id=0x5, dp_port=1, vs_id=0x7266767372667673, vs_port=1)

INFO:rfproxy:routemod sent to datapath (dp_id=0x8)

INFO:rfproxy:routemod sent to datapath (dp_id=0x6)

INFO:rfproxy:routemod sent to datapath (dp_id=0x7)

INFO:rfserver:Mapping client-datapath association (vm_id=0x2a0a0a0a0a0, vm_port=2, dp_id=0x5, dp_port=2, vs_id=0x7266767372667673, vs_port=2)

INFO:rfproxy:Received mapping packet (vm_id=0x2a0a0a0a0a0, vm_port=4, vs_id=8243406406160905843, vs_port=4)

INFO:rfserver:Mapping client-datapath association (vm_id=0x2a0a0a0a0a0, vm_port=3, dp_id=0x5, dp_port=3, vs_id=0x7266767372667673, vs_port=3)

INFO:rfserver:Mapping client-datapath association (vm_id=0x2a0a0a0a0a0, vm_port=4, dp_id=0x5, dp_port=4, vs_id=0x7266767372667673, vs_port=4)

INFO:openflow.of_01:[None 7] closed

INFO:openflow.of_01:[00-00-00-00-00-05 8] connected

WARNING:openflow.topology:Switch 00-00-00-00-00-05 connected, but... it's already connected!

INFO:openflow.topology:Switch 00-00-00-00-00-05 connected

INFO:rfproxy:Registering datapath port (dp_id=0x5, dp_port=1)

INFO:rfproxy:Registering datapath port (dp_id=0x5, dp_port=2)

INFO:rfproxy:Registering datapath port (dp_id=0x5, dp_port=3)

INFO:rfproxy:Registering datapath port (dp_id=0x5, dp_port=4)

INFO:rfserver:Configuring datapath (dp_id=0x5)

INFO:rfproxy:routemod sent to datapath (dp_id=0x5)

INFO:rfserver:Configuring datapath (dp_id=0x5)

INFO:openflow.of_01:[00-00-00-00-00-06 9] connected

WARNING:openflow.topology:Switch 00-00-00-00-00-06 connected, but... it's already connected!

INFO:openflow.topology:Switch 00-00-00-00-00-06 connected

INFO:rfproxy:Registering datapath port (dp_id=0x6, dp_port=1)

INFO:rfproxy:Registering datapath port (dp_id=0x6, dp_port=2)

INFO:rfproxy:Registering datapath port (dp_id=0x6, dp_port=3)

INFO:rfproxy:routemod sent to datapath (dp_id=0x5)

INFO:rfserver:Configuring datapath (dp_id=0x6)

INFO:rfproxy:routemod sent to datapath (dp_id=0x5)

INFO:rfserver:Registering datapath port as idle (dp_id=0x6, dp_port=1)

INFO:openflow.of_01:[00-00-00-00-00-07 10] connected

WARNING:openflow.topology:Switch 00-00-00-00-00-07 connected, but... it's already connected!

INFO:openflow.topology:Switch 00-00-00-00-00-07 connected

INFO:rfproxy:Registering datapath port (dp_id=0x7, dp_port=1)

INFO:rfproxy:Registering datapath port (dp_id=0x7, dp_port=2)

INFO:rfproxy:Registering datapath port (dp_id=0x7, dp_port=3)

INFO:rfserver:Configuring datapath (dp_id=0x6)

INFO:rfserver:Registering datapath port as idle (dp_id=0x6, dp_port=2)

INFO:rfserver:Configuring datapath (dp_id=0x6)

INFO:rfserver:Registering datapath port as idle (dp_id=0x6, dp_port=3)

INFO:rfproxy:routemod sent to datapath (dp_id=0x6)

INFO:rfserver:Configuring datapath (dp_id=0x7)

INFO:rfproxy:routemod sent to datapath (dp_id=0x6)

INFO:rfserver:Registering datapath port as idle (dp_id=0x7, dp_port=1)

INFO:rfproxy:routemod sent to datapath (dp_id=0x6)

INFO:rfserver:Configuring datapath (dp_id=0x7)

INFO:rfserver:Registering datapath port as idle (dp_id=0x7, dp_port=2)

INFO:rfserver:Configuring datapath (dp_id=0x7)

INFO:rfserver:Registering datapath port as idle (dp_id=0x7, dp_port=3)

INFO:openflow.of_01:[00-00-00-00-00-08 11] connected

WARNING:openflow.topology:Switch 00-00-00-00-00-08 connected, but... it's already connected!

INFO:openflow.topology:Switch 00-00-00-00-00-08 connected

INFO:rfproxy:Registering datapath port (dp_id=0x8, dp_port=1)

INFO:rfproxy:Registering datapath port (dp_id=0x8, dp_port=2)

INFO:rfproxy:Registering datapath port (dp_id=0x8, dp_port=3)

INFO:rfproxy:Registering datapath port (dp_id=0x8, dp_port=4)

INFO:rfproxy:routemod sent to datapath (dp_id=0x7)

INFO:rfserver:Configuring datapath (dp_id=0x8)

INFO:rfproxy:routemod sent to datapath (dp_id=0x7)

INFO:rfserver:Registering datapath port as idle (dp_id=0x8, dp_port=1)

INFO:rfproxy:routemod sent to datapath (dp_id=0x7)

INFO:rfserver:Configuring datapath (dp_id=0x8)

INFO:rfserver:Registering datapath port as idle (dp_id=0x8, dp_port=2)

INFO:rfserver:Configuring datapath (dp_id=0x8)

INFO:rfserver:Registering datapath port as idle (dp_id=0x8, dp_port=3)

INFO:rfserver:Configuring datapath (dp_id=0x8)

INFO:rfserver:Registering datapath port as idle (dp_id=0x8, dp_port=4)

INFO:rfproxy:routemod sent to datapath (dp_id=0x8)

Allan Vidal

unread,

Jun 25, 2013, 7:27:56 AM6/25/13

to routeflo...@googlegroups.com

Hi Syed,

It seems that only rfvmA is being started... Since rfvmB, rfvmC and rfvmD are essential (they act as the brains for the other routers, each connected to a host), you can't ping other hosts.

You'll have to check why they're not starting. Try doing it manually:

sudo lxc-start -n rfvmB

If they're started:

sudo lxc-console -n rfvmB

And then check what is happening at:

cat /var/log/rfclient.log

Allan

--
You received this message because you are subscribed to the Google Groups "RouteFlow" group.
To unsubscribe from this group and stop receiving emails from it, send an email to routeflow-disc...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Syed Naveed Abbas Rizvi

unread,

Jun 27, 2013, 10:30:42 AM6/27/13

to routeflo...@googlegroups.com

yeah you were correct ... now its working fine...i dont know why but some times LXC do no start properly.

mly

unread,

Feb 5, 2016, 5:36:59 AM2/5/16

to RouteFlow, all...@cpqd.com.br

Hi,

Could you help me?

I can't ping rftest2...these are the problem.

i've login on rfvmA, rfvmB, rfvmC, and rfvmD (I follow the rftest1 step, that we shoul log in first), use this command:

sudo lxc-console -n rfvmA

sudo lxc-console -n rfvmB

sudo lxc-console -n rfvmC

sudo lxc-console -n rfvmD

------------------------

then i try to all rfvmA, rfvmB, rfvmC, rfvmD, these command below (routing table and ARP table)

sudo sudo route -n

sudo arp -a

------------

then i tried sudo mn with this command:

:~$ sudo mn --custom mininet/custom/topo-4sw-4host.py --topo=rftest2 --controller=remote,ip=[192.168.56.1],port=6633 --pre=ipconf

is there a wrong IP Address in the host? i used 192.168.56.1..

i've read on this group, there's someone who used 127.0.0.1. so which one should i choose?

But i can not log in to h1, h2, h3, also h4.... Should i log in like b1 and b2 in rftest1?

But it's still not working to ping all the host. (destination host unreachable)

And i've copy the file "ipconf" from RouteFlor/rftest/ to folder home/mininet/

But the output still error reading file ipconf

This is file ipconf:

h1 ifconfig h1-eth0 172.31.1.100 netmask 255.255.255.0
h2 ifconfig h2-eth0 172.31.2.100 netmask 255.255.255.0
h3 ifconfig h3-eth0 172.31.3.100 netmask 255.255.255.0
h4 ifconfig h4-eth0 172.31.4.100 netmask 255.255.255.0

h1 route add default gw 172.31.1.1
h2 route add default gw 172.31.2.1
h3 route add default gw 172.31.3.1
h4 route add default gw 172.31.4.1

:~$ sudo mn --custom mininet/custom/topo-4sw-4host.py --topo=rftest2 --controller=remote,ip=[192.168.56.1],port=6633 --pre=ipconf

*** Creating network

*** Adding controller

*** Adding hosts:

h1 h2 h3 h4

*** Adding switches:

s5 s6 s7 s8

*** Adding links:

(h1, s5) (h2, s6) (h3, s7) (h4, s8) (s5, s6) (s5, s7) (s5, s8) (s6, s8) (s7, s8)

*** Configuring hosts

h1 h2 h3 h4

*** Starting CLI:

error reading file ipconf

*** Starting controller

*** Starting 4 switches

s5 s6 s7 s8

*** Starting CLI:

mininet> h1 ifconfig h1-eth0 172.31.1.100 netmask 255.255.255.0

mininet> h2 ifconfig h2-eth0 172.31.2.100 netmask 255.255.255.0

mininet> h3 ifconfig h3-eth0 172.31.3.100 netmask 255.255.255.0

mininet> h4 ifconfig h4-eth0 172.31.4.100 netmask 255.255.255.0

mininet> h1 route add default gw 172.31.1.1

mininet> h2 route add default gw 172.31.2.1

mininet> h3 route add default gw 172.31.3.1

mininet> h4 route add default gw 172.31.4.1

mininet> h1 ifconfig

h1-eth0 Link encap:Ethernet HWaddr 02:72:d6:50:4a:6c

inet addr:172.31.1.100 Bcast:172.31.1.255 Mask:255.255.255.0

inet6 addr: fe80::72:d6ff:fe50:4a6c/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:32 errors:0 dropped:0 overruns:0 frame:0

TX packets:8 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:5312 (5.3 KB) TX bytes:648 (648.0 B)

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

mininet> h2 ifconfig

h2-eth0 Link encap:Ethernet HWaddr ca:2e:c5:42:04:69

inet addr:172.31.2.100 Bcast:172.31.2.255 Mask:255.255.255.0

inet6 addr: fe80::c82e:c5ff:fe42:469/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:49 errors:0 dropped:0 overruns:0 frame:0

TX packets:8 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:8774 (8.7 KB) TX bytes:648 (648.0 B)

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

mininet> h3 ifconfig

h3-eth0 Link encap:Ethernet HWaddr 76:4e:5a:82:70:30

inet addr:172.31.3.100 Bcast:172.31.3.255 Mask:255.255.255.0

inet6 addr: fe80::744e:5aff:fe82:7030/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:54 errors:0 dropped:0 overruns:0 frame:0

TX packets:8 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:9298 (9.2 KB) TX bytes:648 (648.0 B)

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

mininet> h4 ifconfig

h4-eth0 Link encap:Ethernet HWaddr 36:5d:71:b8:e4:91

inet addr:172.31.4.100 Bcast:172.31.4.255 Mask:255.255.255.0

inet6 addr: fe80::345d:71ff:feb8:e491/64 Scope:Link

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:54 errors:0 dropped:0 overruns:0 frame:0

TX packets:8 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:1000

RX bytes:9672 (9.6 KB) TX bytes:648 (648.0 B)

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0

inet6 addr: ::1/128 Scope:Host

UP LOOPBACK RUNNING MTU:65536 Metric:1

RX packets:0 errors:0 dropped:0 overruns:0 frame:0

TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

collisions:0 txqueuelen:0

RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

mininet> h1 ping h2

PING 172.31.2.100 (172.31.2.100) 56(84) bytes of data.

From 172.31.1.100 icmp_seq=1 Destination Host Unreachable

From 172.31.1.100 icmp_seq=2 Destination Host Unreachable

From 172.31.1.100 icmp_seq=3 Destination Host Unreachable

From 172.31.1.100 icmp_seq=4 Destination Host Unreachable

From 172.31.1.100 icmp_seq=5 Destination Host Unreachable

From 172.31.1.100 icmp_seq=6 Destination Host Unreachable

--- 172.31.2.100 ping statistics ---

8 packets transmitted, 0 received, +6 errors, 100% packet loss, time 7031ms

Thankyou so much!

...

Reply all

Reply to author

Forward

0 new messages