Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 14 Jun 2020 17:07:53 +0000
From:      bugzilla-noreply@freebsd.org
To:        net@FreeBSD.org
Subject:   [Bug 246629] Multicast stack problem - MRT_ADD_VIF Address already in use
Message-ID:  <bug-246629-7501-ol8FsKW4IQ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-246629-7501@https.bugs.freebsd.org/bugzilla/>
References:  <bug-246629-7501@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D246629

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

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

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

Many people are using pfSense and "some of them" try to get multicast worki=
ng
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 possib=
le.
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.=20=
=20=20
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=E2=80=99s below provide a VIF the on=
es 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.c=
onf
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 fr=
om the beginning of the kernel startup and not the once starting a bit late=
r <<
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 su=
bnet
192.168.2) as vif #1 - rate 0
Jun 10 11:54:11 pfSense pimd[52647]: Installing lagg0.26 (192.168.2.1 on su=
bnet
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

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-246629-7501-ol8FsKW4IQ>