[Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable

2021-09-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230996 --- Comment #38 from Jason Tubnor --- (In reply to Kevin Bowling from comment #37) Typical these features should be automatically stripped from an interfaces feature set when the interface has been added to a bridge (which happens correctl

[Bug 258528] [fib_algo][routing] crash after switch algo

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

[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface correctly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication

2021-09-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258527 --- Comment #7 from Cy Schubert --- (In reply to Marek Zarychta from comment #6) The problem is here: 375 if (sm->proto == WPA_PROTO_RSN && 376 !wpa_key_mgmt_suite_b(sm->key_mgmt

ROUTE_MPATH and hashing

2021-09-16 Thread Mark Kamichoff
Hi - Does anyone here know how to tweak the hashing algorithm (per flow/packet/x) that's used for the new ROUTE_MPATH option that's in 13? I'm using FRR 7 and I see both routes in the FIB but only one is ever chosen and takes traffic. (dax:20:23:EDT)% show ipv6 route 2620:6:2003:105::/64 Rout

[Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable

2021-09-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230996 --- Comment #37 from Kevin Bowling --- The above commit I intended to mention 230996 and then this PR as partial. It is not obvious what is or isn't going on here because there is enough postulating and recanting of issues to confuse me.

Re: change to deprecate broadcast on host 0 of a subnet

2021-09-16 Thread Rodney W. Grimes
> Bjoern wrote: > > > On 12 Sep 2021, at 15:25, Mike Karels wrote: > > > > Long ago (4.2BSD), the IP broadcast address was the lowest address on > > > a > > > network, the one with a host part of 0. In RFC1122, the broadcast > > > address > > > was standardized using a host part of all ones.

[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface correctly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication

2021-09-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258527 --- Comment #6 from Marek Zarychta --- (In reply to Cy Schubert from comment #5) #uname -a FreeBSD hplaptop.potoki.eu 13.0-STABLE FreeBSD 13.0-STABLE #10 stable/13-n247106-783ace22648: Mon Sep 6 11:02:44 CEST 2021 r...@hamal.dom.potoki

[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface correctly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication

2021-09-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258527 Cy Schubert changed: What|Removed |Added Status|New |Open -- You are receiving this mail

[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface correctly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication

2021-09-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258527 --- Comment #5 from Cy Schubert --- Can you give me uname -a please. I will try to make my stable/13 system the same as yours in order to process the dump. Otherwise you will need to be my eyes and hands. -- You are receiving this mail be

[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface correctly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication

2021-09-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258527 --- Comment #4 from Marek Zarychta --- (In reply to Cy Schubert from comment #2) I have not tried the devel- branch but can check it as soon as will have the opportunity to do so -- You are receiving this mail because: You are on the CC l

[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface correctly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication

2021-09-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258527 --- Comment #3 from Cy Schubert --- (In reply to Cy Schubert from comment #2) My mistake, stable/13 is still at the same codebase as wpa-supplicant [without the -devel]. -- You are receiving this mail because: You are on the CC list for

[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface correctly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication

2021-09-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258527 Cy Schubert changed: What|Removed |Added Assignee|b...@freebsd.org|c...@freebsd.org -- You are receivi

[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface correctly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication

2021-09-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258527 --- Comment #2 from Cy Schubert --- (In reply to Marek Zarychta from comment #0) Can you try wpa_supplicant-devel from ports. It's the same codebase and will tell us if it's the base software or the FreeBSD implementation. -- You are rec

[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface correctly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication

2021-09-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258527 Marek Zarychta changed: What|Removed |Added Hardware|Any |amd64 -- You are receiving this

[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface correctly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication

2021-09-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258527 Marek Zarychta changed: What|Removed |Added Summary|wpa_supplicant(8) from the |wpa_supplicant(8) from the

[Bug 258527] wpa_supplicant(8) from the base is not able to bring up wlan(4) interface incorrectly due to SIGSEGV after EAP/PEAP MSCHAPv2 authentication

2021-09-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258527 Marek Zarychta changed: What|Removed |Added CC||n...@freebsd.org -- You are rece

[Bug 258528] [fib_algo][routing] crash after switch algo

2021-09-16 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=258528 Bug ID: 258528 Summary: [fib_algo][routing] crash after switch algo Product: Base System Version: 13.0-STABLE Hardware: Any OS: Any Status: New Seve