[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
   Assignee|n...@freebsd.org |eu...@freebsd.org

--- Comment #3 from Graham Perrin  ---
^Triage: with closure, there should be assignment to a person.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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,
   ||zarych...@plan-b.pwste.edu.
   ||pl

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[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
 Status|Open|In Progress

--- Comment #6 from Benedict Reuschling  ---
I just opened a review for it here:
https://reviews.freebsd.org/D37096

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[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.com

--- Comment #7 from Graham Perrin (non-committing)  ---
Re: , the 'patch' keyword (above)
can/should be removed. 

Bug 227147 will gain a hint of: 

* how to seek bug reports where an attachment is definitely a patch. 

bcr@ would you like to make yourself the assignee? Also, add the URL of the
review to the See also: field. 

Thanks.


(In reply to O. Hartmann from comment #5)

This Bugzilla includes more than a thousand non-resolved reports that use the
(deprecated) patch keyword. For each such report that is relatively old, there
might be any number of reasons for lack of progress. 

I think, it'll be useful to discuss generally – without singling out this bug
206165 – can I suggest the freebsd-questions mailing list? Or IRC, if you
prefer: aim for the #bugs channel. 

Thanks.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[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 the bug.

[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 the CC list for the bug.

[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 obsolete releases.

Status  |Bug Id | Description
+---+---
In Progress |221146 | [ixgbe] Problem with second laggport  
New |204438 | setsockopt() handling of kern.ipc.maxsockbuf limi 
New |213410 | [carp] service netif restart causes hang only whe 
Open|  7556 | ppp: sl_compress_init() will fail if called anyth 
Open|193452 | Dell PowerEdge 210 II -- Kernel panic bce (broadc 
Open|202510 | [CARP] advertisements sourced from CARP IP cause  
Open|207261 | netmap: Doesn't do TX sync with kqueue
Open|73 | igb(4): Kernel panic (fatal trap 12) due to netwo 
Open|225438 | panic in6_unlink_ifa() due to race
Open|227720 | Kernel panic in ppp server
Open|236888 | ppp daemon: Allow MTU to be overridden for PPPoE  
Open|237072 | netgraph(4): performance issue [on HardenedBSD]?  
Open|237973 | pf: implement egress keyword to simplify rules ac 
Open|238324 | Add XG-C100C/AQtion AQC107 10GbE NIC driver   
Open|238707 | Lock order reversal: rtentry vs "nd6 list"
Open|240944 | em(4): Crash with Intel 82571EB NIC with AMD Pile 
Open|241106 | tun/ppp: panic: vm_fault: fault on nofault entry  
Open|241162 | Panic in closefp() triggered by nginx (uwsgi with 
Open|241191 | route flush panic with RADIX_MPATH
Open|243463 | ix0: Watchdog timeout 
Open|247111 | pxeboot very slow with i219LM 
Open|257709 | netinet6: Set net.inet6.icmp6.nodeinfo default to 
Open|118111 | rc: network.subr Add MAC address based interface  

23 problems total for which you should take action.

[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 
> same 
> vlan untagged.

Is this a layer 2 switch or layer 3 one ?

>I can ping them from an external machine through the router/gateway but the 
>nodes 
> can't ping each others using a public IPv6 /64. Pings using local-link work.
>  `ndp -a` only return local ping-links, the gateway address and address of 
> the current node. 

Do you mean an external machine can ping and have responses from the gateway,
but no responses from the nodes?
and also the nodes can't ping each others ?

Is the router connected with the switch(mikrotik) or the switch it self is the
gateway ?

And can you try pinging IPv6 link-local addresses to each others (although it
should not matter)?

Can you share some tcpdump captures while pinging?


While I'd suggest you connect two of the three nodes with twisted pair and this
is a
minimal setup to narrow down the problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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?docLocale=en_US&docId=a00035643en_us

> See this thread on th emailing-list for the details:
> https://lists.freebsd.org/archives/freebsd-net/2022-August/002294.html

Sorry to the noise, I did not look through the mailing list before the reply.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[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), and see if it works.

On node1 and node2, ifconfig ql0 mtu 4000, then ping link-local address from
node1 to node2.


Some glue in the driver's source code:

```
case SIOCSIFMTU:
QL_DPRINT4(ha, "SIOCSIFMTU (0x%lx)\n", cmd);

if (ifr->ifr_mtu > QLNX_MAX_MTU) {
ret = EINVAL;
} else {
QLNX_LOCK(ha);
ifp->if_mtu = ifr->ifr_mtu;
ha->max_frame_size =
ifp->if_mtu + ETHER_HDR_LEN + ETHER_CRC_LEN;
if (ifp->if_drv_flags & IFF_DRV_RUNNING) {
qlnx_init_locked(ha);
}

QLNX_UNLOCK(ha);
}

break;
```

-- 
You are receiving this mail because:
You are the assignee for the bug.