5 Jan
2015
5 Jan
'15
1:49 a.m.
Hello Paul,
I checked a little and there are a lot of issues.
- gb7cip is listed in the encap data, but is not responding. Gateway is
reachable.
- 44.131.161.0/24 has no entry in the encap list (needs to be registered
with the same gw as gb7cip)
- 44.131.182.0/24 - the same
- 44.131.210.0/24 - the same
Now regarding 44.131.161.0/24:
There are 2 subnets entries in the encap data:
44.131.161.56/29 - no ping response from any host, gateway is reachable
44.131.161.100/30 - no ping response from any host, gateway not responding
to ping
So, unless subnets 161, 182 and 210 are not in the encap data with a corect
gateway, and the gateway and subiacent chain doesn't forward the needed
traffic, they are not reachable from the mesh network.
-----Original Message-----
From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu
[mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Paul
Lewis
Sent: Sunday, January 04, 2015 16:48
To: AMPRNet working group
Subject: [44net] GB7CIP Amprnet Connectivity
(Please trim inclusions from previous messages)
_______________________________________________
...
Amprnet Connectivity 28 November 2015
GB7CIP currently act as gateways for 44.131.161 via GB7IPF SouthBucks
these UDP connected down stream 44.131.168 via M1DUO Cambs
amprnet IP connections. 44.131.182 via GBINE SW Essex
44.131.210 via GB7COW N Devon
You can test if these are connected by pinging
44.131.161.228 44.131.168.129 44.131.182.2 44.131.210.1 44.131.244.1
...