Re: disable the ability to change tun(4) mode from p2p to bcast and back again

2019-02-05 Thread Tim Kuijsten
On Tue, Feb 05, 2019 at 01:50:25PM +1000, David Gwynne wrote: On 4 Feb 2019, at 22:00, Tim Kuijsten wrote: On Mon, Feb 04, 2019 at 12:07:22PM +1000, David Gwynne wrote: Currently you can change a tun interface from being point to point to being a broadcast interface. Why? I'm using

Re: disable the ability to change tun(4) mode from p2p to bcast and back again

2019-02-04 Thread David Gwynne
> On 4 Feb 2019, at 22:00, Tim Kuijsten wrote: > > On Mon, Feb 04, 2019 at 12:07:22PM +1000, David Gwynne wrote: >> Currently you can change a tun interface from being point to point to >> being a broadcast interface. Why? > > I'm using broadcast mode in my own wireguard implementation

Re: disable the ability to change tun(4) mode from p2p to bcast and back again

2019-02-04 Thread Tim Kuijsten
On Mon, Feb 04, 2019 at 12:07:22PM +1000, David Gwynne wrote: Currently you can change a tun interface from being point to point to being a broadcast interface. Why? I'm using broadcast mode in my own wireguard implementation because there can be more than one peer on the network:

disable the ability to change tun(4) mode from p2p to bcast and back again

2019-02-03 Thread David Gwynne
Currently you can change a tun interface from being point to point to being a broadcast interface. Why? This cuts out the ability to change it. Note that the ioctl code is shared by tap, so it still has IFF_BROADCAST code that gets run, you should just not be able to change the flags, only read