[Bug 261828] ifconfig: Remove new name display on interface name change

2022-04-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261828 Kubilay Kocak changed: What|Removed |Added Resolution|FIXED |Overcome By Events -- You are rec

Re: Wireguard, MTUs, and jumbo packets

2022-04-05 Thread Dustin Marquess
On Tue, Apr 5, 2022 at 9:46 AM wrote: > > Interesting. That 60 byte overhead (which I understand is intended > to make the protocol connectionless) is concerning, because to send > a 1500 byte packet one needs to have enabled jumbo packets along > the entire path. Otherwise, there will be a lot of

Re: Wireguard, MTUs, and jumbo packets

2022-04-05 Thread freebsd-net
Interesting. That 60 byte overhead (which I understand is intended to make the protocol connectionless) is concerning, because to send a 1500 byte packet one needs to have enabled jumbo packets along the entire path. Otherwise, there will be a lot of fragmentation... which in turn will create y

[Bug 245981] bnxt(4): BCM57414 / BCM57416 not initializing: bnxt0: Unable to allocate device TX queue / queue memory

2022-04-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245981 --- Comment #23 from Kurt Jaeger --- (In reply to Kurt Jaeger from comment #21) dev.bnxt.0.ver.hwrm_if: 1.10.1 dev.bnxt.0.ver.hwrm_fw: 214.4.91 see also https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 vlans do not work on 13.1-RC

[Bug 236983] bnxt(4): VLAN not operational unless explicit "ifconfig promisc" is enabled on physical interface

2022-04-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 --- Comment #29 from Kurt Jaeger --- (In reply to Kurt Jaeger from comment #28) dev.bnxt.0.ver.hwrm_if: 1.10.1 dev.bnxt.0.ver.hwrm_fw: 214.4.91 -- You are receiving this mail because: You are on the CC list for the bug. You are the assign

[Bug 236983] bnxt(4): VLAN not operational unless explicit "ifconfig promisc" is enabled on physical interface

2022-04-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236983 Kurt Jaeger changed: What|Removed |Added CC||p...@freebsd.org --- Comment #28 fro

[Bug 261828] ifconfig: Remove new name display on interface name change

2022-04-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261828 Nick Hibma changed: What|Removed |Added Status|Open|Closed Resolution|---

[Bug 261828] ifconfig: Remove new name display on interface name change

2022-04-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261828 Nick Hibma changed: What|Removed |Added Flags|maintainer-feedback?(nick@v | |an-laarhoven.org)

[Bug 261828] ifconfig: Remove new name display on interface name change

2022-04-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261828 --- Comment #8 from Michael Gmelin --- This change could break people's existing automation though. The commit which added echoing the interface name[0] gives an example of why this was added in the first place: $ ifconfig tap create m

[Bug 261828] ifconfig: Remove new name display on interface name change

2022-04-05 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=261828 --- Comment #7 from Nick Hibma --- Created attachment 232952 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=232952&action=edit One line change -- You are receiving this mail because: You are on the CC list for the bug.