Amprgw filters at the per-host (/32) level. Each host which is to receive
traffic from the Internet into AMPRNet must individually be listed in
the permissions file, which is built from the
AMPR.ORG DNS 'A' records.
The only host on your subnet which is listed (and therefore is the only
one authorized) is 44.153.164.5. If you want .6 or other hosts on your
subnet to be able to communicate with the Internet, you will need to
have your local coordinator add them to the DNS for you. Or I can do it.
- Brian
On Fri, Jun 09, 2017 at 08:44:38PM -0300, Gustavo Conrad wrote:
> Hi All, I'm new to the list and I find it very interesting.
>
> Let me introduce myself: ham since 1996, former call LU8WFY, primary
> interests CW, HF and later digital communications. Devoted to linux for more
> than ten years. Work in telecommunications since 2001.
>
> Now the problem: I got the assignment 44.153.164.4/30
> <http://44.153.164.4/30> from the local coordinator (LU7ABF) and (after some
> NAT fighting with my Cisco 877 router) I was able to put it online from
> dynamic IP. From the gateway IP 44.153.164.5 there's no problem pinging to
> 44/8 and to the outside world. Ping from outside to .5 is also ok. But when
> I ping from outside to 44.153.164.6 there's no response. The strange thing
> is that, using tcpdump, I see no packets coming into the gateway from amprgw
> (of course they do show when the ping is to .5). Further testing from 44
> net (using
yo2tm.ampr.org network tools) showed that from 44 to my host
> everything works as expected.
> I guess that there's some routing problem between outside world and 44
> net. I don't know in which way the routes from 44 are propagated to the
> rest of the internet.
>
> Maybe I´m missing something but I can't find the problem.
>
> Any help will be appreciated.
>
> Thanks!
>
> 73
>
> Gustavo
> LU7WA
>