[Bug 247912] [if_bridge] IPv6 ndp does not work across local bridge members

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247912 --- Comment #19 from Martin Birgmeier --- I'd like to come back to this issue. Basically, I am (still :-)) not assigning the IP addresses to the bridge interface. The major reason for this is that I am assembling/disassembling the bridge a

[Bug 247912] [if_bridge] IPv6 ndp does not work across local bridge members

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247912 Martin Birgmeier changed: What|Removed |Added Version|12.1-RELEASE|12.2-RELEASE -- You are receiv

[PATCH 1/2] uipc_socket: add sogetsockaddr convenience function

It is useful to be able to call pr_usrreqs->pru_sockaddr on a struct socket, so this commit adds a wrapper around it, analogous to the other types of socket getters. Original-author: Kyle Evans Signed-off-by: Jason A. Donenfeld --- sys/kern/uipc_socket.c | 11 +++ sys/sys/socketvar.h

[PATCH 2/2] ck: add pr_{load,store}_bool functions

While these are functionally the same as ck_pr_{load,store}_8, it's actually quite useful to be able to use this on ordinary bool types, without having to add casting to every callsite. Signed-off-by: Jason A. Donenfeld --- sys/contrib/ck/include/ck_pr.h | 2 ++ 1 file changed, 2 insertions(+)

[PATCH 0/2] two small additions in advance of if_wg

Hi, This series of two is a "trial series" to get a hang of sending in patches to FreeBSD and to very gradually begin the process of upstreaming parts of if_wg. I'll eventually have some larger crypto changes to send in (in addition to if_wg itself, in due time), but it seems wise to start with so

Client Networking Issues / NIC Lab

Greetings, I have been looking into client networking issues in FreeBSD lately. To summarize the situation, common NICs like Intel gigabit (e1000 aka lem(4)/em(4)/igb(4)), Realtek (re(4)), Aquantia, and Tehuti Networks are unmaintained or not present on FreeBSD. The purpose of this thread is to g

[Bug 211219] [e1000] NIC status does not pass into a state of "no carrier" after disconnecting the cable.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211219 Kevin Bowling changed: What|Removed |Added CC||kbowl...@freebsd.org --- Comment #

[Bug 193953] vlan(4) on LACP lagg(4) do not update if_baudrate value and thus SNMP daemons do not provide high capacity counters

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193953 --- Comment #14 from Andrey V. Elsukov --- (In reply to Kubilay Kocak from comment #13) I think I remembered why we use this patch. Without the proposed eventhandler vlan interfaces created on top of lagg will not modify if_boudrate when l

[Bug 235524] igb(4): Ethernet interface loses active link state

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235524 --- Comment #12 from m...@ifis.cs.tu-bs.de --- Created a new bug report, see https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255319 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the

[Bug 235341] em(4): No network traffic after upgrade from 11.2 to 12.0-RELEASE

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=235341 --- Comment #3 from kaan --- Yes, we still use this hardware, I updated it to 11.4 and I plan to migrate to version 13 but because this is a rather critical network node, we will carry out migration in the summer. This is the pciconf -lv o

[Bug 255264] Unable to add default route for fib

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255264 --- Comment #5 from Neal Nelson --- The entry in /usr/src/UPDATING that has been pointed out to me explains the situation a little better than the current message. I'm sure the current message makes sense to those that know the ins and outs