Closed greenpau closed 9 years ago
My bet would have been on the MTU, but what's listed above is plain control traffic so it should work. The packet counters look very much at zero though ... have you tried tcpdump:ing tun1
, or forcing out any multicast with regular old ping?
ping -I tun1 225.1.2.3
With a tcpdump in another terminal
tcpdump -i tun1
@troglobit , I see it:
sending:
ping -I tun1 225.1.2.3
capturing:
13:39:34.693214 IP ny-rt01 > 225.1.2.3: ICMP echo request, id 11083, seq 1, length 64
13:39:35.692925 IP ny-rt01 > 225.1.2.3: ICMP echo request, id 11083, seq 2, length 64
13:39:36.694013 IP ny-rt01 > 225.1.2.3: ICMP echo request, id 11083, seq 3, length 64
13:39:37.693925 IP ny-rt01 > 225.1.2.3: ICMP echo request, id 11083, seq 4, length 644
MTU size is 1460:
26: tun1@NONE: <POINTOPOINT,MULTICAST,NOARP,ALLMULTI,UP,LOWER_UP> mtu 1460 qdisc noqueue state UNKNOWN mode DEFAULT
@troglobit , the issue is resolved. It was TTL value on the tun1
.
Added the following to interface configuration:
MTU=1460
TTL=10
Now, I can see the hellos:
18:18:55.685932 IP 10.254.0.12 > pim-routers.mcast.net: PIMv2, Hello, length 10
18:19:25.626935 IP ip-192-168-16-66 > pim-routers.mcast.net: PIMv2, Hello, length 10
18:19:25.626969 IP ip-192-168-16-66 > pim-routers.mcast.net: PIMv2, Hello, length 10
18:19:25.692172 IP 10.254.0.12 > pim-routers.mcast.net: PIMv2, Hello, length 10
What is the command to get the list of PIM neighbors?
Aha, didn't know about TTL being limited like that on tun interfaces.
There isn't any specific command for that (yet), but you can see neighbors with pimd -r
or sending SIGUSR1
to the running pimd
. The pimd -r
sends SIGUSR1 for you and then dumps the contents of /run/pimd/pimd.dump
on stdout
. Hope this helps!
@troglobit , it does :+1: It makes me want to be a better coder :smile_cat: so I can fix it :smoking:
I have a tunnel interface
I can see PIMv2 Hello packet being send out of
tun1
interface.The interface is registered to forward multicast traffic.
However, the packets never make it to the physical interface and to the other end of that tunnel. Unicast traffic, i.e. BGP and ICMP, works without any issue.
Any idea why that is happening?