2021/freebsd-net/20211003.freebsd-net
Messages: 54, 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 28 bugzilla-noreply@freebsd.o [Bug 172895] [ixgb] [ixgbe] do not properly determine link-state 2. Sep 30 bugzilla-noreply@freebsd.o [Bug 189234] [em] Big lag with Ethernet Connection I217-V 3. Sep 28 bugzilla-noreply@freebsd.o [Bug 210417] Reproducible igb related panic 11.0-ALPHA4 4. Oct 2 bugzilla-noreply@freebsd.o [Bug 226549] lagg failover with re0 and ath0 does not operate by switching back 5. Sep 28 bugzilla-noreply@freebsd.o [Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable 6. Sep 28 bugzilla-noreply@freebsd.o [Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable 7. Sep 28 bugzilla-noreply@freebsd.o [Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable 8. Sep 30 bugzilla-noreply@freebsd.o [Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable 9. Sep 30 bugzilla-noreply@freebsd.o [Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable 10. Sep 30 bugzilla-noreply@freebsd.o [Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable 11. Sep 30 bugzilla-noreply@freebsd.o [Bug 232451] [igb] I210 NIC can not send more than ~670Mbit/s with flow control enabled. 12. Sep 30 bugzilla-noreply@freebsd.o [Bug 232451] [igb] I210 NIC can not send more than ~670Mbit/s with flow control enabled. 13. Sep 30 bugzilla-noreply@freebsd.o [Bug 232451] [igb] I210 NIC can not send more than ~670Mbit/s with flow control enabled. 14. Sep 30 bugzilla-noreply@freebsd.o [Bug 232451] [igb] I210 NIC can not send more than ~670Mbit/s with flow control enabled. 15. Sep 28 bugzilla-noreply@freebsd.o [Bug 235341] em(4): No network traffic after upgrade from 11.2 to 12.0-RELEASE 16. Sep 30 bugzilla-noreply@freebsd.o [Bug 236067] [em] Intel 82574L can not turn off flow control 17. Sep 30 bugzilla-noreply@freebsd.o [Bug 236067] [em] Intel 82574L can not turn off flow control 18. Sep 27 bugzilla-noreply@freebsd.o [Bug 255678] security/strongswan cant add routes via RTM_ADD via PF_ROUTE socket 19. Oct 1 bugzilla-noreply@freebsd.o [Bug 256579] arp(8) -S doesn't honour "blackhole" keyword 20. Sep 30 bugzilla-noreply@freebsd.o [Bug 256579] arp(8) -S doesn't honour "blackhole" keyword
21. Sep 30 bugzilla-noreply@freebsd.o [Bug 256579] arp(8) -S doesn't honour "blackhole" keyword 22. Sep 27 bugzilla-noreply@freebsd.o [Bug 258623] cxgbe(4): Slow routing performance: 2 numa domains vs single numa domain 23. Sep 27 bugzilla-noreply@freebsd.o [Bug 258732] [tcp] TCP_MAXSEG does not work 24. Sep 28 bugzilla-noreply@freebsd.o [Bug 258757] [ix] network driver is losing packets 25. Oct 2 bugzilla-noreply@freebsd.o [Bug 258845] iflib: error from IFDI_PROMISC_SET() not handled 26. Oct 2 bugzilla-noreply@freebsd.o [Bug 258849] IPSec may generate duplicate SPIs 27. Oct 2 bugzilla-noreply@freebsd.o [Bug 258849] IPSec may generate duplicate SPIs 28. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 29. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 30. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 31. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 32. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 33. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 34. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 35. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 36. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 37. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 38. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 39. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 40. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
41. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 42. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 43. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 44. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 45. Oct 2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated 46. Oct 2 bugzilla-noreply@freebsd.o [Bug 258874] route add -inet 240/4 results in 0.0.0.0/4 127.0.0.1 UGRS lo0 47. Oct 3 bugzilla-noreply@freebsd.o [Bug 258874] route add -inet 240/4 results in 0.0.0.0/4 127.0.0.1 UGRS lo0 48. Oct 3 bugzilla-noreply@freebsd.o [Bug 258874] route add -inet 240/4 results in 0.0.0.0/4 127.0.0.1 UGRS lo0 49. Oct 3 bugzilla-noreply@freebsd.o [Bug 258874] route add -inet 240/4 results in 0.0.0.0/4 127.0.0.1 UGRS lo0 50. Oct 3 bugzilla-noreply@freebsd.o [Bug 258874] route add -inet 240/4 results in 0.0.0.0/4 127.0.0.1 UGRS lo0 51. Oct 3 bugzilla-noreply@freebsd.o [Bug 258874] route add -inet 240/4 results in 0.0.0.0/4 127.0.0.1 UGRS lo0 52. Oct 3 bugzilla-noreply@freebsd.o [Bug 258874] route add -inet 240/4 results in 0.0.0.0/4 127.0.0.1 UGRS lo0 53. Oct 3 bugzilla-noreply@FreeBSD.o Problem reports for net@FreeBSD.org that need special attention 54. Oct 3 Lev Serebryakov TCP-related sysctls from year-old 12-STABLE renders fresh 12-STABLE inaccessible
home | up | archive | sorted by: subject - author - date - reverse date