2019/freebsd-net/20190929.freebsd-net
Messages: 101, sorted by subject
|
Last update: Mon Feb 13 14:19:07 UTC 2023
|
|
home | up | archive sorted by: subject | author | date | reverse date
1. Sep 23 oldbout@aliyun.com =?UTF-8?B?5Luj56CU57yl?= 2. Sep 27 midnightdreamer@aliyun.com =?UTF-8?B?5YWs5Y+45pW05aWX6LWE5paZ5Ye65ZSu77yM5bim5a+55YWs6LSm5oi36ZO2?= =?UTF-8?B 3. Sep 25 bugzilla-noreply@freebsd.o [Bug 211106] [net][fib][loopback][route] loopback route added only to interface fi 4. Sep 23 bugzilla-noreply@freebsd.o [Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade 5. Sep 23 bugzilla-noreply@freebsd.o [Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade 6. Sep 23 bugzilla-noreply@freebsd.o [Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade 7. Sep 26 bugzilla-noreply@freebsd.o [Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade 8. Sep 26 bugzilla-noreply@freebsd.o [Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade 9. Sep 26 bugzilla-noreply@freebsd.o [Bug 233952] if_jme: Does not send/receive packets after 11.2 to 12.0 upgrade 10. Sep 23 bugzilla-noreply@freebsd.o [Bug 236724] igb(4): Interfaces fail to switch active to inactive state 11. Sep 24 bugzilla-noreply@freebsd.o [Bug 236724] igb(4): Interfaces fail to switch active to inactive state 12. Sep 25 bugzilla-noreply@freebsd.o [Bug 236724] igb(4): Interfaces fail to switch active to inactive state 13. Sep 25 bugzilla-noreply@freebsd.o [Bug 236724] igb(4): Interfaces fail to switch active to inactive state 14. Sep 26 bugzilla-noreply@freebsd.o [Bug 236724] igb(4): Interfaces fail to switch active to inactive state 15. Sep 26 bugzilla-noreply@freebsd.o [Bug 236724] igb(4): Interfaces fail to switch active to inactive state 16. Sep 24 bugzilla-noreply@freebsd.o [Bug 239118] iflib: Panic in ether_output_frame on ESXi 17. Sep 28 bugzilla-noreply@freebsd.o [Bug 239118] iflib: Panic in ether_output_frame on ESXi 18. Sep 25 bugzilla-noreply@freebsd.o [Bug 239216] Problem with ix(4) driver on systems with two Intel X520 cards 19. Sep 24 bugzilla-noreply@freebsd.o [Bug 239240] igb: TX(2) desc avail = 1024, pidx = 0 messages appear when the netwo 20. Sep 24 bugzilla-noreply@freebsd.o [Bug 239240] igb: TX(2) desc avail = 1024, pidx = 0 messages appear when the netwo
21. Sep 24 bugzilla-noreply@freebsd.o [Bug 239240] igb: TX(2) desc avail = 1024, pidx = 0 messages appear when the netwo 22. Sep 24 bugzilla-noreply@freebsd.o [Bug 239240] igb: TX(2) desc avail = 1024, pidx = 0 messages appear when the netwo 23. Sep 24 bugzilla-noreply@freebsd.o [Bug 239240] igb: TX(2) desc avail = 1024, pidx = 0 messages appear when the netwo 24. Sep 25 bugzilla-noreply@freebsd.o [Bug 239240] igb: TX(2) desc avail = 1024, pidx = 0 messages appear when the netwo 25. Sep 25 bugzilla-noreply@freebsd.o [Bug 239240] igb: TX(2) desc avail = 1024, pidx = 0 messages appear when the netwo 26. Sep 27 bugzilla-noreply@freebsd.o [Bug 239240] igb: TX(2) desc avail = 1024, pidx = 0 messages appear when the netwo 27. Sep 24 bugzilla-noreply@freebsd.o [Bug 239704] ixgbe(4): Only one queue (of eight) enabled on 12.0-RELEASE (ProLiant 28. Sep 26 bugzilla-noreply@freebsd.o [Bug 239704] ixgbe(4): Only one queue (of eight) enabled on 12.0-RELEASE (ProLiant 29. Sep 24 bugzilla-noreply@freebsd.o [Bug 240610] iflib: Panic with INVARIANTS: general protection fault when kldunload 30. Sep 24 bugzilla-noreply@freebsd.o [Bug 240610] iflib: Panic with INVARIANTS: general protection fault when kldunload 31. Sep 24 bugzilla-noreply@freebsd.o [Bug 240610] iflib: Panic with INVARIANTS: general protection fault when kldunload 32. Sep 24 bugzilla-noreply@freebsd.o [Bug 240610] iflib: Panic with INVARIANTS: general protection fault when kldunload 33. Sep 24 bugzilla-noreply@freebsd.o [Bug 240658] iflib: if_igb(4) and some if_em(4) devices don't recognize/report car 34. Sep 25 bugzilla-noreply@freebsd.o [Bug 240658] iflib: if_igb(4) and some if_em(4) devices don't recognize/report car 35. Sep 25 bugzilla-noreply@freebsd.o [Bug 240658] iflib: if_igb(4) and some if_em(4) devices don't recognize/report car 36. Sep 25 bugzilla-noreply@freebsd.o [Bug 240658] iflib: if_igb(4) and some if_em(4) devices don't recognize/report car 37. Sep 25 bugzilla-noreply@freebsd.o [Bug 240658] iflib: if_igb(4) and some if_em(4) devices don't recognize/report car 38. Sep 25 bugzilla-noreply@freebsd.o [Bug 240658] iflib: if_igb(4) and some if_em(4) devices don't recognize/report car 39. Sep 25 bugzilla-noreply@freebsd.o [Bug 240658] iflib: if_igb(4) and some if_em(4) devices don't recognize/report car 40. Sep 25 bugzilla-noreply@freebsd.o [Bug 240658] iflib: if_igb(4) and some if_em(4) devices don't recognize/report car
41. Sep 26 bugzilla-noreply@freebsd.o [Bug 240658] iflib: if_igb(4) and some if_em(4) devices don't recognize/report car 42. Sep 26 bugzilla-noreply@freebsd.o [Bug 240658] iflib: if_igb(4) and some if_em(4) devices don't recognize/report car 43. Sep 22 bugzilla-noreply@freebsd.o [Bug 240685] netgraph/ng_vlan_rotate: IEEE 802.1ad VLAN manipulation netgraph node 44. Sep 22 bugzilla-noreply@freebsd.o [Bug 240685] netgraph/ng_vlan_rotate: IEEE 802.1ad VLAN manipulation netgraph node 45. Sep 23 bugzilla-noreply@freebsd.o [Bug 240685] netgraph/ng_vlan_rotate: IEEE 802.1ad VLAN manipulation netgraph node 46. Sep 23 bugzilla-noreply@freebsd.o [Bug 240685] netgraph/ng_vlan_rotate: IEEE 802.1ad VLAN manipulation netgraph node 47. Sep 23 bugzilla-noreply@freebsd.o [Bug 240685] netgraph/ng_vlan_rotate: IEEE 802.1ad VLAN manipulation netgraph node 48. Sep 24 bugzilla-noreply@freebsd.o [Bug 240787] netgraph/ng_bridge: Replace NG_BRIDGE_MAX_LINKS with auto-incrementin 49. Sep 24 bugzilla-noreply@freebsd.o [Bug 240787] netgraph/ng_bridge: Replace NG_BRIDGE_MAX_LINKS with auto-incrementin 50. Sep 24 bugzilla-noreply@freebsd.o [Bug 240787] netgraph/ng_bridge: Replace NG_BRIDGE_MAX_LINKS with auto-incrementin 51. Sep 26 bugzilla-noreply@freebsd.o [Bug 240787] netgraph/ng_bridge: Replace NG_BRIDGE_MAX_LINKS with auto-incrementin 52. Sep 26 bugzilla-noreply@freebsd.o [Bug 240787] netgraph/ng_bridge: Replace NG_BRIDGE_MAX_LINKS with auto-incrementin 53. Sep 26 bugzilla-noreply@freebsd.o [Bug 240787] netgraph/ng_bridge: Replace NG_BRIDGE_MAX_LINKS with auto-incrementin 54. Sep 27 bugzilla-noreply@freebsd.o [Bug 240787] netgraph/ng_bridge: Replace NG_BRIDGE_MAX_LINKS with auto-incrementin 55. Sep 25 bugzilla-noreply@freebsd.o [Bug 240818] igb drivers: vlanhwfilter feature generate link UP/DOWN for each new 56. Sep 26 bugzilla-noreply@freebsd.o [Bug 240818] igb drivers: vlanhwfilter feature generate link UP/DOWN for each new 57. Sep 26 bugzilla-noreply@freebsd.o [Bug 240818] igb drivers: vlanhwfilter feature generate link UP/DOWN for each new 58. Sep 26 bugzilla-noreply@freebsd.o [Bug 240818] igb drivers: vlanhwfilter feature generate link UP/DOWN for each new 59. Sep 26 bugzilla-noreply@freebsd.o [Bug 240825] Possible race between vlan interfaces and lagg(4) w/ em0/em1 post-EPO 60. Sep 26 bugzilla-noreply@freebsd.o [Bug 240825] Possible race between vlan interfaces and lagg(4) w/ em0/em1 post-EPO
61. Sep 26 bugzilla-noreply@freebsd.o [Bug 240825] Possible race between vlan interfaces and lagg(4) w/ em0/em1 post-EPO 62. Sep 26 bugzilla-noreply@freebsd.o [Bug 240825] Vlan interfaces does not work on lagg from em0, em1 63. Sep 26 bugzilla-noreply@freebsd.o [Bug 240825] Vlan interfaces does not work on lagg from em0, em1 64. Sep 23 vm finance Re: BBR patch on latest src, build failed. 65. Sep 23 hshh Re: BBR patch on latest src, build failed. 66. Sep 25 vm finance Re: BBR patches? 67. Sep 25 Randall Stewart Re: BBR patches? 68. Sep 25 Michael Tuexen Re: BBR patches? 69. Sep 25 Randall Stewart Re: BBR patches? 70. Sep 26 vm finance Re: BBR patches? 71. Sep 26 Randall Stewart Re: BBR patches? 72. Sep 26 Victor Gamov bridged vlan down but traffic still exists 73. Sep 24 Andriy Gapon dummynet: bandwidth is limited to 2 Gbit/s ? 74. Sep 24 Eugene Grosbein Re: dummynet: bandwidth is limited to 2 Gbit/s ? 75. Sep 24 Rodney W. Grimes Re: dummynet: bandwidth is limited to 2 Gbit/s ? 76. Sep 25 Eugene Grosbein Re: dummynet: bandwidth is limited to 2 Gbit/s ? 77. Sep 25 John Hay Re: dummynet: bandwidth is limited to 2 Gbit/s ? 78. Sep 25 Andriy Gapon Re: dummynet: bandwidth is limited to 2 Gbit/s ? 79. Sep 25 Andrey V. Elsukov Re: dummynet: bandwidth is limited to 2 Gbit/s ? 80. Sep 25 Eugene Grosbein Re: dummynet: bandwidth is limited to 2 Gbit/s ?
81. Sep 25 Andrey V. Elsukov Re: dummynet: bandwidth is limited to 2 Gbit/s ? 82. Sep 25 Luigi Rizzo Re: dummynet: bandwidth is limited to 2 Gbit/s ? 83. Sep 25 Eugene Grosbein Re: dummynet: bandwidth is limited to 2 Gbit/s ? 84. Sep 25 Michael Sierchio Re: dummynet: bandwidth is limited to 2 Gbit/s ? 85. Sep 22 Hiroki Sato Re: Link flap for setting ether/MAC address 86. Sep 27 Alexander N. Lunev no network between jails and host with VNET on same interface 87. Sep 27 alexander lunev Re: no network between jails and host with VNET on same interface 88. Sep 22 bugzilla-noreply@FreeBSD.o Problem reports for net@FreeBSD.org that need special attention 89. Sep 24 Mihir Luthra rpc.statd already ipv6 clean? 90. Sep 24 Hiroki Sato Re: rpc.statd already ipv6 clean? 91. Sep 25 Mihir Luthra Re: rpc.statd already ipv6 clean? 92. Sep 25 Hiroki Sato Re: rpc.statd already ipv6 clean? 93. Sep 26 Mihir Luthra Re: rpc.statd already ipv6 clean? 94. Sep 26 Rick Macklem Re: rpc.statd already ipv6 clean? 95. Sep 26 Bjoern A. Zeeb Re: rpc.statd already ipv6 clean? 96. Sep 27 Hiroki Sato Re: rpc.statd already ipv6 clean? 97. Sep 27 Mihir Luthra Re: rpc.statd already ipv6 clean? 98. Sep 27 Mihir Luthra Re: rpc.statd already ipv6 clean? 99. Sep 27 Rick Macklem Re: rpc.statd already ipv6 clean? 100. Sep 27 Bjoern A. Zeeb Re: rpc.statd already ipv6 clean?
101. Sep 28 Rick Macklem Re: rpc.statd already ipv6 clean?
home | up | archive sorted by: subject | author | date | reverse date