CONFIG_MROUTE: Allow multicast routing
Description
Problem/Justification
None
Impact
None
Activity
Show:

Michael Kirgus June 22, 2022 at 4:45 PM
Thanks, with that information i think i could manage it to work...i was just not sure if that was compiled with it...because multicast routing is not very common 😉.
But because of the read-only-filesystem and the changes that are required at the base system i think it would be better to perform the multicast routing on another place...
Solved!

Ameer Hamza June 22, 2022 at 1:28 AMEdited
Hello ,
TrueNAS Scale kernel is already compiled with multicast forwarding config option. In linux, "sysctl net.ipv4.conf.all.mc_forwarding" reads from a proc file "/proc/sys/net/ipv4/conf/all/mc_forwarding", which is read only, e.g.,
However, Multi cast routing daemons like pimd can help update this value.
Behaves as Intended
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee

Reporter

Impact
Low
Time remaining
0m
Components
Fix versions
Affects versions
Priority
Katalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Katalon Platform
Linked Test Cases, Katalon Defect Results, Katalon Studio Test Results
Created January 5, 2022 at 12:08 AM
Updated July 6, 2022 at 8:58 PM
Resolved June 22, 2022 at 4:48 PM
Under TrueNAS CORE it was possible to set the sysctl
net.link.ether.inet.allow_multicast = 1
to enable multicast routing to the host system and the VMs.
Under TrueNAS SCALE the support for multicast routing seems not to be compiled in the kernel:
root@System:~# sysctl -w net.conf.all.mc_forwarding=1
sysctl: cannot stat /proc/sys/net/conf/all/mc_forwarding: No such file or directory
I dont know its a bug or its wanted, but under TrueNAS Core it was possible at all.