can't add mroute via smcroutectl add #194
-
|
Hi there! I need any help. config R1: config R2: smcroute enable, i see in ps: But if i use command smcroutectl show,I can't see anything. When i start app for dlna by my phone, this scheme doesn't work( I see ssdp a packet on interface br0 R1, from my phone, but i can't see forwards between br0 to nwg0 ssdp of the packet If I try use command smcroutectl add, I see this error: Where am I wrong? |
Beta Was this translation helpful? Give feedback.
Replies: 26 comments 2 replies
-
|
Also i use rules s in iptables on both sides |
Beta Was this translation helpful? Give feedback.
-
|
Super difficult to help debug your system remotely. Here are a few things that would be good to start with:
|
Beta Was this translation helpful? Give feedback.
-
|
Hi @troglobit. Thank you for your quick response. I can give your access for my routers. 3)I can see only br0 in file: |
Beta Was this translation helpful? Give feedback.
-
|
OK, so the problem seems to be that smcrouted failed to enumerate the nwg0 interface, otherwise it would be listed in ip_mr_vif. Not sure why, but it should be shown in the syslog. You can run the daemon with I've never tested with a wireguard tunnel interface before, or any p-t-p interface for that matter. It is likely you'll have to workaround the issue by using a GRE tunnel over nwg0. |
Beta Was this translation helpful? Give feedback.
-
|
How can I do it? |
Beta Was this translation helpful? Give feedback.
-
|
I used this manual for help in setting https://an0n-r0.medium.com/making-dlna-through-site-to-site-vpn-work-f393629f4ce0 |
Beta Was this translation helpful? Give feedback.
-
|
Here's the HTML version of the manual page I distributed with SMCRoute, hopefully that helps. Like I said, I've never tested running over a wireguard tunnel. Glad to see someone got it working. The real problem here is that smcrouted fails to enumerate the interface as a multicast VIF in the kernel. Only way to debug that is to get some more logs from the daemon and then drill down from there. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you so much!I will try to get debug log |
Beta Was this translation helpful? Give feedback.
-
|
@troglobit I get debug log, but i don't see, the deamon is started / # cat /opt/var/log/syslog |
Beta Was this translation helpful? Give feedback.
-
|
Maybe it doesn't work because there are a lot of interfaces in the system? |
Beta Was this translation helpful? Give feedback.
-
|
Hmm, yeah that's a possibility. Linux only supports 32 VIFs (it's being worked on). So try starting with |
Beta Was this translation helpful? Give feedback.
-
|
Could you please tell me what is foo? I can't find description in internet:) |
Beta Was this translation helpful? Give feedback.
-
|
Other common "any" names are; |
Beta Was this translation helpful? Give feedback.
-
|
@troglobit Thanks. I have in my configuration interfaces nwg0 and br0 on both sides. I changed my config, now it looks like that include /etc/smcroute.d/*.conf I don't like this line: Pv4 multicast routing API already in use: Address already in use |
Beta Was this translation helpful? Give feedback.
-
|
It means you have another multicast routing daemon running already. Possibly a previous instance of smcrouted. Only one can run at the same time by default due to a kernel limitation. |
Beta Was this translation helpful? Give feedback.
-
|
I think maybe this problem that any deamon use address 239.255.255.250? |
Beta Was this translation helpful? Give feedback.
-
|
I check it |
Beta Was this translation helpful? Give feedback.
-
|
I checked all system, deleted upnp,dlna and igmp proxy components, and that's what i see. I think that the problem with starting the daemon was solved. But could you please tell me, this line bad or may i ignore it?(Feb 10 11:01:24 Keenetic-1605 daemon.err smcroute[1122]: Failed enabling PIM IGMPMSG_WRONGVIF, ignoring: Protocol not available) |
Beta Was this translation helpful? Give feedback.
-
|
I understood one thing, smcroute didn't start if in my system use igmp-proxy module |
Beta Was this translation helpful? Give feedback.
-
|
The igmp-proxy project is actually a multicast router |
Beta Was this translation helpful? Give feedback.
-
|
Smcroute has the support for detecting the source ip of the sender using that PIM mechanism. Your kernel does not seem to support it. So you need to set the sender ip in your routes. |
Beta Was this translation helpful? Give feedback.
-
|
Must i add in my config this settings?: |
Beta Was this translation helpful? Give feedback.
-
|
Now i see ssdp on wg interfaces but not on br0 interfaces in tcpdump 172.16.137.2 dlna server |
Beta Was this translation helpful? Give feedback.
-
|
wooooo!!!! It's WORKED =) |
Beta Was this translation helpful? Give feedback.
-
|
can you share how you make it work,I have a similar problem .thanks |
Beta Was this translation helpful? Give feedback.
-
|
Even I am looking forward on how you did it. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Great, I'll convert this from an issue to discussion then. |
Beta Was this translation helpful? Give feedback.
-
|
can you share how you make it work,I have a similar problem ,thanks. @UrusovVladimir |
Beta Was this translation helpful? Give feedback.
wooooo!!!! It's WORKED =)
Thank you so much, for your help!
I will write how I setup it a little bit later!