26 Jun
2013
26 Jun
'13
12:21 a.m.
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
26 Jun
26 Jun
4:44 a.m.
New subject: Basic help needed with Linux and rip44d
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
5:54 p.m.
New subject: ampr.org dns zone delegation
Steve,
To solve the dynamic DNS issue, I asked Brian to setup a hostname in the
AMPR DNS with a CNAME record instead of an A record, which referenced a
dynamic hostname.
Basically, when someone resolves your CNAME record, it will provide the
dynamic hostname, that hostname is then resolved for its A record.
https://en.wikipedia.org/wiki/CNAME_record
As an example, perform a NSLOOKUP on kb3vwg.ampr.org you'll note that
it's a CNAME record to a dynamic DNS name; that name is also used for my
44Gateway (instead of the IP).
73,
Lynwood
KB3VWG
27 Jun
27 Jun
12:32 a.m.
New subject: ampr.org dns zone delegation
Thanks for that. I know of some folks dealing with dynamic DNS issues and I
passed along this tip.
Michael
N6MEF
-----Original Message-----
From: 44net-bounces+n6mef=mefox.org(a)hamradio.ucsd.edu
[mailto:44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu] On Behalf Of
lleachii(a)aol.com
Sent: Wednesday, June 26, 2013 3:55 AM
To: 44net(a)hamradio.ucsd.edu
Subject: Re: [44net] ampr.org dns zone delegation
(Please trim inclusions from previous messages)
_______________________________________________
Steve,
To solve the dynamic DNS issue, I asked Brian to setup a hostname in the
AMPR DNS with a CNAME record instead of an A record, which referenced a
dynamic hostname.
Basically, when someone resolves your CNAME record, it will provide the
dynamic hostname, that hostname is then resolved for its A record.
https://en.wikipedia.org/wiki/CNAME_record
As an example, perform a NSLOOKUP on kb3vwg.ampr.org you'll note that it's a
CNAME record to a dynamic DNS name; that name is also used for my 44Gateway
(instead of the IP).
73,
Lynwood
KB3VWG
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
http://www.ampr.org/donate.html
5:42 a.m.
New subject: ampr.org dns zone delegation
On Wed, 26 Jun 2013, Michael E. Fox - N6MEF wrote:
Thanks for that. I know of some folks dealing with
dynamic DNS issues and I
passed along this tip.
Need to be careful with the use of CNAMEs. You should not for example
point MX at a CNAME.
--
Antonio Querubin
e-mail: tony(a)lavanauts.org
xmpp: antonioquerubin(a)gmail.com
6:45 p.m.
New subject: ampr.org dns zone delegation
Tony,
I failed to mention that; but in the scenario provided, it was
referencing an Internet host (IP address needing a FQDN). And you are
correct, a CNAME should (in good practice) only point to an A Record.
While it can point to another CNAME, you increase the chance that it
will not resolve, or that an unresolvable loop is created.
-Lynwood
KB3VWG
4197
days inactive
4199
days old
5 comments
4 participants
participants (4)
-
Antonio Querubin -
Jesse Hindmarsh -
lleachii＠aol.com -
Michael E. Fox - N6MEF