10 Apr
2014
10 Apr
'14
9:26 p.m.
Bart,
That realization you posit is INCORRECT:
AMPR IPs packets do one of 2 things at a 44GW:
1.) if a valid DST 44 address, go to a destination via IPIP to another 44GW
2.) all others use default gateway - go via IPIP to the AMPRGW
~~~
the request proposes an ***INVALID*** or STATIC option
3.) - ***if a 44 address, go to the 44 address via IPIP to the AMPRGW***
you asked:
"Why did your router choose tunl0 as the next-hop
when ***we don't
announce any special route for 44.24.221.0/24?***
Because within AMPR, 44.24.221.0/24 is an invalid IP subnet and is choosing the default
route, which is also invalid at AMPRGW.
Your router seems to have made a routing mistake
here.
It should have chosen the default route (0.0.0.0/0)
to send the packet since it has no special information about
44.24.221.0/24."
Not accurate, it made a CORRECT routing decision, it selected the ***Default AMPR
Route***
As I noted:
- the gateways using the KB3VWG Linux script (and most devices using rip44) are set to use
a custom routing table if the SRC and/or DST address is 44.0.0.0/8
- the default route for AMPR host to reach the Internet is:
ip route add default dev tunl0 via 169.228.66.251 onlink table 44
I don't want to belabor the group on this, as I had to discover this by trial and
error when developing the script; your only options are to:
- develop an Amateur Radio custom Linux kernel and IP command; or
- have every station add a static route for you (which should only be used for subnets
local to the GW)
73,
Lynwood
KB3VWG