2025/freebsd-net/20250526.freebsd-net
Messages: 35, sorted by subject
|
Last page update: Sat Jan 3 13:11:46 UTC 2026
|
|
home | up | archive | sorted by: subject - author - date - reverse date
1. May 19 bugzilla-noreply@freebsd.o [Bug 254445] cloned_interfaces="bridge0" does not respect net.inet6.ip6.auto_linklocal 2. May 19 bugzilla-noreply@freebsd.o [Bug 254445] cloned_interfaces="bridge0" does not respect net.inet6.ip6.auto_linklocal 3. May 19 bugzilla-noreply@freebsd.o [Bug 254675] ICMP Unreach needfrag is broken at least since 13.0-RC4 4. May 19 bugzilla-noreply@freebsd.o [Bug 254675] ICMP Unreach needfrag is broken in 13.0-RC4 5. May 20 bugzilla-noreply@freebsd.o [Bug 262828] [carp] CARP arp replays with wrong src mac 6. May 23 bugzilla-noreply@freebsd.o [Bug 281938] Make sure max_len is not 0 before using it as modulo 7. May 23 bugzilla-noreply@freebsd.o [Bug 281938] Make sure max_len is not 0 before using it as modulo 8. May 23 bugzilla-noreply@freebsd.o [Bug 286631] TCP SACK: CWND set to 2 MSS after successful SACK recovery 9. May 23 bugzilla-noreply@freebsd.o [Bug 286689] igb nic flaps when tap added to bridge 10. May 23 bugzilla-noreply@freebsd.o [Bug 286720] Broadcom bnxt driver store_cfg bug fixed 11. May 23 bugzilla-noreply@freebsd.o [Bug 286759] Fatal trap 12: page fault while in kernel mode - Mellanox NIC on FreeBSD14.2 12. May 19 bugzilla-noreply@freebsd.o [Bug 286762] igc driver doesn't properly recognize link status when in down state 13. May 21 bugzilla-noreply@freebsd.o [Bug 286762] igc driver doesn't properly recognize link status when in down state 14. May 21 bugzilla-noreply@freebsd.o [Bug 286762] igc driver doesn't properly recognize link status when in down state [PATCH] 15. May 20 bugzilla-noreply@freebsd.o [Bug 286949] Race condition in ether_ifattach 16. May 19 Lexi Winter HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” 17. May 19 Paul Vixie HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” 18. May 19 Patrick M. Hausen Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” 19. May 19 Paul Vixie Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” 20. May 20 Lexi Winter Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument”
21. May 21 void Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” 22. May 21 Kristof Provost Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” 23. May 21 Kristof Provost Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” 24. May 22 Lexi Winter Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” 25. May 22 void Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” 26. May 22 void Re: HEADS UP: 15.0-CURRENT, change to bridge(4) might break some network configurations with “Invalid argument” 27. May 21 Lexi Winter net.link.bridge.member_ifaddrs has landed in stable/14 28. May 21 Warner Losh Re: net.link.bridge.member_ifaddrs has landed in stable/14 29. May 23 void Re: net.link.bridge.member_ifaddrs has landed in stable/14 30. May 23 Ronald Klop Re: net.link.bridge.member_ifaddrs has landed in stable/14 31. May 23 Peter Blok Re: net.link.bridge.member_ifaddrs has landed in stable/14 32. May 23 void Re: net.link.bridge.member_ifaddrs has landed in stable/14 33. May 23 ivy@FreeBSD.org Re: net.link.bridge.member_ifaddrs has landed in stable/14 34. May 24 void Re: net.link.bridge.member_ifaddrs has landed in stable/14 35. May 25 bugzilla-noreply@FreeBSD.o Problem reports for net@FreeBSD.org that need special attention
home | up | archive | sorted by: subject - author - date - reverse date