26 Jun
2013
26 Jun
'13
4:44 a.m.
Thanks for the link. As it turns out, my routing fundamentals are based in the Cisco world
while my Linux skills are heavily conflicted. I was able to get the gateway up and running
as expected with a little help.
Thanks to all who replied.
73 de WC3XS
Sent from my iPhone
On Jun 25, 2013, at 1:21 PM, lleachii(a)aol.com wrote:
(Please trim inclusions from previous messages)
_______________________________________________
Jesse,
Take a look at my startup script at
http://44.60.44.13/startampr
It seems you have a similar setup, although one line of your configuration seems
incorrect:
ip route add 44/8 via 169.228.66.251 dev tunl0 onlink src 44.64.192.253
You should remove this route, it's invalid inside AMPR. You should not reach
44.0.0.0/8 via AMPRGW (169.228.66.251), you should reach each subnet via its gateway WAN
IP address, as populated by rip44d. The return packet would come in the same manner, via
their 44GW that has a route configured for you.
My router:
@kb3vwg-001:~# ip route get 44.64.192.253
44.64.192.253 via 24.229.88.252 dev tunl0 src 172.31.255.254
My route table shows:
44.64.192.0/24 via 24.229.88.252 dev tunl0 onlink window 840
73,
Lynwood
KB3VWG
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html