On 5/27/19 1:38 PM, Jack Craig wrote:
On Sun, May 26, 2019 at 10:17 PM Ed Greshko <ed.greshko(a)greshko.com
On 5/27/19 12:17 PM, Jack Craig wrote:
> i thought what i read was after nm brings up the vpn, only then is the default
> vpn created. more, its torn down first on shutdown.
> i'm thinking along this line, ...
I've never used that configuration setting.
Could you show your routes before vpn and after vpn activation?
the table didnt change. dorking with it did blow my default route out, so i will resume
in the am after rest
I find it odd that you don't show routes similar to a default route such as...
default via 22.214.171.124 dev tun0 proto static metric 50
and a specific route to the VPN server like
126.96.36.199 via 192.168.1.1 dev enp2s0 proto static metric 100
i expect what should happen is that after each interface comes up via NM a default route
is set to it
so eth0 up, default route to , say, 10.0.0./24 <http://10.0.0./24>
;, then vpn comes
default route is now pointed at the vpn.
and this process in reverse on shutdown...
Yes, but all the routing information needed by the client should be provided by the
server, in most cases.
Are you connecting to a commercial openvpn service? Or, are you setting up your own
afaik, openvpn is an open source pkg that i built from src code to my goal of anonymous
the consumer version found here, ...
I didn't phrase my question very well.
I was asking if you have created your own OpenVPN server and you're trying to use it,
you're connection to a VPN service like NordVPN or Ironsocket or another service
provider. I'm connecting to Ironsocket.
I get the feeling, based on what you've said, your configuring your own OpenVPN
If that is the case, you may want to show folks your configuration. It seems something
may be missing.
Right: I dislike the default color scheme Wrong: What idiot picked the default color