Reworking the Network Configuration Libraries idea for laptop/desktop use

Hello everyone,

I’m a student preparing a GSoC proposal for FreeBSD, and I would like to revisit the older “Network Configuration Libraries” idea which I encountered while looking for ideas list page in the wiki, in a way that better matches current laptop and desktop priorities.

After looking into the original idea, it seems to me that some of the lower-level routing work has already been implemented, so I do not want to simply repeat that scope. Instead, I would like to revise the proposal toward a more practical desktop/laptop networking direction, aligned with the Laptop and Desktop Working Group goals of improving the usability of FreeBSD on daily-driver systems.

My current thinking is to focus on network configuration libraries and tools that help with common user-facing workflows, such as:

Switching between Wi-Fi networks and saved profiles.

Scanning and connecting/disconnecting from wireless networks.

Handling IP, gateway, MAC, and DNS configuration in a consistent way.

Supporting temporary network setup for tethering, VMs, and jails where appropriate

At some extend creating ease of use for configuration of VPN or proxy services

Before I write the full proposal, I would appreciate any feedback on the right scope. In particular:

Would a project centered on a small network configuration library plus a simple CLI/TUI be considered useful?

Would it be better to focus only on wireless profile management first, with VM/jail networking as a stretch goal?

Is there a preferred approach or existing work I should build on to avoid duplicating effort?

My goal is to contribute something genuinely useful to FreeBSD laptop and desktop users by working on the daily cases I encounter while I am using FreeBSD as a daily driver, while keeping the project realistic for GSoC and aligned with the current LDWG direction.

Thanks from now for your time and feedback.

Best regards,Berke Nar