7 Jun
2017
7 Jun
'17
12:45 p.m.
This is not the case. I'm running ubuntu server. The only client type
software I use on it is traceroute. It never occurred to me to specify
the interface and tell it to use eth2. Will try it along with Marius'
suggestion to put 44.98.63.6/8 on tunl0. I had 44.98.63.6/29 on it as a
test in the past and expected an IP conflict but the kernel never
complained. The 63.6/8 is new ground an I'm going to try it along with
specifying the interface when I do ping, mtr and traceroute.
--tom
N2XU / Tom Cardinal MSgt USAF(Ret) / BSCS / CASP, Security+
On 06/07/2017 04:28 AM, lleachii--- via 44Net wrote:
I also contacted Tom off-thread about it, as it seems
he may be trying
to run his machine as a desktop. If that's the case, his issue is that
he has to configure the user applications to use tunl0, or simply
virtualize the AMPR desktop and connect it's virtual-NIC to eth2.