2017/freebsd-net/20170319.freebsd-net
Messages: 121, sorted by subject
|
Last page update: Sat Jan 3 13:11:31 UTC 2026
|
|
home | up | archive | sorted by: subject - author - date - reverse date
1. Mar 17 bugzilla-noreply@freebsd.o [Bug 196361] Constrain IPv6 routes to each FIB (Consistent with IPv4 route behaviour) 2. Mar 16 bugzilla-noreply@freebsd.o [Bug 208409] [PATCH] igb and ALTQ 3. Mar 15 bugzilla-noreply@freebsd.o [Bug 209581] igb vf driver does not correctly handle vlan tag 4. Mar 16 bugzilla-noreply@freebsd.o [Bug 209581] igb vf driver does not correctly handle vlan tag 5. Mar 18 bugzilla-noreply@freebsd.o [Bug 212018] Enable IPSEC_NAT_T in GENERIC kernel configuration 6. Mar 18 bugzilla-noreply@freebsd.o [Bug 212018] Enable IPSEC_NAT_T in GENERIC kernel configuration 7. Mar 13 bugzilla-noreply@freebsd.o [Bug 213015] openvswitch and vnet jails - panic when bridge is destroyed and recreated 8. Mar 15 bugzilla-noreply@freebsd.o [Bug 213257] Crash in IGB driver with ALTQ 9. Mar 14 bugzilla-noreply@freebsd.o [Bug 217413] panic: Assertion err == 0 failed at /usr/src/sys/net/iflib.c:2242 after 1000baseT physical link shutdown 10. Mar 14 bugzilla-noreply@freebsd.o [Bug 217606] Bridge stops working after some days 11. Mar 15 bugzilla-noreply@freebsd.o [Bug 217606] Bridge stops working after some days 12. Mar 15 bugzilla-noreply@freebsd.o [Bug 217606] Bridge stops working after some days 13. Mar 15 bugzilla-noreply@freebsd.o [Bug 217606] Bridge stops working after some days 14. Mar 15 bugzilla-noreply@freebsd.o [Bug 217606] Bridge stops working after some days 15. Mar 15 bugzilla-noreply@freebsd.o [Bug 217606] Bridge stops working after some days 16. Mar 16 bugzilla-noreply@freebsd.o [Bug 217606] Bridge stops working after some days 17. Mar 17 bugzilla-noreply@freebsd.o [Bug 217606] Bridge stops working after some days 18. Mar 13 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO time 19. Mar 14 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO time 20. Mar 14 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO time
21. Mar 14 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO time 22. Mar 14 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO time 23. Mar 14 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 24. Mar 14 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 25. Mar 14 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 26. Mar 15 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 27. Mar 16 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 28. Mar 16 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 29. Mar 16 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 30. Mar 16 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 31. Mar 16 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 32. Mar 16 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 33. Mar 16 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 34. Mar 16 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 35. Mar 17 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 36. Mar 17 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 37. Mar 17 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 38. Mar 17 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 39. Mar 17 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 40. Mar 17 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times
41. Mar 17 bugzilla-noreply@freebsd.o [Bug 217637] One TCP connection accepted TWO times 42. Mar 18 bugzilla-noreply@freebsd.o [Bug 217667] arp "moved" log message gives incorrect "from" MAC 43. Mar 18 bugzilla-noreply@freebsd.o [Bug 217667] arp "moved" log message gives incorrect "from" MAC 44. Mar 13 bugzilla-noreply@freebsd.o [Bug 217712] [netgraph]: panic during boot with WITNESS / DIAGNOSTIC / etc enabled (r315088) 45. Mar 13 bugzilla-noreply@freebsd.o [Bug 217721] axge(4) hangs while link goes offline 46. Mar 13 bugzilla-noreply@freebsd.o [Bug 217721] axge(4) hangs while link goes offline 47. Mar 13 bugzilla-noreply@freebsd.o [Bug 217721] axge(4) hangs while link goes offline 48. Mar 16 bugzilla-noreply@freebsd.o [Bug 217721] axge(4) hangs while link goes offline 49. Mar 16 bugzilla-noreply@freebsd.o [Bug 217721] axge(4) hangs while link goes offline 50. Mar 16 bugzilla-noreply@freebsd.o [Bug 217721] axge(4) hangs while link goes offline 51. Mar 13 bugzilla-noreply@freebsd.o [Bug 217746] sys/dev/cxgbe/t4_main.c: PVS-Studio: Expression is Always True (CWE-571) (3) 52. Mar 13 bugzilla-noreply@freebsd.o [Bug 217746] sys/dev/cxgbe/t4_main.c: PVS-Studio: Expression is Always True (CWE-571) (3) 53. Mar 13 bugzilla-noreply@freebsd.o [Bug 217748] sys/dev/ixgbe/if_ix.c: PVS-Studio: Assignment to Variable without Use (CWE-563) (1) 54. Mar 13 bugzilla-noreply@freebsd.o [Bug 217749] sys/netinet/libalias/alias_proxy.c: PVS-Studio: Assignment to Variable without Use (CWE-563) (2) 55. Mar 13 bugzilla-noreply@freebsd.o [Bug 217749] sys/netinet/libalias/alias_proxy.c: PVS-Studio: Assignment to Variable without Use (CWE-563) (2) 56. Mar 13 bugzilla-noreply@freebsd.o [Bug 217749] sys/netinet/libalias/alias_proxy.c: PVS-Studio: Assignment to Variable without Use (CWE-563) (2) 57. Mar 15 bugzilla-noreply@freebsd.o [Bug 217782] sys/dev/bhnd/cores/pmu/bhnd_pmu_subr.c: PVS-Studio: Assignment to Variable without Use (CWE-563) (3) 58. Mar 15 bugzilla-noreply@freebsd.o [Bug 217782] sys/dev/bhnd/cores/pmu/bhnd_pmu_subr.c: PVS-Studio: Assignment to Variable without Use (CWE-563) (3) 59. Mar 15 bugzilla-noreply@freebsd.o [Bug 217784] sys/dev/wi/if_wi_pci.c: PVS-Studio: Dead Code (CWE-561) 60. Mar 15 bugzilla-noreply@freebsd.o [Bug 217784] sys/dev/wi/if_wi_pci.c: PVS-Studio: Dead Code (CWE-561)
61. Mar 15 bugzilla-noreply@freebsd.o [Bug 217784] sys/dev/wi/if_wi_pci.c: PVS-Studio: Dead Code (CWE-561) 62. Mar 18 bugzilla-noreply@freebsd.o [Bug 217784] sys/dev/wi/if_wi_pci.c: PVS-Studio: Dead Code (CWE-561) 63. Mar 17 bugzilla-noreply@freebsd.o [Bug 217862] ixgbe broken after 315333 64. Mar 17 bugzilla-noreply@freebsd.o [Bug 217862] ixgbe broken after 315333 65. Mar 17 bugzilla-noreply@freebsd.o [Bug 217871] SLAAC on a newly created epair sometimes fails to add routes 66. Mar 17 bugzilla-noreply@freebsd.o [Bug 217871] SLAAC on a newly created epair sometimes fails to add routes 67. Mar 17 bugzilla-noreply@freebsd.o [Bug 217871] SLAAC on a newly created epair sometimes fails to add routes 68. Mar 17 asomers (Alan Somers) [Differential] D9451: Constrain IPv6 interface routes to each FIB 69. Mar 17 Harry Schmalzbauer [panic] netmap(4) and if_lagg(4) 70. Mar 17 Vincenzo Maffione Re: [panic] netmap(4) and if_lagg(4) 71. Mar 17 Harry Schmalzbauer Re: [panic] netmap(4) and if_lagg(4) 72. Mar 17 Vincenzo Maffione Re: [panic] netmap(4) and if_lagg(4) 73. Mar 12 Sepherosa Ziehau Re: about that DFBSD performance test 74. Mar 17 Harry Schmalzbauer Are ./valte-ctl and ./bridge friends or competitors? 75. Mar 17 Harry Schmalzbauer Re: Are ./valte-ctl and ./bridge friends or competitors? 76. Mar 17 Vincenzo Maffione Re: Are ./valte-ctl and ./bridge friends or competitors? 77. Mar 17 Harry Schmalzbauer Re: Are ./valte-ctl and ./bridge friends or competitors? 78. Mar 17 Olivier Cochard-Labbé Re: Are ./valte-ctl and ./bridge friends or competitors? 79. Mar 18 Vincenzo Maffione Re: Are ./valte-ctl and ./bridge friends or competitors? 80. Mar 18 Vincenzo Maffione Re: Are ./valte-ctl and ./bridge friends or competitors?
81. Mar 12 John Jasen bad throughput performance on multiple systems: Re: Fwd: Re: Disappointing packets-per-second performance results on a Dell,PE R530 82. Mar 12 Slawa Olhovchenkov Re: bad throughput performance on multiple systems: Re: Fwd: Re: Disappointing packets-per-second performance results on a Dell,PE R530 83. Mar 13 John Jasen Re: bad throughput performance on multiple systems: Re: Fwd: Re: Disappointing packets-per-second performance results on a Dell,PE R530 84. Mar 13 Navdeep Parhar Re: bad throughput performance on multiple systems: Re: Fwd: Re: Disappointing packets-per-second performance results on a Dell,PE R530 85. Mar 13 John Jasen Re: bad throughput performance on multiple systems: Re: Fwd: Re: Disappointing packets-per-second performance results on a Dell,PE R530 86. Mar 13 John Jasen Re: bad throughput performance on multiple systems: Re: Fwd: Re: Disappointing packets-per-second performance results on a Dell,PE R530 87. Mar 13 Navdeep Parhar Re: bad throughput performance on multiple systems: Re: Fwd: Re: Disappointing packets-per-second performance results on a Dell,PE R530 88. Mar 16 John Jasen Re: bad throughput performance on multiple systems: Re: Fwd: Re: Disappointing packets-per-second performance results on a Dell,PE R530 89. Mar 17 Slawa Olhovchenkov Re: bad throughput performance on multiple systems: Re: Fwd: Re: Disappointing packets-per-second performance results on a Dell,PE R530 90. Mar 17 John Jasen Re: bad throughput performance on multiple systems: Re: Fwd: Re: Disappointing packets-per-second performance results on a Dell,PE R530 91. Mar 17 Navdeep Parhar Re: bad throughput performance on multiple systems: Re: Fwd: Re: Disappointing packets-per-second performance results on a Dell,PE R530 92. Mar 17 Slawa Olhovchenkov Re: bad throughput performance on multiple systems: Re: Fwd: Re: Disappointing packets-per-second performance results on a Dell,PE R530 93. Mar 18 John Jasen Re: bad throughput performance on multiple systems: Re: Fwd: Re: Disappointing packets-per-second performance results on a Dell,PE R530 94. Mar 18 Navdeep Parhar Re: bad throughput performance on multiple systems: Re: Fwd: Re: Disappointing packets-per-second performance results on a Dell,PE R530 95. Mar 13 Ayaka Koshibe BPF departure handler and interface renaming 96. Mar 18 Quartz Filtering multicast and/or 6to4? 97. Mar 16 Harry Schmalzbauer if_igb(4) VLAN(4) and [RT]XCSUM_IPV6, TSO6 98. Mar 12 Ermal Luçi Re: ipsec with ipfw 99. Mar 12 Slawa Olhovchenkov Re: ipsec with ipfw 100. Mar 13 Andrey V. Elsukov Re: ipsec with ipfw
101. Mar 13 Hooman Fazaeli Re: ipsec with ipfw 102. Mar 14 Andrey V. Elsukov LLE reference leak in the L2 cache 103. Mar 14 Mike Karels Re: LLE reference leak in the L2 cache 104. Mar 14 Andrey V. Elsukov Re: LLE reference leak in the L2 cache 105. Mar 15 Mike Karels Re: LLE reference leak in the L2 cache 106. Mar 13 Mike Tancsa pf bug with tun interfaces ? 107. Mar 13 Mike Tancsa Re: pf bug with tun interfaces ? 108. Mar 15 Kristof Provost Re: pf bug with tun interfaces ? 109. Mar 15 Mike Tancsa Re: pf bug with tun interfaces ? 110. Mar 16 Kristof Provost Re: pf bug with tun interfaces ? 111. Mar 16 Ermal Luçi Re: pf bug with tun interfaces ? 112. Mar 16 Mike Tancsa Re: pf bug with tun interfaces ? 113. Mar 16 Ermal Luçi Re: pf bug with tun interfaces ? 114. Mar 12 bugzilla-noreply@FreeBSD.o Problem reports for freebsd-net@FreeBSD.org that need special attention 115. Mar 15 Bryan Drewery Re: r314708: panic: Assertion err == 0 failed at /usr/src/sys/net/iflib.c:2241 116. Mar 14 Reshad Patuck VNET kernel panic on remove renamed interfaces 117. Mar 14 Ayaka Koshibe Re: VNET kernel panic on remove renamed interfaces 118. Mar 15 Reshad Patuck Re: VNET kernel panic on remove renamed interfaces 119. Mar 17 Reshad Patuck Re: VNET kernel panic on remove renamed interfaces 120. Mar 12 Sepherosa Ziehau Re: Why is MSI-X support disabled on bce(4)?
121. Mar 12 Kevin Bowling Re: Why is MSI-X support disabled on bce(4)?
home | up | archive | sorted by: subject - author - date - reverse date