4 Jun
2017
4 Jun
'17
12:06 p.m.
Lynwood,
I choose to go with using the tunnel IP since that code is already there
and it seems somehow legit to have an IP on that interface.
BTW, you could assign the same IP as your other interface with a netmask
of /32 to the tunnel. It should work without issues (but there could be
some firewall adjustment needed if you use interface names).
The map form the internet has issues independent from myself: It seems
gateway forwarding has some problems starting with Yesterday.
Let's wait for Monday.
On 04.06.2017 14:05, lleachii--- via 44Net wrote:
Marius,
Thanks again. Apologies for the use of the term "carrier", this is an
old phrase commonly used in FCC-land to mean "telephone company" or
"ISP".
Now...
- the map at http://yo2tm.ampr.org/ampr-map/ doesn't load for me on
the Public Internet (block of the WAN discovery packets?)
- connecting from 44.60.44.14 on AMPRNet, my dot disappeared
- I assigned an IP to tunl0 (44.60.44.254) and rebooted (I guess you
implemented the code on the -i argument)
- My dot now appears green
Use of an extra IP, but this is a valid use!
Thanks and 73,
- Lynwood
KB3VWG
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net