: Kristof Provost
AuthorDate: 2025-01-21 09:49:55 +
Commit: Kristof Provost
CommitDate: 2025-02-11 16:52:42 +
carp: don't unintentionally revert to multicast mode
PR: 284140
MFC after: 2 weeks
Sponsored by: Rubicon Communications, LLC (&qu
: Kristof Provost
AuthorDate: 2025-01-21 09:49:55 +
Commit: Kristof Provost
CommitDate: 2025-01-24 10:20:30 +
carp: don't unintentionally revert to multicast mode
PR: 284140
MFC after: 2 weeks
Sponsored by: Rubicon Communications, LLC (&qu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=284140
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283820
Mark Linimon changed:
What|Removed |Added
CC||pku...@freebsd.org
Assign
Hi-
I just moved my router VM from a bridge + virtio setup to using a VF (virtual
function) on my Chelsio T520-LL-CR to improve performance. It’s working
beautifully for the most part, but I have noticed two things that aren’t, both
related to multicast.
First, when using dhcpcd to assign
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247652
Alexander Vereeken changed:
What|Removed |Added
Keywords|patch |
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606
Mark Linimon changed:
What|Removed |Added
Resolution|--- |Overcome By Events
Stat
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281125
Kurt Jaeger changed:
What|Removed |Added
Assignee|n...@freebsd.org |free...@intel.com
--
You are recei
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606
--- Comment #22 from Ingeborg Hellemo ---
I don't have this kind of HW anymore for testing.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213606
Mark Linimon changed:
What|Removed |Added
CC||bugmeis...@freebsd.org
As
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280086
Franco Fichtner changed:
What|Removed |Added
CC||fra...@opnsense.org
--- Comment
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280086
gu...@gvr.org changed:
What|Removed |Added
Resolution|--- |FIXED
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280086
--- Comment #5 from gu...@gvr.org ---
This bug was solved in 14-stable with the following commits to
https://cgit.freebsd.org/src/commit/sys/netinet/in_mcast.c?h=stable/14&id=88e1bc06692ae4552462945c53b5047e8dad5929
and
https://cgit.freebs
with a
comment.
Here's some of my truss output with concurrent runs on 13.4 and 14.1
the 14.1 machine... (command "hive foo" i.e. one argument to cause ipv6
case...)
NOTE this receives the multicast messages...
socket(PF_INET6,SOCK_DGRAM,0)= 3 (0x3)
bind(3,{ A
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281391
Mark Johnston changed:
What|Removed |Added
CC||ma...@freebsd.org
Stat
--- Comment #1 from anto...@hesiod.org ---
I have a test program which shows 13.3 multicast reaching 14.1 but the 14.1
packets do not reach 13.3
The program tests ipv4 or ipv6.
It was working fine when written for 13.1 years ago.
So, anyhow, I think I've hit this problem.
--
You are receiving this
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281391
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=281125
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
Hi,
This references https://reviews.freebsd.org/D46190 as it is
currently broken on FreeBSD 14.0/14.1 but fixed on main.
I’m sending this because so far I got no reaction from anyone
Involved. It would be nice to get this on stable/14 at least.
Cheers,
Franco
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280086
--- Comment #4 from gu...@gvr.org ---
I tested the test program on my system (13.3-RELEASE-p3) (tcpdump in backgroud
while the test programs runs). As you can se there is no IGMP traffic after
dropping mebership:
Add membership
11:31:24.963
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280086
--- Comment #3 from Gleb Smirnoff ---
Created attachment 251852
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=251852&action=edit
mcasttest.c
test program
--
You are receiving this mail because:
You are the assignee for the bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280086
--- Comment #2 from Gleb Smirnoff ---
On Tue Jul 2 12:57:26 2024 UTC, gu...@gvr.org wrote:
> Bug 242677 was fixed in FBSD 12 but since some time it is back in FBSD 13. The
> test script fro hps can be used to prove this. As I am unsure ho
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280086
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242677
Mark Linimon changed:
What|Removed |Added
See Also||https://bugs.freebsd.org/bu
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247652
Mark Linimon changed:
What|Removed |Added
Attachment #216059|0 |1
is patch|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=275265
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243554
Graham Perrin changed:
What|Removed |Added
Severity|Affects Only Me |Affects Some People
St
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243554
--- Comment #12 from Kristof Provost ---
(In reply to Patrick M. Hausen from comment #11)
I'm inclined to leave this open. While it's a well documented configuration
issue there's also a case to be made that this should either just work, or
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243554
--- Comment #11 from Patrick M. Hausen ---
(In reply to Kristof Provost from comment #10)
Another closing candidate?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=231859
Mark Linimon changed:
What|Removed |Added
Status|In Progress |Closed
Resolution|---
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
Kubilay Kocak changed:
What|Removed |Added
Keywords||crash
--
You are receiving this m
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265540
Bug ID: 265540
Summary: EADDRNOTAVAIL when leaving IPv6 multicast group and
ipv6_mreq.ipv6mr_interface=0
Product: Base System
Version: CURRENT
Hardware: Any
Kristof wrote:
> On 18 Mar 2022, at 19:02, Mike Karels wrote:
> > It looks like the IPv4 multicast code has not been fully converted to
> > use epochs. I installed this week's snapshot of -current, configured
> > and started mrouted, and started rwhod -m.
On 18 Mar 2022, at 19:02, Mike Karels wrote:
> It looks like the IPv4 multicast code has not been fully converted to
> use epochs. I installed this week's snapshot of -current, configured
> and started mrouted, and started rwhod -m. The system crashed shortly
> thereafter wit
It looks like the IPv4 multicast code has not been fully converted to
use epochs. I installed this week's snapshot of -current, configured
and started mrouted, and started rwhod -m. The system crashed shortly
thereafter with this:
panic: Assertion in_epoch(net_epoch_preempt) failed at
/us
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243554
--- Comment #10 from Kristof Provost ---
(In reply to Patrick M. Hausen from comment #9)
I confirm what Patrick says here. Set your IP address on the bridge, not on
member interfaces.
There's also this bug, and the one comment specifically
reeNAS/TrueNAS has been doing it wrong for years. The problem is with
dynamically generated bridge interfaces of course.
Most TrueNAS users won't notice, because there is not much in IPv4 that relies
on multicast. So it works, most of the time. With IPv6 things get interesting
...
If you plan
page for bridging:
> https://docs.freebsd.org/en/books/handbook/advanced-networking/#network-bridging
>> If the bridge host needs an IP address, set it on the bridge interface, not
>> on the member interfaces.
> I don't know if this already fixes your problem or if there is sti
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243554
sl...@zone42.org changed:
What|Removed |Added
CC||sl...@zone42.org
--- Comment #6
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=140647
Kevin Bowling changed:
What|Removed |Added
CC||kbowl...@freebsd.org
Ass
On Fri, 7 Aug 2020 15:25:25 +0200
Abelenda Diego wrote:
> Hello,
>
> I have discovered that I had a multicast issue for years I did not
> know about. I use a FreeBSD (opnsense) setup as router for my home
> network and have igmpproxy for IPTV. Somehow everything seems to
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=241121
Neel Chauhan changed:
What|Removed |Added
Resolution|--- |Not Accepted
Status|New
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251047
Kubilay Kocak changed:
What|Removed |Added
Status|New |Open
Keywords|needs-patc
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251047
--- Comment #4 from Louis ---
Thanks,
It does not win the beauty price, but it could work.
Stupid, that there is not proper call for that,
Louis
--
You are receiving this mail because:
You are the assignee for the bug.
_
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251047
--- Comment #3 from Andrey V. Elsukov ---
(In reply to Louis from comment #2)
It seems there is no easy way, but the kernel has sysctl variable that depends
from MAXVIFS:
# sysctl -o net.inet.ip.viftable
net.inet.ip.viftable: Format:S,vif
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251047
--- Comment #2 from Louis ---
Thanks for your reaction, which made me realize that I had to do more than one
change, to get a changed maxvifs working.
I think I managed that. Not in the proper way yet, and surely not the way it
IMHO should
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251047
Andrey V. Elsukov changed:
What|Removed |Added
CC||a...@freebsd.org
--- Comment #
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=251047
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
;> Hello,
> >>>
> >>> I have discovered that I had a multicast issue for years I did not
> >>> know
> >>> about. I use a FreeBSD (opnsense) setup as router for my home
> >>> network and
> >>> have igmpproxy for IPTV. Some
On 8 Aug 2020, at 12:31, Abelenda Diego wrote:
On Sat, 8 Aug 2020 12:54:37 +0200
Hans Petter Selasky wrote:
On 2020-08-07 15:25, Abelenda Diego wrote:
Hello,
I have discovered that I had a multicast issue for years I did not
know
about. I use a FreeBSD (opnsense) setup as router for my
On Sat, 8 Aug 2020 12:54:37 +0200
Hans Petter Selasky wrote:
> On 2020-08-07 15:25, Abelenda Diego wrote:
> > Hello,
> >
> > I have discovered that I had a multicast issue for years I did not know
> > about. I use a FreeBSD (opnsense) setup as router for my home net
On 2020-08-07 15:25, Abelenda Diego wrote:
Hello,
I have discovered that I had a multicast issue for years I did not know about.
I use a FreeBSD (opnsense) setup as router for my home network and have
igmpproxy for IPTV. Somehow everything seems to work, until I realized that my
ISP was
Hello,
I have discovered that I had a multicast issue for years I did not know about.
I use a FreeBSD (opnsense) setup as router for my home network and have
igmpproxy for IPTV. Somehow everything seems to work, until I realized that my
ISP was making a DoS with multicast. It is pretty much
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248243
Kubilay Kocak changed:
What|Removed |Added
Status|New |Closed
Keywords|IntelNet
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248243
--- Comment #3 from Louis ---
In the past two months the situation is very much(!) improved. I did retest I
can not reproduce the crash any longer.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248243
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
--
You are receiv
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248243
Mark Linimon changed:
What|Removed |Added
Flags|maintainer-feedback+|
--- Comment #2 from Mark Linimon
>
> Can you try 12.0 using a 12-stable kernel and see if there are any
> differences?
>
I've updated my system to 12-stable and the behavior is exactly the same.
Just in case, this is what uname -a returns (I'm not that familiar with
FreeBSD versioning and building):
FreeBSD freebsd 12.1-STABLE F
On 2020-07-07 13:55, Fabrice Colliot wrote:
Sorry, I forgot to mention it. I've tried on FreeBSD 11.3 and FreeBSD 12.0.
Can you try 12.0 using a 12-stable kernel and see if there are any
differences?
--HPS
___
freebsd-net@freebsd.org mailing list
Sorry, I forgot to mention it. I've tried on FreeBSD 11.3 and FreeBSD 12.0.
/Fabrice
On Tue, Jul 7, 2020 at 1:48 PM Hans Petter Selasky wrote:
> On 2020-07-07 12:01, Fabrice Colliot wrote:
> > Hi,
> >
> > I'm using smcroute to join and leave multicast groups
On 2020-07-07 12:01, Fabrice Colliot wrote:
Hi,
I'm using smcroute to join and leave multicast groups and I don't
understand the behavior of FreeBSD when the group is left.
Here is what I do:
smcroute join em1 10.3.4.5 224.0.55.55
ifmcstat -i em1
em1:
inet 10.10.0.1
Hi,
I'm using smcroute to join and leave multicast groups and I don't
understand the behavior of FreeBSD when the group is left.
Here is what I do:
smcroute join em1 10.3.4.5 224.0.55.55
ifmcstat -i em1
em1:
inet 10.10.0.1
igmpv3 rv 2 qi 125 qri 10 uri 3
Keywords||patch
Summary|Unwanted leaved on AllHost |Unwanted leave on AllHost
|multicast group |multicast group when
||calling SIOCAIFADDR ioctl
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246629
Bjoern A. Zeeb changed:
What|Removed |Added
Assignee|n...@freebsd.org |b...@freebsd.org
--- Comment #6
from Joel S ---
Created this account simply to mention this is also causing me some issues as
well. Been trying to get my multicast-traffic to work correctly on pfsense
2.5.0 snapshot for the last month without luck.
Their related issue can be found here: https://redmine.pfsense.org/issues/7727
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246629
Louis changed:
What|Removed |Added
Flags||maintainer-feedback+
--
You are receiving
Louis ---
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
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246629
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
CC
Hello,
I'm using FreeBSD 12.1-STABLE. After restarting multicast routing daemon,
daemon can't start with this error: "Failed adding VIF 1 (MRT_ADD_VIF) for
iface em1: Address already in use". pimd tries to disable all vifs from
kernel (shown in output below) but still throws
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
Kubilay Kocak changed:
What|Removed |Added
Assignee|n...@freebsd.org |hsela...@freebsd.org
panic while trying to read multicast stream.
When VIMAGE is enabled make sure the "m_pkthdr.rcvif" pointer is set
for all mbufs being input by the IGMP/MLD6 code. Else there will be a
NULL-pointer dereference in the netisr code when trying to set the
VNET based on the incoming mb
panic while trying to read multicast stream.
When VIMAGE is enabled make sure the "m_pkthdr.rcvif" pointer is set
for all mbufs being input by the IGMP/MLD6 code. Else there will be a
NULL-pointer dereference in the netisr code when trying to set the
VNET based on the incoming mb
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
Hans Petter Selasky changed:
What|Removed |Added
Status|In Progress |Closed
Resolution|--
trying to read multicast stream.
When VIMAGE is enabled make sure the "m_pkthdr.rcvif" pointer is set
for all mbufs being input by the IGMP/MLD6 code. Else there will be a
NULL-pointer dereference in the netisr code when trying to set the
VNET based on the incoming mbuf. Add an
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #20 from Bjoern A. Zeeb ---
Comment on attachment 211583
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211583
Patch to solve problem
Looks ok to me (without further context).
--
You are receiving this mail because
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #19 from Hans Petter Selasky ---
Feel free to test it while bz@ is doing review.
--HPS
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@free
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #18 from Vladislav V. Prodan ---
(In reply to Hans Petter Selasky from comment #17)
Does this patch need to be tested too?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
Ed Maste changed:
What|Removed |Added
CC||ema...@freebsd.org
Component|b
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
Hans Petter Selasky changed:
What|Removed |Added
Attachment #211532|0 |1
is obsolete|
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #16 from Bjoern A. Zeeb ---
Comment on attachment 211532
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211532
Patch to solve problem
Why do we only need to do this in the VIMAGE case and not generally? Is no one
el
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #15 from Vladislav V. Prodan ---
Thanks.
all works!
#ffmpeg -i udp://@239.2.147.238:1234
...
Input #0, mpegts, from 'udp://@239.2.147.238:1234':
Duration: N/A, start: 10866.865244, bitrate: N/A
Program 1
Metadata:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #14 from Vladislav V. Prodan ---
(In reply to Hans Petter Selasky from comment #13)
I applied this second patch and am building my kernel.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
Hans Petter Selasky changed:
What|Removed |Added
Status|New |In Progress
--
You are rece
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #12 from Hans Petter Selasky ---
Hi Bjorn,
IGMP stores the VNET in "m->m_pkthdr.PH_loc.ptr", but the netisr code expects
m->m_pkthdr.rcvif to be valid!
--HPS
--
You are receiving this mail because:
You are the assignee for t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #13 from Hans Petter Selasky ---
Created attachment 211532
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211532&action=edit
Patch to solve problem
Hi,
Can you try this patch for now?
--HPS
--
You are receiving t
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #11 from Vladislav V. Prodan ---
NULL RCVIF AT:
KDB: stack backtrace:
#0 0x80cc68b7 at kdb_backtrace+0x67
#1 0x80dce6b5 at netisr_queue_src+0x95
#2 0x80dce989 at netisr_dispatch_src+0x69
#3 0x80e8
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #10 from Vladislav V. Prodan ---
NULL RCVIF AT:
KDB: stack backtrace:
#0 0x80cc68b7 at kdb_backtrace+0x67
#1 0x80dce6b5 at netisr_queue_src+0x95
#2 0x80dce989 at netisr_dispatch_src+0x69
#3 0x80e7
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #9 from Vladislav V. Prodan ---
I applied this patch and am building my kernel, not GENERIC.
--
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #8 from Hans Petter Selasky ---
Apply patch like this:
cd /usr/src
cat netisr.diff | patch -p1
make buildkernel
make installkernel
reboot
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #7 from Hans Petter Selasky ---
Created attachment 211530
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211530&action=edit
Debug patch
Can you try the attached debug patch, and send the print it generates in dmesg,
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #6 from Vladislav V. Prodan ---
Created attachment 211529
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211529&action=edit
My kernel config
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #5 from Vladislav V. Prodan ---
(In reply to Hans Petter Selasky from comment #4)
No.
The INVARIANTS and INVARIANT_SUPPORT options are not included in my kernel.
--
You are receiving this mail because:
You are the assignee fo
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #4 from Hans Petter Selasky ---
It looks like m->m_pkthdr.rcvif == NULL.
Is this kernel built with INVARIANTS enabled?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
--- Comment #3 from Vladislav V. Prodan ---
(In reply to Hans Petter Selasky from comment #2)
Multicast is available through interface re0 and fxp0
# ifconfig
re0: flags=8943 metric 0 mtu
1500
options=82099
ether 00:e0
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
Hans Petter Selasky changed:
What|Removed |Added
CC||hsela...@freebsd.org
--- Com
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=244002
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243554
--- Comment #5 from Kyle Evans ---
(In reply to James Blachly from comment #4)
Interesting- re-reading your original post... so the proper packets are
appearing via tcpdump, but they're not being tapped off to avahi?
That may be indicativ
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243554
--- Comment #4 from James Blachly ---
@Kyle Evans:
Patch did not do the trick. I can try to tcpdump this weekend (perhaps) to
prove it, but behavior is same as before.
Also I note that the patch adds the call to ETHER_BPF_MTAP at a differ
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243554
Mark Linimon changed:
What|Removed |Added
Assignee|b...@freebsd.org|n...@freebsd.org
Keywords
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=242677
--- Comment #11 from Hans Petter Selasky ---
I think only FreeBSD 12-stable is relevant for this patch.
--
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-ne
1 - 100 of 754 matches
Mail list logo
