Re: [44net] now what is he next step

It depends. You might want to try checking your outgoing IP with a tool like 'telnet telnetmyip.com’ and see if your outgoing address is what you want it to be. We have a bunch of other IRLP services running on the same machine in my example, that must remain accessible with or without a tunnel. You can change outgoing source by using 44.135.59.1 as the gateway in the route table. From ifconfig... ens3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 149.28.163.64 netmask 255.255.254.0 broadcast 149.28.163.255 tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500 inet 44.136.33.1 netmask 255.255.255.255 destination 44.136.33.2 I can use either of those addresses as the outgoing source. root@server4:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 128.0.0.0 44.136.33.1 128.0.0.0 UG 0 0 0 ens3 0.0.0.0 44.136.33.1 128.0.0.0 UG 0 0 0 ens3 0.0.0.0 149.28.162.1 0.0.0.0 UG 0 0 0 ens3 As long as OpenVPN (server side) is running, outgoing traffic will use 44.136.33.1 as its source. If you stop OpenVPN, traffic will originate from the 149-network address. -Dave K9DC Indianapolis