Gerbera LXD Container routes:
ip r
default via 169.254.0.1 dev eth0 proto static onlink
IP forwarding enabled.
cat /proc/sys/net/ipv4/ip_forward
1
Multicast forwarding can’t be enabled as noted at the link below.
cat /proc/sys/net/ipv4/conf/all/mc_forwarding
0
I have installed, enabled and started pimd on the host.
Reverse path forwarding isn’t 0, but when I did set it manually to 0 it didn’t seem to help.
sysctl -ar '\.rp_filter'
net.ipv4.conf.all.rp_filter = 2
net.ipv4.conf.br0.rp_filter = 2
net.ipv4.conf.default.rp_filter = 2
net.ipv4.conf.eno1.rp_filter = 2
net.ipv4.conf.lo.rp_filter = 0
net.ipv4.conf.lxdbr0.rp_filter = 2
net.ipv4.conf.tunl0.rp_filter = 2
net.ipv4.conf.veth016d3221.rp_filter = 2
net.ipv4.conf.veth561902ae.rp_filter = 2
net.ipv4.conf.veth92844081.rp_filter = 1
net.ipv4.conf.wlp2s0b1.rp_filter = 2
net.ipv4.conf.wlxc46e1f25e927.rp_filter = 2
Nftable rules:
nft add rule ip filter INPUT ip daddr 224.0.0.0/4 ct state new counter accept
nft add rule ip filter FORWARD ip daddr 224.0.0.0/4 counter accept
nft add rule ip filter FORWARD ip saddr 224.0.0.0/4 counter accept
nft add rule ip filter OUTPUT ip daddr 224.0.0.0/4 ct state new counter accept
I test changes by pinging multicast from within the Gerbera container.
ping 224.0.0.1 -t 100
I then look for a response on the outbound host interface using tcpdump.
tcpdump -vv -l -i br0 net 224.0.0.0/4
The multicast traffic is visible on the host on the container’s veth interface but not on the outbound br0 interface. I’d like to get multicast working using the routed network profile because then I could transition to a wifi server connection only.