documentation:examples:multicast_with_pim-sm
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| documentation:examples:multicast_with_pim-sm [2019/11/08 10:52] – [2. Check VM2 updates its mrouting table with discovered mcast source] olivier | documentation:examples:multicast_with_pim-sm [2019/11/08 18:55] – [Checking NIC drivers and Bhyve compatibility with multicast] olivier | ||
|---|---|---|---|
| Line 130: | Line 130: | ||
| </ | </ | ||
| + | ===== Checking NIC drivers and Bhyve compatibility with multicast ===== | ||
| + | |||
| + | Before to star with advanced routing setup, just start to test simple multicast between 2 relatives host: Some NIC (vtnet) or some hypervisors network setup aren't compliant with very simple multicast. | ||
| + | |||
| + | On VM1, start a mcast generator (client emitting mcast): | ||
| + | < | ||
| + | [root@VM1]~# | ||
| + | ------------------------------------------------------------ | ||
| + | Client connecting to 239.1.1.1, UDP port 5001 | ||
| + | Sending 1470 byte datagrams, IPG target: 11215.21 us (kalman adjust) | ||
| + | Setting multicast TTL to 32 | ||
| + | UDP buffer size: 9.00 KByte (default) | ||
| + | ------------------------------------------------------------ | ||
| + | [ 3] local 10.0.12.1 port 46636 connected with 239.1.1.1 port 5001 | ||
| + | [ ID] Interval | ||
| + | [ 3] 0.0- 1.0 sec 131 KBytes | ||
| + | [ 3] 1.0- 2.0 sec 128 KBytes | ||
| + | [ 3] 2.0- 3.0 sec 128 KBytes | ||
| + | [ 3] 0.0- 3.5 sec 446 KBytes | ||
| + | [ 3] Sent 311 datagrams | ||
| + | (...) | ||
| + | </ | ||
| + | |||
| + | On the direct connected VM2, start to check if in non-promiscious mode it sees mcast packets comming: | ||
| + | < | ||
| + | [root@VM2]~# | ||
| + | tcpdump: verbose output suppressed, use -v or -vv for full protocol decode | ||
| + | listening on em0, link-type EN10MB (Ethernet), capture size 262144 bytes | ||
| + | 15: | ||
| + | 15: | ||
| + | 2 packets captured | ||
| + | 2 packets received by filter | ||
| + | 0 packets dropped by kernel | ||
| + | </ | ||
| + | |||
| + | => VM2 is receiving mcast packets from 10.0.12.1 to mcast group 239.1.1.1. | ||
| + | Now on VM2 start a mcast listener (server receiving), it should receive multicast flow | ||
| + | |||
| + | < | ||
| + | [root@VM2]~# | ||
| + | ------------------------------------------------------------ | ||
| + | Server listening on UDP port 5001 | ||
| + | Binding to local address 239.1.1.1 | ||
| + | Joining multicast group 239.1.1.1 | ||
| + | Receiving 1470 byte datagrams | ||
| + | UDP buffer size: 41.1 KByte (default) | ||
| + | ------------------------------------------------------------ | ||
| + | [ 3] local 239.1.1.1 port 5001 connected with 192.168.100.149 port 35181 | ||
| + | [ ID] Interval | ||
| + | [ 3] 0.0- 1.0 sec 129 KBytes | ||
| + | [ 3] 1.0- 2.0 sec 128 KBytes | ||
| + | [ 3] 2.0- 3.0 sec 128 KBytes | ||
| + | [ 3] 3.0- 4.0 sec 128 KBytes | ||
| + | [ 3] 4.0- 5.0 sec 128 KBytes | ||
| + | [ 3] 5.0- 6.0 sec 129 KBytes | ||
| + | [ 3] 6.0- 7.0 sec 128 KBytes | ||
| + | (...) | ||
| + | </ | ||
| + | => Notice the mcast receiver is correctly receiving at 1Mb/s. | ||
| + | |||
| + | Here is a non working example (here because source interface not given): | ||
| + | < | ||
| + | [root@VM2]~# | ||
| + | ------------------------------------------------------------ | ||
| + | Server listening on UDP port 5001 | ||
| + | Binding to local address 239.1.1.1 | ||
| + | Joining multicast group 239.1.1.1 | ||
| + | Receiving 1470 byte datagrams | ||
| + | UDP buffer size: 41.1 KByte (default) | ||
| + | ------------------------------------------------------------ | ||
| + | (...) | ||
| + | </ | ||
| + | |||
| + | => Here it doesn' | ||
| ===== Checking pimd behavior ===== | ===== Checking pimd behavior ===== | ||
| Line 396: | Line 470: | ||
| < | < | ||
| - | [root@VM3]~# | + | [root@VM3]~# |
| Virtual Interface Table ====================================================== | Virtual Interface Table ====================================================== | ||
| Vif Local Address | Vif Local Address | ||
| --- --------------- | --- --------------- | ||
| 0 10.0.23.3 | 0 10.0.23.3 | ||
| - | 1 10.0.34.3 | + | 1 10.0.34.254 |
| 2 10.0.23.3 | 2 10.0.23.3 | ||
| Line 419: | Line 493: | ||
| TIMERS: | TIMERS: | ||
| - | | + | |
| ----------------------------------- (S,G) ------------------------------------ | ----------------------------------- (S,G) ------------------------------------ | ||
| Source | Source | ||
| Line 432: | Line 506: | ||
| TIMERS: | TIMERS: | ||
| - | 195 50 0 | + | 200 55 0 |
| --------------------------------- (*,*,G) ------------------------------------ | --------------------------------- (*,*,G) ------------------------------------ | ||
| Number of Groups: 1 | Number of Groups: 1 | ||
| Line 446: | Line 520: | ||
| IPv4 Virtual Interface Table | IPv4 Virtual Interface Table | ||
| | | ||
| - | 0 | + | 0 |
| - | 1 | + | 1 |
| 2 | 2 | ||
| IPv4 Multicast Forwarding Table | IPv4 Multicast Forwarding Table | ||
| | | ||
| - | | + | |
| Line 458: | Line 532: | ||
| IPv6 Multicast Forwarding Table is empty | IPv6 Multicast Forwarding Table is empty | ||
| - | |||
| </ | </ | ||
| - | VM3 correctly learn that there is a subscriber to group 239.1.1.1 on interface vif1 (toward VM4). | + | VM3 correctly learn that there is a subscriber to group 239.1.1.1 on interface vif1 (toward VM4) and the source is on vif0 (toward VM2). |
documentation/examples/multicast_with_pim-sm.txt · Last modified: 2019/11/08 19:22 by olivier