[Bug 246706] [netgraph] kernel panic due to corrupted memory

2022-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=246706 Graham Perrin changed: What|Removed |Added CC||grahamper...@freebsd.org

[Bug 206165] resolv.conf(5) is missing documentation on options

2022-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206165 Marek Zarychta changed: What|Removed |Added CC||n...@freebsd.org,

[Bug 206165] resolv.conf(5) is missing documentation on options

2022-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206165 Benedict Reuschling changed: What|Removed |Added CC||b...@freebsd.org

[Bug 206165] resolv.conf(5) is missing documentation on options

2022-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206165 Graham Perrin (non-committing) changed: What|Removed |Added CC||grahamper...@gmail

[Bug 206165] resolv.conf(5) is missing documentation on options

2022-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206165 --- Comment #8 from Graham Perrin (non-committing) --- > … add the URL of the review to the See also: field. … For clarity, I mean: * your D37096 * not my D37086 -- You are receiving this mail because: You are on the CC list for th

[Bug 206165] resolv.conf(5) is missing documentation on options

2022-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206165 --- Comment #9 from Graham Perrin (non-committing) --- Re: comment #7 > aim for the #bugs channel. Correcting myself: the #freebsd-bugs channel. Apologies for the noise. -- You are receiving this mail because: You are on

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #3 from benoitc --- any news ? -- You are receiving this mail because: You are the assignee for the bug.

Problem reports for n...@freebsd.org that need special attention

2022-10-23 Thread bugzilla-noreply
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and ob

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #4 from Zhenlei Huang --- (In reply to benoitc from comment #0) >I have setup 3 nodes on a fresh Freebsd 13.1-RELEASE-p1. They have the same >gateway > and IPS are in same /64. All 3 nodes are on the same switch (mikrotik) and

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #5 from Zhenlei Huang --- > Pings start to work when the interface is put in promiscuous mode or an IPV4 > address is set. > The card is an HPE Eth 10/25Gb 2p 621SFP28 Adptr: > https://support.hpe.com/hpesc/public/docDisplay?

[Bug 265857] qlnxe: no IPV6 pings between nodes on the same switch until an IPv4 address is set

2022-10-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=265857 --- Comment #6 from Zhenlei Huang --- (In reply to benoitc from comment #1) I'm not sure whether the interface is not properly initialized or not, but you can try to change the MTU (maximum is 9000 as defined in the driver's source code),