High PING (rftest1)

[Fernando Cappi]

Hi,

I pull the updates from github and now, when i try to ping b2 from b1, i get the following PING values:

ubuntu@b1:~$ ping 172.31.2.2
PING 172.31.2.2 (172.31.2.2) 56(84) bytes of data.
64 bytes from 172.31.2.2: icmp_req=1 ttl=63 time=42.1 ms
64 bytes from 172.31.2.2: icmp_req=2 ttl=63 time=83.7 ms
64 bytes from 172.31.2.2: icmp_req=3 ttl=63 time=45.0 ms
64 bytes from 172.31.2.2: icmp_req=4 ttl=63 time=39.2 ms
64 bytes from 172.31.2.2: icmp_req=5 ttl=63 time=33.0 ms
64 bytes from 172.31.2.2: icmp_req=6 ttl=63 time=26.6 ms
64 bytes from 172.31.2.2: icmp_req=7 ttl=63 time=9.80 ms
64 bytes from 172.31.2.2: icmp_req=8 ttl=63 time=10.3 ms
64 bytes from 172.31.2.2: icmp_req=9 ttl=63 time=54.0 ms
64 bytes from 172.31.2.2: icmp_req=10 ttl=63 time=46.6 ms
64 bytes from 172.31.2.2: icmp_req=11 ttl=63 time=40.4 ms
64 bytes from 172.31.2.2: icmp_req=12 ttl=63 time=18.6 ms
64 bytes from 172.31.2.2: icmp_req=13 ttl=63 time=10.0 ms
64 bytes from 172.31.2.2: icmp_req=14 ttl=63 time=52.7 ms
64 bytes from 172.31.2.2: icmp_req=15 ttl=63 time=43.9 ms
64 bytes from 172.31.2.2: icmp_req=16 ttl=63 time=23.3 ms
64 bytes from 172.31.2.2: icmp_req=17 ttl=63 time=15.0 ms
64 bytes from 172.31.2.2: icmp_req=18 ttl=63 time=39.4 ms
64 bytes from 172.31.2.2: icmp_req=19 ttl=63 time=32.0 ms
64 bytes from 172.31.2.2: icmp_req=20 ttl=63 time=23.2 ms
64 bytes from 172.31.2.2: icmp_req=21 ttl=63 time=51.7 ms
64 bytes from 172.31.2.2: icmp_req=22 ttl=63 time=44.0 ms
64 bytes from 172.31.2.2: icmp_req=23 ttl=63 time=5.80 ms
64 bytes from 172.31.2.2: icmp_req=24 ttl=63 time=48.5 ms
64 bytes from 172.31.2.2: icmp_req=25 ttl=63 time=89.0 ms
64 bytes from 172.31.2.2: icmp_req=26 ttl=63 time=15.8 ms
64 bytes from 172.31.2.2: icmp_req=27 ttl=63 time=58.3 ms
^C
--- 172.31.2.2 ping statistics ---
27 packets transmitted, 27 received, 0% packet loss, time 26039ms
rtt min/avg/max/mdev = 5.803/37.147/89.002/20.617 ms

[Christian Esteve Rothenberg]

that is expected, now by default the ping packets go via the controller, see the discussion in the latest github commits related to the Cardigan contributions.

An optimization to keep PING traffic among hosts in the data plane is very simple to implement, but we have decided for now not to have it by default. The reason being that control plane traffic match high priority rules with the action set to the controller.

-Ch

--
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.
 
 

--
Christian Esteve Rothenberg, Ph.D.
Converged Networks Business Unit
CPqD - Center for Research and Development in Telecommunications
Tel. (+55 19) 3705 4479 / Cel. (+55 19) 8193-7087

[Fernando Cappi]

OK Christian, Thanks