22 Mar
2021
22 Mar
'21
4:15 a.m.
Yep, I have the two instances however will have to look at the NAT to see if that is
disabled in OpenVPN as that is not something I looked at upon set up.
On 3/21/21, 10:26 AM, "44Net on behalf of Dave Gingrich via 44Net"
<44net-bounces+ai6bx=arrl.net(a)mailman.ampr.org on behalf of 44net(a)mailman.ampr.org>
wrote:
You need to add at least two outgoing static routes to force using 44.18.51.1 as your
source.
ip route add 0.0.0.0/1 via 44.18.51.1 dev ens3 (or whatever your interface is called
ip route add 128.0.0.0/1 via 44.18.51.1 dev ens3
The reason this works, is because the netmask (/1) is longer than the mask of the
default route (/0)
You can add post-up instructions to /etc/network/interfaces, so this is always in
place.
Also make sure you have disabled any NAT. Most OpenVPN instruction sets, assume you
want to NAT your clients to the server address. You do not want that.
--
Dave K9DC
Indianapolis
On Mar 21, 2021, at 12:25, Keith Kasin via 44Net
<44net(a)mailman.ampr.org> wrote:
I may be in somewhat of the same situation. I have my /24 subnet set up with VULTR and
have installed OpenVPN on my instance with them. I added by gateway address, 44.18.51.1 to
the NIC card on the VPS so can now ping that. The OpenVPN server assigns me an address
from the 44.18.51.x range however I cannot access other 44net services and others are not
seeing my OpenVPN assigned address when I am active. I note that when using
"whatismyip" I am still coming up with the VULTR public address rather than my
AMPR address or gateway address. Perhaps I have something configured wrong in OpenVPN
server or am I missing a series of DNS entries for each OpenVPN client instances?
Thank you,
Keith AI6BX
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net