28.10.2023 23:43, Roy Marples wrote:
> Using netlink rather than route on a modern FreeBSD kernel may allow you do
> do the same thing
> but install a kernel filter on the socket just to receive interface changes.
>
> That should match your requirements.
This scales bad still. More new vlans un
Using netlink rather than route on a modern FreeBSD kernel may allow you do do
the same thing but install a kernel filter on the socket just to receive
interface changes.That should match your requirements.Roy Marples On
Sat,28 Oct 2023 15:29:01 +0100 eu...@freebsd.org wrote 28.10.202
28.10.2023 23:21, Roy Marples wrote:
> What you would do is open a route socket, then call getifaddrs and then
> listen on the route socket for new interfaces.
>
> Then you can maintain a list of current vlans and take action accordingly.
I'd like to be able to make a couple of system calls onl
Hi!
Assume we run some FreeBSD-based broadband remote access server for PPPoE
(net/mpd5 for example).
The server has hundreds or thousands vlan interfaces and even more ngXXX
interfaces, one per user PPPoE session.
The server software may need to enable its PPPoE service for all newly created
