Bug #10750
closed
(vlan)interfaces not properly handled in relation multicast (e.g. triggered by pimd)
0%
Description
Hello,
As known I try to get pimd running, but up to now that does not work. Interfaces are not treated correctly and switching interfaces off and on does frequently lead to crashes. Those crashes are sometimes recoverable and sometimes not. I assume that the noted issues are not related to pimd itself but that there are one or more multicast related issues causing this. For that reason I suppose that also ffr, Avahi, IMGP-proxy etc. are in some way affected.
IMHO this issue is provoked by PIMD but not related to PIMD. I think it is somewhere on FreeBSD or pfSense kernel level.
I notice:
1) when starting up something goes wrong after Installing lagg0.13, there are many more interfaces__
Jul 4 19:28:20 pfSense pimd5494: Interface register_vif0 comes up; vif #3 now in service
Jul 4 19:28:20 pfSense pimd5494: Interface lagg0.13 comes up; vif #2 now in service
Jul 4 19:28:20 pfSense pimd5494: Interface lagg0.26 is DISABLED; vif #1 out of service
Jul 4 19:28:20 pfSense pimd5494: Interface lagg0.10 is DISABLED; vif #0 out of service
Jul 4 19:28:20 pfSense pimd5494: Local static RP: 169.254.0.1, group 232.0.0.0/8
Jul 4 19:28:20 pfSense pimd5494: Local static RP: 192.168.14.1, group 224.0.0.0/4
Jul 4 19:28:20 pfSense pimd5494: Local Cand-RP address 192.168.13.1, priority 0, interval 60 sec
Jul 4 19:28:20 pfSense pimd5494: /var/etc/pimd/pimd.conf:12 - Invalid Cand-RP address 'ix0.14', defaulting to 192.168.13.1
Jul 4 19:28:20 pfSense pimd5494: /var/etc/pimd/pimd.conf:10 - Invalid phyint address 'ix0.14'
Jul 4 19:28:20 pfSense pimd5494: /var/etc/pimd/pimd.conf:9 - Invalid phyint address 'ix1.116'
Jul 4 19:28:20 pfSense pimd5494: /var/etc/pimd/pimd.conf:8 - Invalid phyint address 'lagg0.16'
Jul 4 19:28:20 pfSense pimd5494: Recommended querier timeout = Robustness x query-interval + response-time / 2 = 3 x 6 + 10 / 2 = 23
Jul 4 19:28:20 pfSense pimd5494: Getting vifs from /var/etc/pimd/pimd.conf
Jul 4 19:28:20 pfSense pimd5494: Disabling all vifs from kernel
Jul 4 19:28:20 pfSense pimd5494: Installing lagg0.13 (192.168.13.1 on subnet 192.168.13) as vif #2 - rate 0
Jul 4 19:28:20 pfSense pimd5494: Installing lagg0.26 (192.168.2.1 on subnet 192.168.2) as vif #1 - rate 0
Jul 4 19:28:20 pfSense pimd5494: Installing lagg0.10 (192.168.10.1 on subnet 192.168.10) as vif #0 - rate 0
Jul 4 19:28:20 pfSense pimd5494: Getting vifs from kernel
Jul 4 19:28:20 pfSense pimd5494: pimd version 2.3.2 starting ...
Jul 4 19:28:19 pfSense root1123: Bootup complete
2) I am using the pimd file below, however pimd only sees the interfaces processed before the issue described in 1) does occur__
- DO NOT EDIT THIS FILE! ###################### ###################################################################
- This file was created by an automatic configuration generator. #
- The contents of this file will be overwritten without warning! #
###################################################################
igmp-query-interval 6
igmp-querier-timeout 23
phyint lagg0.16 enable ttl-threshold 2
phyint ix1.116 enable ttl-threshold 2
phyint lagg0.26 enable ttl-threshold 2
phyint ix0.14 enable ttl-threshold 2
phyint lagg0.13 ttl-threshold 2
rp-candidate ix0.14
rp-address 192.168.14.1
Virtual Interface Table ======================================================
Vif Local Address Subnet Thresh Flags Neighbors
--- --------------- ------------------ ------ --------- -----------------
0 192.168.10.1 192.168.10 1 DISABLED
1 192.168.2.1 192.168.2 1 DISABLED
2 192.168.13.1 192.168.13 2 DR NO-NBR
3 192.168.13.1 register_vif0 1
Vif SSM Group SourcesMulticast Routing Table ======================================================
--------------------------------- (*,*,G) ------------------------------------
Number of Groups: 0
Number of Cache MIRRORs: 0
------------------------------------------------------------------------------
3) I noticed that switching on and off interfaces does almost ever lead to a crash__
I am not sure if this is PIMD related, my impression is "up to a certain level"
4) PIMD does not behave correct independent from the fact that the package was yes/or present at boot time__
5) I can get PIMD running properly using "tricks" (sometimes)__
For that the OS have to be forced to reprocess interfaces, which can be provoked by switching on and of interfaces.
However that does not always work due to the issues described under 3)
Procedure is like this
pimd off
vlan13 off
vlan26 off
pimd on
pimd off
vlan13 on
vlan26 on
pimd on
If you have some luck pimd is working as it should now
For a sucessfull test see copy of one of the mails I exchanged with pimd-maintainer on 23/6
20200623 ExpirimentWithDisablingAndEnablingInterfaces.txt
More info on the forum and in the attached file "Drama when testing with yesterdays snapshot"
I consider this bug as high priority, because I think it is a kernel problem probably causing issues in multiple situations.
Louis
Files
Updated by Jim Pingle almost 5 years ago
- Category set to Interfaces
- Status changed from New to Rejected
- Priority changed from High to Normal
Please keep these kinds of things on the forum until a more definite issue can be identified here. Far too much speculation and not enough specific information.
Updated by Louis B almost 5 years ago
Jim,
This is not the first time you make me angry! You consequently refuse to accept issues which are clearly there!!!
Of cause I did not analyze the issue with a debugger or an in circuit analyzer, however you can clearly see in the logs that there is a bug and it fairly easy to reproduce!
So please stop this behavior!!
Louis
Updated by Jim Pingle almost 5 years ago
The correct place for this is the forum, not a bug report. Keep it on the forum. Opening issues without concrete information, with lots of irrelevant information and speculation, takes time away from developers and other staff.
There still isn't any evidence here that this affects anyone else but you and your environment. It can't be reproduced here yet.