Re: epair(4)

From: Marek Zarychta <zarychtam_at_plan-b.pwste.edu.pl>
Date: Thu, 15 May 2025 19:32:40 UTC
W dniu 15.05.2025 o 20:59, Cy Schubert pisze:
> In message <20250515162552.9209B20E@slippy.cwsent.com>, Cy Schubert writes:
>> Over the last couple of days epair(4) fails to set up when an IP address is
>> specified.
>>
>> bob# service jail onestart test2
>> Starting jails: cannot start jail  "test2":
>> epair0a
>> ifconfig: ioctl (SIOCAIFADDR): Invalid argument
>> jail: test2: /sbin/ifconfig epair0a inet 10.1.1.70 netmask 0xffffff00 up:
>> failed
>> .
>> bob# ifconfig epair0a inet 10.1.1.70 netmask 0xffffff00
>> ifconfig: ioctl (SIOCAIFADDR): Invalid argument
>> bob# ifconfig epair0a inet up
>> bob#
>>
>>
>> -- 
>> Cheers,
>> Cy Schubert <Cy.Schubert@cschubert.com>
>> FreeBSD UNIX:  <cy@FreeBSD.org>   Web:  https://FreeBSD.org
>> NTP:           <cy@nwtime.org>    Web:  https://nwtime.org
>>
>> 			e^(i*pi)+1=0
>>
>>
>>
> This regression is caused by b61850c4e6f6.
>
>
Yes, it requires at least head up, similar to old one, known from fibs :

WARNING: Configuring address on bridge(4) member has been turned off by 
default. Consider tuning  net.link.bridge.member_ifaddrs if needed.

Looking at my setups used on stable/14 a lot of them will be broken 
after upgrade to stable/15 by the end of this year.

-- 
Marek Zarychta