First I wanted to mention I am glad to read Bjorn's message about
adding some content to the network.
Keeping in contact is key. Be that a coordinator or any host on the
amprnet. Seems every few months on here we are discussing how someone
is sending out random packets, and a straight forward way to get a
hold of people would be helpful.
Some time back it was brought up to have a whois server or something
like that. I bet I can guess the status of that.
As for everyone having an ampr.org email address, perhaps a forwarding
service like the arrl.net addresses? Then there is the possible spam
problem, and the fact that someone would need to set up such a
service.
Overall a lot of good ideas are brought up on this list, so few ever
happen. The only solution I am offering is everyone should help
spread the word and try and get more people involved with moving this
network forward. I wish I had better coding skills.
One of the core problems at least in my country where the ampr/44net
space is not well utilized is the lack of higher speed equipment to
build a network. You really have to be part of a well organized club
with site connections to do anything microwave on any big scale from
what I have seen.
Hi Brian,
I don't see the rip broadcasts from ucsd to my gateway at 69.165.175.62
since a couple days. I'm still in the encap.txt and I still see the
regular packets routed by ucsd.edu addressed to my subnets coming in.
Something wrong at that end?
Bob (Boudewijn) VE3TOK
--
There is nothing permanent except change
Heraclitus
> I've tried a few other things with no avail at this point.
Put a monitoring device at the outside port, or start a data capture in the router itself when EdgeOS can
do that, and then check what is arriving when you do the outside ping.
When you see packets coming from 169.228.66.251 addressed to your external IP with protocol field 4 you
at least know the external causes are covered. You can then concentrate on the setup of your router.
When no such packets appear, the problem is in your gateway setup at portal.ampr.org or your DNS entry.
As I don't see your callsign or AMPRnet IP anywhere in your message I can't do much research...
Rob
The host 'hamradio.ucsd.edu' will be offline some of Monday to
upgrade its operating system. Services such as this mailing
list and the DNS robot will be unavailable during that time.
- Brian
> Any ideas? I feel like I did configure the tunnel correctly, but I don't
> see anything on the LAN. Will post config if needed.
Your gateway config looks OK to me.
Your route entry appears in our gateway:
44.98.17.32/27 via 73.1.142.180 dev tunl0 proto ampr-ripd metric 4 onlink
(of course useless for us, because the method described on the WiKi does not
provide connectivity for gateway stations other than amprgw)
I can ping your external address.
Maybe Comcast or the modem is filtering IPIP?
Rob
Its not perfect. I was just curious as to the shift now being done
direct with BGP.
Probably the most useful information for many would be to correlate
gateways or network space with a rough location.
One might like to coordinate some coordinate some tunneled
activities/traffic with someone in a geographic area for instance. I
for one, would like to know who else in my state is reachable over
44net.
But I don't see an easy way to do that.
> Actually, Steve, because of the host-level filtering at amprgw,
> only 17652 hosts addresses implied in the encap file go anywhere.
> - Brian
That is what I wanted to suggest as well. You cannot calculate the number of
reachable hosts from the subnet sizes alone. Not even when you subtract two
(network- and broadcast address) for every subnet you know about.
And please do not try to resolve this puzzle by trying to ping every host...
Rob
Rob,
Its a count of the number of routed hosts, taken from the encap file
and the BGP announce list.
Small math bug, but the number of hosts was right. So about 10% of
the 44/8 allocation actually goes somewhere.
10/22/16 Routeable Ampr.org 44/8 Net Stats:
ENCAP Total Hosts: 1224922
ENCAP Percent: 7
BGP Total Hosts: 581204
BGP Percent: 3
