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


2021/freebsd-net/20211003.freebsd-net

Messages: 54, new messages first
Last update: Mon Feb 13 14:19:11 2023
home | archive sorted by: subject | author | date | reverse date 
  1. Oct  3 Lev Serebryakov            TCP-related sysctls from year-old 12-STABLE renders fresh 12-STABLE inaccessible
  2. 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
  3. Oct  3 bugzilla-noreply@FreeBSD.o Problem reports for net@FreeBSD.org that need special attention
  4. 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
  5. 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
  6. 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
  7. 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
  8. 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
  9. 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
 10. Oct  2 bugzilla-noreply@freebsd.o [Bug 258849] IPSec may generate duplicate SPIs
 11. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
 12. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
 13. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
 14. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
 15. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
 16. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
 17. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
 18. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
 19. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
 20. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated



 21. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
 22. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
 23. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
 24. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
 25. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
 26. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
 27. Oct  2 bugzilla-noreply@freebsd.o [Bug 258850] lagg(4): interface vanishes when both member interfaces are inactive/unassociated, and members cannot be reactivated
 28. Oct  2 bugzilla-noreply@freebsd.o [Bug 258849] IPSec may generate duplicate SPIs
 29. Oct  2 bugzilla-noreply@freebsd.o [Bug 258845] iflib: error from IFDI_PROMISC_SET() not handled
 30. Oct  2 bugzilla-noreply@freebsd.o [Bug 226549] lagg failover with re0 and ath0 does not operate by switching back
 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  1 bugzilla-noreply@freebsd.o [Bug 256579] arp(8) -S doesn't honour "blackhole" keyword
 33. Sep 30 bugzilla-noreply@freebsd.o [Bug 256579] arp(8) -S doesn't honour "blackhole" keyword
 34. Sep 30 bugzilla-noreply@freebsd.o [Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable
 35. Sep 30 bugzilla-noreply@freebsd.o [Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable
 36. Sep 30 bugzilla-noreply@freebsd.o [Bug 232451] [igb] I210 NIC can not send more than ~670Mbit/s with flow control enabled.
 37. Sep 30 bugzilla-noreply@freebsd.o [Bug 232451] [igb] I210 NIC can not send more than ~670Mbit/s with flow control enabled.
 38. Sep 30 bugzilla-noreply@freebsd.o [Bug 236067] [em] Intel 82574L can not turn off flow control
 39. Sep 30 bugzilla-noreply@freebsd.o [Bug 232451] [igb] I210 NIC can not send more than ~670Mbit/s with flow control enabled.
 40. Sep 30 bugzilla-noreply@freebsd.o [Bug 256579] arp(8) -S doesn't honour "blackhole" keyword



 41. Sep 30 bugzilla-noreply@freebsd.o [Bug 236067] [em] Intel 82574L can not turn off flow control
 42. Sep 30 bugzilla-noreply@freebsd.o [Bug 189234] [em] Big lag with Ethernet Connection I217-V
 43. Sep 30 bugzilla-noreply@freebsd.o [Bug 232451] [igb] I210 NIC can not send more than ~670Mbit/s with flow control enabled.
 44. Sep 30 bugzilla-noreply@freebsd.o [Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable
 45. Sep 28 bugzilla-noreply@freebsd.o [Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable
 46. Sep 28 bugzilla-noreply@freebsd.o [Bug 258757] [ix] network driver is losing packets
 47. Sep 28 bugzilla-noreply@freebsd.o [Bug 172895] [ixgb] [ixgbe] do not properly determine link-state
 48. Sep 28 bugzilla-noreply@freebsd.o [Bug 210417] Reproducible igb related panic 11.0-ALPHA4
 49. Sep 28 bugzilla-noreply@freebsd.o [Bug 235341] em(4): No network traffic after upgrade from 11.2 to 12.0-RELEASE
 50. Sep 28 bugzilla-noreply@freebsd.o [Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable
 51. Sep 28 bugzilla-noreply@freebsd.o [Bug 230996] em/igb: Intel i210/i350: ifconfig: enabling "vlanhwtag" renders VLAN on i210/i350 NICs unusable
 52. Sep 27 bugzilla-noreply@freebsd.o [Bug 258623] cxgbe(4): Slow routing performance: 2 numa domains vs single numa domain
 53. Sep 27 bugzilla-noreply@freebsd.o [Bug 255678] security/strongswan cant add routes via RTM_ADD via PF_ROUTE socket
 54. Sep 27 bugzilla-noreply@freebsd.o [Bug 258732] [tcp] TCP_MAXSEG does not work

home | archive sorted by: subject | author | date | reverse date