That being the case, we have a serious security problem. With AUTOADDMAP active, unknown non ham entities can? gain access to what's supposed to be a closed network. It's like opening the border. Anyone and everyone will be able to waltz in unhindered. That was recently experienced here when I made the mistake of activating AUTOADDMAP. What was reportedly some sort of European CB type node gained direct access to my system, and I to theirs. That is a non starter and will not end well if left uncontrolled.? It's advisable to NOT enable AUTOADDMAP.
My system seems to (mostly)? work just fine without it.
However, in consideration of the above, I wonder if not running AUTOADDMAP could be the reason for some AXIP/BBS partners using DDNS.NET not being accessible? I've lost at least two AXIP/BBS partners who utilize DDNS.NET in that they are simply not reachable. They may resolve to an IP address but just don't respond. There's no route.? It's been reported that they see me on their end, but there is no connectivity. A route to them never or rarely appears on my end. If a route appears, it is dead/unresponsive. They have my correct MAP information entered on their end, and I theirs. My solution was to dump DDNS.NET and replace it with DYNU/FREEDDNS.ORG. That works well for me. DDNS.NET must be eliminated on both ends just to be sure.
Best regards,
Gary, K7EK
Get
On 8/23/24 16:41, John G8BPQ wrote:
If you are talking about AUTOADDMAP that is not needed.
73, John
On 23/08/2024 20:52, Chuck Gelm wrote:
If I understand, this is necessary for AXUDP links to function as
intended.
73, Chuck
Hi, John:
Thanks.
I want to get you and Matt KB8UVN chatting about this.
When I commented my AUTOADDMAP, I lost all links.
When I re-enabled AUTOADDMAP I got my links back.
I will send you a copy of Matt's recent email to me
containing an explanation of the protocol in use.
vy73, Chuck
