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

2020-09-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220468

Eugene Grosbein  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|n...@freebsd.org
 CC||eu...@freebsd.org

--- Comment #12 from Eugene Grosbein  ---
Reset Assignee after 10 months of inactivity.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: CARP over VLAN over LAGG

2020-09-01 Thread Julien Cigar 
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 (1). Those are plugged in two 2930F (with VSF) using LACP.
> >> It works well, except that I have some weird issues with the CARP 
> >> demotion counter when I'm unplugging some interfaces involved in the 
> >> lagg/carp setup, for example if I unplug/replug igb0 and igb1 in this 
> >> case:
> >> 
> >> (dmesg):
> >> igb0: link state changed to DOWN
> >> igb1: link state changed to DOWN
> >> carp: demoted by 240 to 240 (send error 50 on vlan11)
> >> carp: 11@vlan11: MASTER -> BACKUP (more frequent advertisement received)
> >> vlan11: deletion failed: 3
> >> igb1: link state changed to UP
> >> igb0: link state changed to UP
> >> 
> >> then the CARP status stays to BACKUP unless I demote the CARP demotion
> >> counter manually with: sudo sysctl net.inet.carp.demotion=-240:
> >> 
> >> (dmesg):
> >> carp: demoted by -240 to 0 (sysctl)
> >> carp: 11@vlan11: BACKUP -> MASTER (preempting a slower master)
> >> 
> >> I guess this is because it takes some time for lagg/lacp to converge and
> >> thus carp thinks that there is a problematic condition as it experiences
> >> problems with sending announcements..
> >> 
> >> What it the best way to handle this?
> > 
> > I'm wondering if setting net.inet.carp.senderr_demotion_factor to "0"
> > could be a solution? Are there any downsides of setting this to "0"
> > instead of "240"?
> > 
> 
> Sharing your pf.conf from both hosts could be helpful analyzing the issue.

Here is my pf.conf (it's the same on both host):
https://gist.github.com/silenius/b758851f03c28ef8caaa53cfe381c455

However, I don't think pf is the issue here, the problem is that there
is a slight delay when LAGG/LACP converge and thus CARP increase the
demotion counter by net.inet.carp.senderr_demotion_factor (240).

> 
> -m
> 
> 

-- 
Julien Cigar
Belgian Biodiversity Platform (http://www.biodiversity.be)
PGP fingerprint: EEF9 F697 4B68 D275 7B11  6A25 B2BB 3710 A204 23C0
No trees were killed in the creation of this message.
However, many electrons were terribly inconvenienced.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

wireguard integration D26137 connectivity test

2020-09-01 Thread Peter Libassi 
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.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

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

2020-09-01 Thread bugzilla-noreply 
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 receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

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

2020-09-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050

Mark Linimon  changed:

   What|Removed |Added

 Attachment #217690|0   |1
   is patch||
 Attachment #217690|file_249050.txt |file_249050.patch
   filename||

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

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

2020-09-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050

Mark Johnston  changed:

   What|Removed |Added

 CC||ma...@freebsd.org
 Status|New |Open

--- Comment #1 from Mark Johnston  ---
The MTU initialization looks reasonable, but after ether_ifattach() we are
still unconditionally assigning to if_capabilities, so doesn't IFCAP_LINKSTATE
get cleared?

What problems were you seeing with up'ing the interface?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

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

2020-09-01 Thread bugzilla-noreply 
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 the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

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

2020-09-01 Thread bugzilla-noreply 
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 before setting max_frame_size.

  Previously we were relying on ether_ifattach() to set if_mtu, but
  max_frame_size is initialized earlier.  This fixes a regression
  introduced by r250375.

  PR:   249050
  Submitted by: Christian Valli?res 
  MFC after:3 days

Changes:
  head/sys/dev/qlxgb/qla_os.c

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

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

2020-09-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050

Mark Johnston  changed:

   What|Removed |Added

   Assignee|n...@freebsd.org |ma...@freebsd.org
 Status|Open|In Progress

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

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

2020-09-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249050

Mark Johnston  changed:

   What|Removed |Added

 CC||p...@pogotopia.net

--- Comment #4 from Mark Johnston  ---
*** Bug 226217 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

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

2020-09-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226217

Mark Johnston  changed:

   What|Removed |Added

 CC||ma...@freebsd.org
 Resolution|--- |DUPLICATE
 Status|New |Closed

--- Comment #6 from Mark Johnston  ---
Sorry it took so long for this to get resolved.  Thanks to Christian it's fixed
in head now and will be merged in a few days.

*** This bug has been marked as a duplicate of bug 249050 ***

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

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

2020-09-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249058

Mark Linimon  changed:

   What|Removed |Added

   Assignee|b...@freebsd.org|n...@freebsd.org
   Keywords||IntelNetworking, regression

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

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

2020-09-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249058

VVD  changed:

   What|Removed |Added

 CC||v...@unislabs.com

--- Comment #1 from VVD  ---
GENERIC?
pciconf -lv from both 11.3 and 12.1.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

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

2020-09-01 Thread bugzilla-noreply 
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 compiling and installing Intel ixl driver
version 1.12.2 on 12.1.

 I will also post the output from 11.3 and 12.1 (with default driver) as soon
as I get a chance either today or tomorrow.






hostb0@pci0:0:0:0:  class=0x06 card=0x1b2d15d9 chip=0x14501022 rev=0x00
hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'Family 17h (Models 00h-0fh) Root Complex'
class  = bridge
subclass   = HOST-PCI
hostb1@pci0:0:1:0:  class=0x06 card=0x chip=0x14521022 rev=0x00
hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge'
class  = bridge
subclass   = HOST-PCI
pcib1@pci0:0:1:1:   class=0x060400 card=0x14531022 chip=0x14531022 rev=0x00
hdr=0x01
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'Family 17h (Models 00h-0fh) PCIe GPP Bridge'
class  = bridge
subclass   = PCI-PCI
pcib2@pci0:0:1:3:   class=0x060400 card=0x14531022 chip=0x14531022 rev=0x00
hdr=0x01
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'Family 17h (Models 00h-0fh) PCIe GPP Bridge'
class  = bridge
subclass   = PCI-PCI
pcib4@pci0:0:1:5:   class=0x060400 card=0x14531022 chip=0x14531022 rev=0x00
hdr=0x01
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'Family 17h (Models 00h-0fh) PCIe GPP Bridge'
class  = bridge
subclass   = PCI-PCI
hostb2@pci0:0:2:0:  class=0x06 card=0x chip=0x14521022 rev=0x00
hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge'
class  = bridge
subclass   = HOST-PCI
hostb3@pci0:0:3:0:  class=0x06 card=0x chip=0x14521022 rev=0x00
hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge'
class  = bridge
subclass   = HOST-PCI
pcib5@pci0:0:3:1:   class=0x060400 card=0x14531022 chip=0x14531022 rev=0x00
hdr=0x01
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'Family 17h (Models 00h-0fh) PCIe GPP Bridge'
class  = bridge
subclass   = PCI-PCI
hostb4@pci0:0:4:0:  class=0x06 card=0x chip=0x14521022 rev=0x00
hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge'
class  = bridge
subclass   = HOST-PCI
hostb5@pci0:0:7:0:  class=0x06 card=0x chip=0x14521022 rev=0x00
hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge'
class  = bridge
subclass   = HOST-PCI
pcib6@pci0:0:7:1:   class=0x060400 card=0x14541022 chip=0x14541022 rev=0x00
hdr=0x01
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus
B'
class  = bridge
subclass   = PCI-PCI
hostb6@pci0:0:8:0:  class=0x06 card=0x chip=0x14521022 rev=0x00
hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge'
class  = bridge
subclass   = HOST-PCI
pcib7@pci0:0:8:1:   class=0x060400 card=0x14541022 chip=0x14541022 rev=0x00
hdr=0x01
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus
B'
class  = bridge
subclass   = PCI-PCI
intsmb0@pci0:0:20:0:class=0x0c0500 card=0x790b15d9 chip=0x790b1022 rev=0x59
hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'FCH SMBus Controller'
class  = serial bus
subclass   = SMBus
isab0@pci0:0:20:3:  class=0x060100 card=0x790e15d9 chip=0x790e1022 rev=0x51
hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'FCH LPC Bridge'
class  = bridge
subclass   = PCI-ISA
hostb7@pci0:0:24:0: class=0x06 card=0x chip=0x14601022 rev=0x00
hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function
0'
class  = bridge
subclass   = HOST-PCI
hostb8@pci0:0:24:1: class=0x06 card=0x chip=0x14611022 rev=0x00
hdr=0x00
vendor = 'Advanced Micro Devices, Inc. [AMD]'
device = 'Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function
1'
class  = bridge
subclass   = HOST-PCI
hostb9@pci0:0:24:2: class=0x06 card=0x chip=0x14621022 rev=0x00
hdr=0x00
v

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

2020-09-01 Thread bugzilla-noreply 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=249058

VVD  changed:

   What|Removed |Added

 CC||e...@freebsd.org

--- Comment #3 from VVD  ---
Check this for PCI ID 0x15ff:
https://svnweb.freebsd.org/base/releng/11.3/sys/dev/ixl/i40e_devids.h?r1=349026&r2=349181
https://svnweb.freebsd.org/base/releng/12.1/sys/dev/ixl/i40e_devids.h?view=log
https://svnweb.freebsd.org/base/stable/12/sys/dev/ixl/i40e_devids.h?revision=363876&view=markup

Don't know why, but stable/12 have old version of the ixl driver…

It was commited to HEAD 1:30h ago only!
https://svnweb.freebsd.org/base/head/sys/dev/ixl/i40e_devids.h?r1=361992&r2=365231
> MFC after:3 days

AFAIU, this change will be commited to stable/12 at 4-5th of Sep, and 12.2
should get support of this hardware.
Release in 2 months: https://www.freebsd.org/releases/12.2R/schedule.html

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

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

2020-09-01 Thread bugzilla-noreply 
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.
___
freebsd-net@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"