[Bug 220468] libfetch: Does not handle 407 (proxy auth) when connecting to HTTPS using connect tunnel

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220468 Eugene Grosbein changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org

Re: CARP over VLAN over LAGG

On Mon, Aug 31, 2020 at 01:55:52PM +0200, Michael Gmelin wrote: > > > > On 31. Aug 2020, at 10:37, Julien Cigar wrote: > > > > On Fri, Aug 28, 2020 at 04:52:01PM +0200, Julien Cigar wrote: > >> Hello, > >> > >> I have a "highly available" router/firewall with the following > >> configuration

wireguard integration D26137 connectivity test

I can confirm that the issue reported in https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247853 is now resolved. Thanks Peter ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.or

[Bug 249050] if_qlxgb mtu not initialized bug causing wrong pkt 0x62 dump start

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org -- You are receiv

[Bug 249050] if_qlxgb mtu not initialized bug causing wrong pkt 0x62 dump start

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050 Mark Linimon changed: What|Removed |Added Attachment #217690|0 |1 is patch|

[Bug 249050] if_qlxgb mtu not initialized bug causing wrong pkt 0x62 dump start

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org Stat

[Bug 249050] if_qlxgb mtu not initialized bug causing wrong pkt 0x62 dump start

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050 --- Comment #2 from Christian Vallières --- The interface didn't respond when in bridge, but I realized that moving ifp->if_capabilities = IFCAP_LINKSTATE; didn't solve, forget that part. -- You are receiving this mail because: You are th

[Bug 249050] if_qlxgb mtu not initialized bug causing wrong pkt 0x62 dump start

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050 --- Comment #3 from commit-h...@freebsd.org --- A commit references this bug: Author: markj Date: Tue Sep 1 20:13:51 UTC 2020 New revision: 365060 URL: https://svnweb.freebsd.org/changeset/base/365060 Log: qlxgb: Initialize if_mtu befor

[Bug 249050] if_qlxgb mtu not initialized bug causing wrong pkt 0x62 dump start

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050 Mark Johnston changed: What|Removed |Added Assignee|n...@freebsd.org |ma...@freebsd.org Sta

[Bug 249050] if_qlxgb mtu not initialized bug causing wrong pkt 0x62 dump start

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050 Mark Johnston changed: What|Removed |Added CC||p...@pogotopia.net --- Comment #4

[Bug 226217] if_qlxgb (QLogic cLOM8214) not working for me when configured via netif

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226217 Mark Johnston changed: What|Removed |Added CC||ma...@freebsd.org Resoluti

[Bug 249058] Intel X710-T2L Ethernet Adapter not detected in FreeBSD 12.1

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249058 Mark Linimon changed: What|Removed |Added Assignee|b...@freebsd.org|n...@freebsd.org Keywords

[Bug 249058] Intel X710-T2L Ethernet Adapter not detected in FreeBSD 12.1

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249058 VVD changed: What|Removed |Added CC||v...@unislabs.com --- Comment #1 from VVD -

[Bug 249058] Intel X710-T2L Ethernet Adapter not detected in FreeBSD 12.1

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249058 --- Comment #2 from Abhinav Tella --- Thanks for looking into this. My card is the standard Intel product, not an OEM version. I would assume this issue would also affect the Intel X710-T4L as well. Here is the pciconf -lv output after co

[Bug 249058] Intel X710-T2L Ethernet Adapter not detected in FreeBSD 12.1

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249058 VVD changed: What|Removed |Added CC||e...@freebsd.org --- Comment #3 from VVD --

[Bug 249058] Intel X710-T2L Ethernet Adapter not detected in FreeBSD 12.1

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249058 --- Comment #4 from Abhinav Tella --- Nice, thanks for the info and update, glad to hear this is being fixed. -- You are receiving this mail because: You are the assignee for the bug. ___ freebs