23 May
2017
23 May
'17
1:59 p.m.
I think ampr-ripd shouldn't care. It is the regular routing
daemons/multicast clients that drop the data which does not fit, not the
socket itself.
I also have a /32 interface which works as expected with multicast packets.
On 23.05.2017 20:48, Rob Janssen wrote:
(Please trim inclusions from previous messages)
_______________________________________________
That's actually a limitation on how multicast
works. In usual
circumstances, a router does not listen to multicasts not originating
from the subnet its interface is connected to.
Could that be the reason why ampr-ripd multicast mode does not work
for me?
I always put the local address /32 on the tunnel interface. Maybe it
would
work when that is changed to /8 ?
Rob
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net