> If the tun interface is always the same, just use firewall-cmd
> --zone=my_zone --add-interface=tun0
Hi Stuart,
Yea I can control the interface name but I can also pass it into the up script.
So this seemed to work well where as I also tried
firewall-cmd --permanent --change-zone=tun0
I have a system controlled openvpn configuration that creates a tun interface.
As the resulting tun interface falls under network manager, I created an up
script
That executes `/usr/bin/nmcli connection modify tun0 connection.zone my_zone`
where the actual interface name is passed in. This
Basically, you need an existing connection to the internet. Then you create
another shared connection that your other computers will access. When you
have both of those, then NM will start dnsmasq and everything and NAT the
shared connection to the main internet connection.
If you've already
Looking at a video Dan Williams posted to Redhat Magazine shows enabling
it is now as simple as creating the new connection in ad-hoc mode with ipv4
settings as 'available to other computers' but on my F12 system this doesn't
start dnsmasq etc. Is it still required to set this all up manually or
I need to add an auth-user-pass directive to my configuration, where does nm
store the config files for OpenVPN connections?
Thanks!
jlc
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
NM doesn't store OpenVPN config files--it actually constructs a
complete OpenVPN command line, with all the required options, every
time it starts the daemon.
Oh, that’s good to know...
You'll need to set your OpenVPN options via the NM GUI. I don't
remember off the top of my head whether
