-
-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PIMD only worknig in one direction - wrong input vif for remote source #243
Comments
I have exactly the same problem! Also using KNX/IP Router here. I even use the same multicast group: 224.0.23.12 and port: 3671. The multicast traffic from site A is seen at site B. But, when setting the RP -and- the BSR to Site A, it works. Havinf only the RP or the BSR at site B, it doesn't work anymore and we see the same problem (multicast traffic from site B is seen at the eth0 interface, but not at the tap0 interface).
|
Thanks a lot for your response @roelbroersma! In pfSense I can only configure the "interfaces on which to enable Bootstrap Router (BSR) candidate election participation". I cannot test at the moment because the tunnel to router B is down for a few days.
|
@Snafu I think we should ask @troglobit about this one. It seems to look like a bug. Probably has something todo with wrong in/out interface. |
Hi @troglobit Can you shine your light on this? Do you have any idea what could be wrong here? If there is something in the code.. but you are unsure.. let me know. I can do a Fork.. commit, PR. Or we can look together at the source.. ~Roel |
Hi, |
I'm sorry, this is unfortunately not a prioritised project for me anymore. The company I worked for decided to go in another direction and I've since moved on. FYI, I have three other multicast router projects that work, are well tested, and have active coordinators. There are also other PIM-SM projects out there that you can try. Now, this is not the first report of this problem. So a constructive way forward is if someone could help debug their issue to help narrow things down. I've put a lot of effort into the still-to-be-released 3.0 version, so I can help steward things along, but I really need help debugging and fixing this particular case. |
Hi troglobit,
I can help you work on this issue.
Let’s do the following; I build a test environment and set it up so we can see the problem. From then on, we can work together on the issue; I can start tcpdump etc., running and also switch the environment to a working situation and do tcpdump again. We can do Teams or another sharing tool.
I can make time for it to help troubleshoot it, however since you have most knowledge of this and the 3.0 you want to release; if I spend time in it, can you do it also?
Kind regards,
Roel Broersma
|
@roelbroersma thank you, but like I said, this is not a prioritised project for me. That means I don't have the time (or energy) to troubleshoot and fix issues on it during my spare time. I am however open to reviewing pull-requests to fixes concerning this problem. To everyone else in this thread, or lurking around pimd, the project has been without activity for quite some time, and this is mainly because of funding and lack of user involvement/PRs. I would love to see pimd succeed since it still has a lot to offer compared to offering from, e.g., Frr. This does, however, require a lot more code contributions from other people since I only have time for reviews and release work. |
I understand. I personally switched to Udp broadcast relay for the project for which I needed it, but sooner or later I still need a pimd (sort of) daemon. |
Hello troglobit,
I'm using pimd in order to forward the multicast data from two LANs of different routers (pfSense, FreeBSD14.0) to each other, connected via WireGuard tunnel. On router A it is the LAN 192.168.11.0/24 and on router B it is the LAN 192.168.22.0/24, see image below. In LAN 192.168.11.0/24 there are two KNX/IP routers (192.168.11.30 and 192.168.11.35) and in LAN 192.168.22.0/24 there is one KNX/IP router (192.168.22.20) that all broadcast packets to multicast group 224.0.23.12. Within the LAN 192.168.11.0/24 everything works great, now I want to get the KNX/IP router from the other LAN to join the party.
Issue
I currently have it half way working, meaning I can see all multicast data in the LAN of router B. In the LAN of router A, howerver, I can only see the local multicast data. From what I can see it seems as if on router A the wrong Vif is used as input for the remote source. Instead of Vif 4 it shows the Vif 17 register_vif0 as input.
On router B it correctly shows Vif 2 (tun_wg0) as input for the remote source.
Is my assumption correct or is the pimd -r output OK in your mind and I have some other issue? (Hints appreciated)
I've got static routes configured on both routers, multicast is enabled on all involved interfaces and firewall rules are configured correctly as well. I can see PIM messages from 192.168.22.1 to 192.168.11.1 on the tunnel network.
Edit: I just swapped the DR role and made 192.168.22.1 the RP on both routers and now I have the same issue just the other way round. The router which is acting as RP somehow can't handle the broadcasts properly.
Router A
Router B
The text was updated successfully, but these errors were encountered: