You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I've compiled pimd on a Linux and for now I would like to test it as a single multicast router for testing purposes.
Actually for a VXLAN scenario to connect 2 different data centers.
10.14.11.1 is the ip address of the interface tun0, so pimd is configured with itself as RP
The VXLAN is configured with the 239.13.13.3 multicast address
PublicIP1 and PublicIP2 are the Source ip addresses of the VXLAN VTEPs that send messages to 239.13.13.3
When I start pimd -n -l debug, I see:
# pimd -n -l debug
pimd: 09:26:18.925 pimd version 3.0-beta1 starting.
...
...
pimd: 09:26:18.926 VIF #1: Installing tun0 (10.14.11.1 -> 10.14.11.1) rate 0
pimd: 09:26:18.926 VIF #2: Installing tun1 (10.14.12.1 -> 10.14.12.1) rate 0
pimd: 09:26:18.926 ALTNET: PublicIP1/32
pimd: 09:26:18.927 ALTNET: PublicIP2/32
pimd: 09:26:18.927 Local static RP: 10.14.11.1, group 224.0.0.0/4
pimd: 09:26:18.927 spt-threshold packets 0 interval 100
pimd: 09:26:18.927 Local static RP: 169.254.0.1, group 232.0.0.0/8
pimd: 09:26:18.927 VIF #0: Installing pimreg, using tun0 with ifaddr 10.14.11.1
pimd: 09:26:18.927 VIF #1: now in service, interface tun0 UP
pimd: 09:26:18.927 VIF #2: now in service, interface tun1 UP
pimd: 09:26:18.931 VIF #0: now in service, interface pimreg UP
pimd: 09:26:18.931 Binding IPC socket to /var/run/pimd.sock
pimd: 09:26:20.112 Upstream router not available.
When I try to communicate (with a simple ping) through VXLAN, the communication is not established, maybe due to the "Upstream router not available".
It means that the multicast message with (S,G) = (PublicIP1, 239.13.13.3), coming from tun0, is not routed to tun1.
pimctl shows:
Multicast Routing Table
Source Group RP Address Flags
ANY 239.13.13.3 10.14.11.1 WC RP
Number of Groups : 1
Number of Cache MIRRORs : 0
and:
PIM Candidate Rendez-Vous Point Table
Group Address RP Address Prio Holdtime Expires
232.0.0.0/8 169.254.0.1 1 Forever Never
224.0.0.0/4 10.14.11.1 1 Forever Never
mrouted works with a similar configuration file /etc/mrouted.conf:
why does pimd configure 169.254.0.1 as RP candidate for 232.0.0.0/8 ? I haven't specified it in the conf file.
Can pimd act as a "standalone" multicast router, with no neighbors, itself as RP, only with interfaces that send igmp joins/leaves and multicast traffic?
regarding VXLAN: RFCs say that bidir-pim would be better than sparse mode, can pimd act as bidir-pim router?
I tested with both the current release and the latest release v2.3.2, the results are exactly the same.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I've compiled pimd on a Linux and for now I would like to test it as a single multicast router for testing purposes.
Actually for a VXLAN scenario to connect 2 different data centers.
The pimd.conf is:
When I start pimd -n -l debug, I see:
When I try to communicate (with a simple ping) through VXLAN, the communication is not established, maybe due to the "Upstream router not available".
It means that the multicast message with (S,G) = (PublicIP1, 239.13.13.3), coming from tun0, is not routed to tun1.
pimctl shows:
and:
mrouted works with a similar configuration file /etc/mrouted.conf:
I would have some questions here:
I tested with both the current release and the latest release v2.3.2, the results are exactly the same.
Regards, thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions