3 Jun
2017
3 Jun
'17
6:55 p.m.
Sorry, what works as designed?
You have an daemon running on a tunnel, with a 44net address, creating
routes to other 44net entities.
You don't send traffic destined to those partners from a 44net address
with a 44net source.
Instead you use a public address to reach those nodes.
Ok. Now could you please explain why do you think the mesh network was
designed to work like that?
Because it wasn't. It was designed to forward traffic from 44 to 44
addresses via a tunnel mesh, not the way you use it.
Maybe it works as you want it, but not as designed.
Marius, YO2LOJ.
On 04.06.2017 01:21, lleachii--- via 44Net wrote:
Marius,
Cool...then it seems mine is working as designed. My system uses the
WAN for it's Tx/Rx. I'd have to mangle the packet, or have non 44
traffic masquerade to 44.0.0.0/8 from my location.
Since I often test accessibility on the Public Internet and AMPRNet
(and I don't want non-Hams at my QTH on the AMPRNet), I'll leave it
as-is. I can disable the discovery if it's an issue, it's OK with me.
- Lynwood
KB3VWG
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net