Re: kern/57650

[Sverre Froyen <sfroyen%gmail.com@localhost>]

The following reply was made to PR kern/57650; it has been noted by GNATS.

From: Sverre Froyen <sfroyen%gmail.com@localhost>
To: "gnats-bugs%gnats.netbsd.org@localhost" <gnats-bugs%gnats.NetBSD.org@localhost>
Cc: 
Subject: Re: kern/57650
Date: Tue, 17 Oct 2023 11:48:45 -0600

 Thanks for fixing the locking bug! I can now modify the MTU on the =
 interface.
 
 There is still an issue with part 2 of the bug. Using this =
 ifconfig.lagg0 file:
 
 	!ifconfig wm0 up mtu 9000
 	!ifconfig wm1 up mtu 9000
 	create
 	laggproto lacp laggport wm0 laggport wm1 192.168.2.1 netmask =
 255.255.255.0
 	up
 
 returns the error message (as before):
 
 	exec_matches: invalid argument
 
 I suspect it has to do with the interface not being up when the driver =
 attempts to set the MTU.
 
 I can obviously work around it, but it is confusing, especially since =
 the man page states
 
 	The MTU of the first interface to be added is used as the lagg =
 MTU=