[Bug 202959] Fix net/pimd build with clang 3.7.0
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Wed Sep 16 21:28:01 UTC 2015
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202959
--- Comment #3 from olivier at cochard.me ---
(In reply to Hiroki Sato from comment #2)
My multicast virtual lab didn't works once I've upgraded pimd to 2.3.0.
My virtual lab detail:
http://bsdrp.net/documentation/examples/multicast_with_pim-sm
Once pimd started on the multicast router (R2 and R3), when R4 ask for joining
a mcast group:
[root at R4]~# mtest
multicast membership test program; enter ? for list of commands
j 239.1.1.1 em2 10.0.12.1
ok
R3 correctly received the join request:
[root at R3]~# tcpdump -ni em2 -vv
tcpdump: listening on em2, link-type EN10MB (Ethernet), capture size 65535
10.0.34.4 > 224.0.0.22: igmp v3 report, 1 group record(s) [gaddr 239.1.1.1
to_in { 10.0.12.1 }]
22:41:02.438726 IP (tos 0xc0, ttl 1, id 741, offset 0, flags [DF], proto IGMP
(2), length 44, options (RA))
10.0.34.4 > 224.0.0.22: igmp v3 report, 1 group record(s) [gaddr 239.1.1.1
to_in { 10.0.12.1 }]
But it didn't update its mcast table anymore by showing a new mcast subscriber
:-(
[root at R3]~# pimd -r
Virtual Interface Table ======================================================
Vif Local Address Subnet Thresh Flags Neighbors
--- --------------- ------------------ ------ --------- -----------------
0 10.0.23.3 10.0.23/24 1 DR PIM 10.0.23.2
1 10.0.34.3 10.0.34/24 1 DR NO-NBR
2 10.0.23.3 register_vif0 1
Vif SSM Group Sources
Multicast Routing Table ======================================================
--------------------------------- (*,*,G) ------------------------------------
Number of Groups: 0
Number of Cache MIRRORs: 0
------------------------------------------------------------------------------
Because iperf is igmpv2 only, I've tried with mcastread, but same behavior:
[root at R4]~# mcastread -v4 -s 10.0.12.1 em2 239.1.1.1 9090
mcastread: trying 239.1.1.1
mcastread: using (S,G)=(10.0.12.1,239.1.1.1)
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list