On Mon, Mar 18, 2019 at 02:33:20PM +, Daniel P. Berrangé wrote:
> On Mon, Mar 18, 2019 at 02:23:12PM +, Tom Hughes wrote:
> > On 18/03/2019 14:07, Daniel P. Berrangé wrote:
> >
> > > Historically in Fedora the /dev/net/tun device always existed, even if
> > > there is no 'tun' module
On Mon, Mar 18, 2019 at 02:23:12PM +, Tom Hughes wrote:
> On 18/03/2019 14:07, Daniel P. Berrangé wrote:
>
> > Historically in Fedora the /dev/net/tun device always existed, even if
> > there is no 'tun' module currently loaded. Opening it then cause the
> > 'tun' kernel module to autoload
On Mon, Mar 18, 2019 at 2:23 PM Adam Williamson
wrote:
>
> On Mon, 2019-03-18 at 14:07 +, Daniel P. Berrangé wrote:
> > Historically in Fedora the /dev/net/tun device always existed, even if
> > there is no 'tun' module currently loaded. Opening it then cause the
> > 'tun' kernel module to
On 18/03/2019 14:07, Daniel P. Berrangé wrote:
Historically in Fedora the /dev/net/tun device always existed, even if
there is no 'tun' module currently loaded. Opening it then cause the
'tun' kernel module to autoload IIUC.
It doesn't just exist..
There is a systemd service
On Mon, 2019-03-18 at 14:07 +, Daniel P. Berrangé wrote:
> Historically in Fedora the /dev/net/tun device always existed, even if
> there is no 'tun' module currently loaded. Opening it then cause the
> 'tun' kernel module to autoload IIUC.
>
> In Fedora 31 rawhide this is no longer the case.