8 Jun
2017
8 Jun
'17
10:46 a.m.
Hi Lynwood,
Actually it would be possible to receive announcements from everywhere,
but the data collecting daemon only accepts announcement from 44 addresses
(route present or not).
I have done this because a few minutes after publishing the announcement
URLs, I had some spamming tentatives from public IPs and I would rather
keep the system clean.
On the other hand, if there is no way for announcements to arrive from a
44 address, that host is not a AMPR mesh gateway, since the mesh is not
working.
Marius
All,
I once again notice intermittent connection to AMPRNet for about 24
hours. When this happens:
- When I login into the /private page, I cannot see Encap.txt
- Each time, this is how I attempt to confirm I'm in the most recant Encap
- I'm not on Marius' map, and from my understanding of his OS (hi) he
will not receive packets if he doesn't have a route for me
I figure I'm not on Encap.txt. Can someone check?
Linux commands:
dynamic filter check:
ipset test ipipfilter 71.178.210.39
check route:
ip route get 44.60.44.0/24 from <your_AMPR_IP_on_router>
My encap file reads June 8, 00:20 UTC.
- Lynwood
KB3VWG
-rw-r--r-- 1 root root 31119 Jun 7 20:20
/etc/config/encap.txt
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net