Open GrumpyOldTroll opened 3 years ago
A quick glance suggests that it's intentional in the kernel to deny this if using the same table:
Is there maybe a way to use different mrt tables for default IPv4 and default IPv6?
Yup, they share the same multicast routing socket by default. I have it on my backlog of things to port the multiple-table support from pimd to pim6sd, that would indeed fix this limitation.
Please paste kernel version
@ne-vlezay80 kernel version doesn't help when pim6sd doesn't support multicast policy routing yet.
What may help is to use the pimd functionality and let pim6sd use the "main" table, as long as there is no overlap between interfaces. Should have mentioned that possible workaround previously.
What may help is to use the pimd functionality and let pim6sd use the "main" table, as long as there is no overlap between interfaces. Should have mentioned that possible workaround previously.
And How
@ne-vlezay80 Well I haven't tried it, that's why I said "possible workaround". It's entirely likely to not work at all, but you can play around with it yourself, the pimd docs detail the table option.
It looks not possible to run this concurrently with pimd to support a dual-stack multicast routing?
If I try I get an error message and a stop: