Re: networking in 14.1 release notes

2024-05-19 Thread John Hay
Hi Mike,

The ice(4) driver for Intel E800 Ethernet controllers has been in the tree
since May 2020, but it seems it was never added to the release notes. It
also does not have a man page. There is a bug report for the missing man
page:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=262892

Regards

John


On Sat, 18 May 2024 at 16:50, Mike Karels  wrote:

> I have no networking changes at all in the 14.1 release notes.  Is there
> anything that should be mentioned?  Feel free to reply to me individually.
>
> Thanks,
> Mike
>
>


Re: networking in 14.1 release notes

2024-05-19 Thread Mike Karels
On 19 May 2024, at 18:29, mike tancsa wrote:

> On 5/18/2024 10:49 AM, Mike Karels wrote:
>> I have no networking changes at all in the 14.1 release notes.  Is there
>> anything that should be mentioned?  Feel free to reply to me individually.
>>
> Not sure if appropriate or not, but when going to 13.x to 14.x, not all vlan 
> configs work now in rc.conf
>
> Both
>
> ifconfig_vlan2="192.168.1.51/24 vlandev igb1 vlan 2"
> ifconfig_vlan2="192.168.1.51/24 vlan 2 vlandev igb1"
>
> used to work on RELENG_13
>
> now only
>
> ifconfig_vlan2="192.168.1.51/24  vlan 2 vlandev igb1"
>
> is allowed.  Maybe a heads up in UPDATING ?

That sounds like an outright bug.  Looks like it was true in 14.0 as well.
Is there a bug report?  I couldn't find one.

btw, UPDATING is meant for upgrades from source.

Mike



Re: networking in 14.1 release notes

2024-05-19 Thread mike tancsa

On 5/18/2024 10:49 AM, Mike Karels wrote:

I have no networking changes at all in the 14.1 release notes.  Is there
anything that should be mentioned?  Feel free to reply to me individually.

Not sure if appropriate or not, but when going to 13.x to 14.x, not all 
vlan configs work now in rc.conf


Both

ifconfig_vlan2="192.168.1.51/24 vlandev igb1 vlan 2"
ifconfig_vlan2="192.168.1.51/24 vlan 2 vlandev igb1"

used to work on RELENG_13

now only

ifconfig_vlan2="192.168.1.51/24  vlan 2 vlandev igb1"

is allowed.  Maybe a heads up in UPDATING ?

    ---Mike





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

2024-05-19 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
+---+---
New |254445 | cloned_interfaces="bridge0" does not respect net. 
Open|166724 | if_re(4): watchdog timeout
Open|200836 | iovctl(8): Return descriptions in the returned sc 
Open|223824 | Panic in ng_base.c (netgraph) 
Open|230807 | if_alc(4): Driver not working for Killer Networki 
Open|232472 | ixgbe(4): SR-IOV passthru not working on Hyper-V  
Open|234073 | ixl(4): Host X710-DA2 drops connect starting bhyv 
Open|241106 | tun/ppp: panic: vm_fault: fault on nofault entry  
Open|257038 | em(4): Panic on HTTP traffic to or from jail thro 
Open|257286 | gateway with `ping -6 -e` is ignored  
Open|258623 | cxgbe(4): Slow routing performance: 2 numa domain 
Open|258850 | lagg(4): interface vanishes when both member inte 
Open|261866 | ixgbe(4): Resets media type -> autoselect after s 
Open|262024 | em(4): iflib handles bad packets incorrectly  
Open|262093 | ixl(4): RX packet errors on Intel X710 after 12.2 
Open|263568 | ix(4): SR-IOV connection lost after loading VM wi 
In Progress |118111 | rc: network.subr Add MAC address based interface  

17 problems total for which you should take action.