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


2021/freebsd-net/20210926.freebsd-net

Messages: 55, 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 20 bugzilla-noreply@freebsd.o [Bug 194453] dummynet(4): pipe config bw parameter limited to 2Gbits/s (signed integer limit)
  2. Sep 20 bugzilla-noreply@freebsd.o  [Bug 194453] dummynet(4): pipe config bw parameter limited to 2Gbits/s (signed integer limit)
  3. Sep 24 bugzilla-noreply@freebsd.o  [Bug 194453] dummynet(4): pipe config bw parameter limited to 2Gbits/s (signed integer limit)
  4. Sep 24 bugzilla-noreply@freebsd.o  [Bug 194453] dummynet(4): pipe config bw parameter limited to 2Gbits/s (signed integer limit)
  5. Sep 24 bugzilla-noreply@freebsd.o  [Bug 194453] dummynet(4): pipe config bw parameter limited to 2Gbits/s (signed integer limit)
  6. Sep 24 bugzilla-noreply@freebsd.o  [Bug 194453] dummynet(4): pipe config bw parameter limited to 2Gbits/s (signed integer limit)
  7. Sep 24 bugzilla-noreply@freebsd.o  [Bug 194453] dummynet(4): pipe config bw parameter limited to 2Gbits/s (signed integer limit)
  8. Sep 25 bugzilla-noreply@freebsd.o [Bug 235341] em(4): No network traffic after upgrade from 11.2 to 12.0-RELEASE
  9. Sep 22 bugzilla-noreply@freebsd.o [Bug 253469] realtek-re-kmod MC filter problem
 10. Sep 24 bugzilla-noreply@freebsd.o [Bug 254695] Hyper-V + TCP_BBR: Kernel Panic: Assertion in_epoch(net_epoch_preempt) failed at netinet/tcp_lro.c:1180
 11. Sep 20 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
 12. Sep 20 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
 13. Sep 20 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 20 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 21 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 21 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 20 bugzilla-noreply@freebsd.o [Bug 258623] [routing] peformance - 2 numa domains vs signale numa domain
 18. Sep 20 bugzilla-noreply@freebsd.o [Bug 258623] cxgbe(4): Slow routing performance: 2 numa domains vs single numa domain
 19. Sep 20 bugzilla-noreply@freebsd.o  [Bug 258623] cxgbe(4): Slow routing performance: 2 numa domains vs single numa domain
 20. Sep 20 bugzilla-noreply@freebsd.o  [Bug 258623] cxgbe(4): Slow routing performance: 2 numa domains vs single numa domain

 21. Sep 20 bugzilla-noreply@freebsd.o  [Bug 258623] cxgbe(4): Slow routing performance: 2 numa domains vs single numa domain
 22. Sep 20 bugzilla-noreply@freebsd.o  [Bug 258623] cxgbe(4): Slow routing performance: 2 numa domains vs single numa domain
 23. Sep 20 bugzilla-noreply@freebsd.o  [Bug 258623] cxgbe(4): Slow routing performance: 2 numa domains vs single numa domain
 24. Sep 20 bugzilla-noreply@freebsd.o  [Bug 258623] cxgbe(4): Slow routing performance: 2 numa domains vs single numa domain
 25. Sep 21 bugzilla-noreply@freebsd.o  [Bug 258623] cxgbe(4): Slow routing performance: 2 numa domains vs single numa domain
 26. Sep 22 bugzilla-noreply@freebsd.o  [Bug 258623] cxgbe(4): Slow routing performance: 2 numa domains vs single numa domain
 27. Sep 26 bugzilla-noreply@freebsd.o [Bug 258732] [tcp] TCP_MAXSEG does not work
 28. Sep 26 bugzilla-noreply@freebsd.o [Bug 258732] TCP_MAXSEG does not work
 29. Sep 26 bugzilla-noreply@freebsd.o  [Bug 258732] TCP_MAXSEG does not work
 30. Sep 26 Harry Schmalzbauer         Re: git: 1a72c3d76aea - stable/13 - e1000: always enable PCSD when RSS hashing [Was: TCP6 regression for MTU path on stable/13]
 31. Sep 26 Kevin Bowling               Re: git: 1a72c3d76aea - stable/13 - e1000: always enable PCSD when RSS hashing [Was: TCP6 regression for MTU path on stable/13]
 32. Sep 23 Kevin Bowling              Re: igb(4) and VLAN issue?
 33. Sep 24 Peter Jeremy               IPSEC problems with pf
 34. Sep 24 Michael Sierchio            Re: IPSEC problems with pf
 35. Sep 25 charles@freebsdbrasil.com.  Re: IPSEC problems with pf
 36. Sep 25 Eugene Grosbein             Re: IPSEC problems with pf
 37. Sep 25 Andrey V. Elsukov           Re: IPSEC problems with pf
 38. Sep 26 Peter Jeremy                Re: IPSEC problems with pf
 39. Sep 26 Eugene Grosbein             Re: IPSEC problems with pf
 40. Sep 25 Andriy Gapon               Re: page fault in pfioctl

 41. Sep 25 Andriy Gapon                Re: page fault in pfioctl
 42. Sep 25 Kristof Provost             Re: page fault in pfioctl
 43. Sep 25 Andriy Gapon                Re: page fault in pfioctl
 44. Sep 25 Andriy Gapon                Re: page fault in pfioctl
 45. Sep 20 <driesm.michiels@gmail.com Performance of PPPOE in FreeBSD
 46. Sep 20 Julien Cigar                Re: Performance of PPPOE in FreeBSD
 47. Sep 20 Eugene Grosbein             Re: Performance of PPPOE in FreeBSD
 48. Sep 21 Evilham                     Re: Performance of PPPOE in FreeBSD
 49. Sep 21 <driesm.michiels@gmail.com  RE: Performance of PPPOE in FreeBSD
 50. Sep 21 Evilham                     Re: Performance of PPPOE in FreeBSD
 51. Sep 26 bugzilla-noreply@FreeBSD.o Problem reports for net@FreeBSD.org that need special attention
 52. Sep 20 Alexander V. Chernikov     Re: ROUTE_MPATH and hashing
 53. Sep 21 Mark Kamichoff              Re: ROUTE_MPATH and hashing
 54. Sep 21 Francois ten Krooden       RE: Vector Packet Processing (VPP) portability on FreeBSD
 55. Sep 22 Santiago Martinez           Re: Vector Packet Processing (VPP) portability on FreeBSD

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