Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 24 Jan 2025 13:46:37 +0300
From:      Anthony Pankov <anthony.pankov@yahoo.com>
To:        Mark Johnston <markj@freebsd.org>, Jim Thompson <jim@netgate.com>
Cc:        Daniel Lovasko <daniel.lovasko@gmail.com>, freebsd-hackers@freebsd.org
Subject:   Re: wg ifconfing control
Message-ID:  <1422038205.20250124134637@yahoo.com>
In-Reply-To: <Z5KJ0DVOm7F9V9IB@nuc>
References:  <CA%2BcSnN1UYpecBV145FAkdySM9otr%2BOPTfaWL6PUfj14VEinGVQ@mail.gmail.com>  <DA7CA979-415C-49E2-9A6B-FF91A245D5FA@netgate.com> <Z5KJ0DVOm7F9V9IB@nuc>

next in thread | previous in thread | raw e-mail | index | archive | help
Hello,

I fill that this suggestion raising from the sense of wg as a technology close to silver bullet for encrypted networking.

This is true while one has no pressure on networking communication.. In other case wg can be fully blocked easily. Then one have to go to another tool which is not incapsulated in ifconfig.

May be there is a need for separate tool for encrypted network interfaces and some options from ifconfig can migrate there.


Thursday, January 23, 2025, 9:26:24 PM, you wrote:

> On Wed, Jan 22, 2025 at 06:44:49PM -0600, Jim Thompson wrote:
>> We had it.
>> 
>> It was part of the original implementation that others decided to rip out because of politics. 
>> 
>> I doubt the powers that be (who tore it out) will put it back and will inhibit anyone else doing so. 

> There is no reason why we wouldn't want to have it, ignoring the
> question of whether ifconfig is already too bloated.  The main
> consideration would be to avoid modifying the if_wg ioctl interface,
> i.e., using the existing SIOCSWG and SIOCGWG ioctls, as wg(8) does.

>> I’m sure I have the code somewhere if you really want to try. 

> It can be easily fetched from the src repo:

> $ git checkout f187d6dfbf633665ba6740fe22742aec60ce02a2~ sbin/ifconfig/ifwg.c

>> Jim
>> 
>> 
>> > On Jan 22, 2025, at 5:41 PM, Daniel Lovasko <daniel.lovasko@gmail.com> wrote:
>> > 
>> > 
>> > Hello all,
>> > 
>> > I noticed that OpenBSD has added the ability to control the WireGuard interfaces through ifconfig. I am interested in implementing similar support in FreeBSD - is there anyone already working on this or perhaps the right mentor for adding this functionality? NetBSD has a similar functionality exposed through the wgconfig tool.
>> > 
>> > Short rationale: 1) not needing a package to do the setup, 2) procedural configuration, 3) ability to include all config in rc.conf, 4) consistency with other interface types (e.g. carp or gre).
>> > 
>> > Cheers,
>> > Daniel
>> 



-- 
Best regards,
Anthony




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1422038205.20250124134637>