Skip site navigation (1)Skip section navigation (2)


2021/freebsd-net/20210919.freebsd-net

Messages: 39, sorted by subject
Last page update: Sat Jan 3 13:11:42 UTC 2026
home | up | archive | sorted by: subject - author - date - reverse date 
  1. Sep 15 bugzilla-noreply@freebsd.o [Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable
  2. Sep 16 bugzilla-noreply@freebsd.o  [Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable
  3. Sep 17 bugzilla-noreply@freebsd.o  [Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable
  4. Sep 18 bugzilla-noreply@freebsd.o  [Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable
  5. Sep 17 bugzilla-noreply@freebsd.o [Bug 250436] Regression in 12.stable em driver
  6. Sep 17 bugzilla-noreply@freebsd.o [Bug 254341] igb hung every 5-20 hours. ifconfig down+up solves the problem for next N hours
  7. Sep 19 bugzilla-noreply@freebsd.o [Bug 255678] security/strongswan cant add routes via RTM_ADD via PF_ROUTE socket
  8. Sep 15 bugzilla-noreply@freebsd.o [Bug 258258] igb - batch creating vlans causes ifconfig %100 cpu usage - dmesg: igbX: Hardware Initialization Failed
  9. Sep 15 bugzilla-noreply@freebsd.o  [Bug 258258] igb - batch creating vlans causes ifconfig %100 cpu usage - dmesg: igbX: Hardware Initialization Failed
 10. Sep 15 bugzilla-noreply@freebsd.o  [Bug 258258] igb - batch creating vlans causes ifconfig %100 cpu usage - dmesg: igbX: Hardware Initialization Failed
 11. Sep 15 bugzilla-noreply@freebsd.o  [Bug 258258] igb - batch creating vlans causes ifconfig %100 cpu usage - dmesg: igbX: Hardware Initialization Failed
 12. Sep 15 bugzilla-noreply@freebsd.o [Bug 258420] stge: fix null pointer dereference
 13. Sep 16 bugzilla-noreply@freebsd.o [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 authen
 14. Sep 16 bugzilla-noreply@freebsd.o  [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 authen
 15. Sep 16 bugzilla-noreply@freebsd.o  [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 authen
 16. Sep 16 bugzilla-noreply@freebsd.o  [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 authen
 17. Sep 16 bugzilla-noreply@freebsd.o  [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 authen
 18. Sep 16 bugzilla-noreply@freebsd.o  [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 authen
 19. Sep 16 bugzilla-noreply@freebsd.o  [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 authen
 20. Sep 16 bugzilla-noreply@freebsd.o  [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 authen

 21. Sep 16 bugzilla-noreply@freebsd.o  [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 authen
 22. Sep 17 bugzilla-noreply@freebsd.o  [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 authen
 23. Sep 17 bugzilla-noreply@freebsd.o  [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 authen
 24. Sep 17 bugzilla-noreply@freebsd.o  [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 authen
 25. Sep 17 bugzilla-noreply@freebsd.o  [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 authen
 26. Sep 17 bugzilla-noreply@freebsd.o  [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 authen
 27. Sep 17 bugzilla-noreply@freebsd.o  [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 authen
 28. Sep 18 bugzilla-noreply@freebsd.o  [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 authen
 29. Sep 16 bugzilla-noreply@freebsd.o [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 auth
 30. Sep 16 bugzilla-noreply@freebsd.o [Bug 258528] [fib_algo][routing] crash after switch algo
 31. Sep 17 bugzilla-noreply@freebsd.o  [Bug 258528] [fib_algo][routing] crash after switch algo
 32. Sep 15 Bjoern A. Zeeb             Re: change to deprecate broadcast on host 0 of a subnet
 33. Sep 15 Mike Karels                 Re: change to deprecate broadcast on host 0 of a subnet
 34. Sep 16 sthaug@nethelp.no           Re: change to deprecate broadcast on host 0 of a subnet
 35. Sep 16 Rodney W. Grimes            Re: change to deprecate broadcast on host 0 of a subnet
 36. Sep 19 bugzilla-noreply@FreeBSD.o Problem reports for net@FreeBSD.org that need special attention
 37. Sep 17 Mark Kamichoff             ROUTE_MPATH and hashing
 38. Sep 13 Andrey V. Elsukov          Re: TCP6 regression for MTU path on stable/13
 39. Sep 13 Harry Schmalzbauer          Re: TCP6 regression for MTU path on stable/13
home | up | archive | sorted by: subject - author - date - reverse date