[Bug 246629] Multicast stack problem - MRT_ADD_VIF Address already in use

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246629

Louis <l.m.v.breda at xs4all.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |l.m.v.breda at xs4all.nl

--- Comment #4 from Louis <l.m.v.breda at xs4all.nl> ---
Hello,

Many people are using pfSense and "some of them" try to get multicast working
using IMCP-proxy or PIMD. That simply does not work.

I put a lot of effort getting multicast to work and it is simply not possible.
Reading this bug report, I am 99% sure that this is one of the underlaying
issues. That is also the verdict of jimp (pfSense Lead Designer)

So please fix it with high priority!

During PIMD startup I notice:
1) after processing the first few (vlan)interfaces something goes wrong.   
Jun 10 11:53:50 pfSense kernel: vlan4: changing name to 'em0.4'
Jun 10 11:53:49 pfSense kernel: vlan3: changing name to 'em0.6'
Jun 10 11:53:47 pfSense sshd[11688]: Server listening on 0.0.0.0 port 22.
Jun 10 11:53:47 pfSense sshd[11688]: Server listening on :: port 22.
>>> after starting PIMD the three vlan’s below provide a VIF the ones above DO NOT, so some thing wrong here ! <<
Jun 10 11:53:47 pfSense kernel: vlan2: changing name to 'lagg0.13'
Jun 10 11:53:47 pfSense kernel: vlan1: changing name to 'lagg0.26'
Jun 10 11:53:47 pfSense kernel: vlan0: changing name to 'lagg0.10'

2) Related things are going wrong with PIMD
Jun 10 11:54:11 pfSense pimd[52647]: Getting vifs from /var/etc/pimd/pimd.conf
Jun 10 11:54:11 pfSense pimd[52647]: Disabling all vifs from kernel
Jun 10 11:54:11 pfSense pimd[52368]: Disabling all vifs from kernel
>> see here that only from three vlan's there are vifs, exactly the ones from the beginning of the kernel startup and not the once starting a bit later <<
Jun 10 11:54:11 pfSense pimd[52647]: Installing lagg0.13 (192.168.13.1 on
subnet 192.168.13) as vif #2 - rate 0
Jun 10 11:54:11 pfSense pimd[52368]: Installing lagg0.13 (192.168.13.1 on
subnet 192.168.13) as vif #2 - rate 0
Jun 10 11:54:11 pfSense pimd[52368]: Installing lagg0.26 (192.168.2.1 on subnet
192.168.2) as vif #1 - rate 0
Jun 10 11:54:11 pfSense pimd[52647]: Installing lagg0.26 (192.168.2.1 on subnet
192.168.2) as vif #1 - rate 0
Jun 10 11:54:11 pfSense pimd[52368]: Installing lagg0.10 (192.168.10.1 on
subnet 192.168.10) as vif #0 - rate 0
Jun 10 11:54:11 pfSense pimd[52647]: Installing lagg0.10 (192.168.10.1 on
subnet 192.168.10) as vif #0 - rate 0

3) then there is a problem recognising interfaces
Jun 10 11:54:11 pfSense pimd[52647]: /var/etc/pimd/pimd.conf:12 - Invalid
phyint address 'ix1.116'
Jun 10 11:54:11 pfSense pimd[52647]: /var/etc/pimd/pimd.conf:11 - Invalid
phyint address 'lagg0.16'
Jun 10 11:54:11 pfSense pimd[52647]: /var/etc/pimd/pimd.conf:10 - Invalid
phyint address 'ix0.14'

4) and the result is
Jun 10 11:54:11 pfSense pimd[52368]: Cannot forward: no enabled vifs


As allready indicated, I expect that this is all related to this bug.

Hope to see it fixed soon. Importance is defenitively not correct!!

Sincerely


Louis

-- 
You are receiving this mail because:
You are the assignee for the bug.