Hi all,
I have setup, after many years of absence, our AMPRnet GATEWAY in
Athens, running in a LINUX BOX.
I have a dynamic IP here which rarely changes and up to now I had
access to several AMPRnet hosts.
Yesterday I had to reset my router (TL-WR1043ND running DD-WRT) and I
lost connectivity.
Checking http://portal.ampr.org I can see that my new Internet IP has
been updated (it takes about 1 hour I think).
Problem is that now I cannot ping gb7cip.ampr.org or any other AMPRnet
host I could before?
I can see that rip44d is doing it's thing using "tcpdump -i tunl0".
How long does it take for AMPRnet to be informed after a change in
Internet IP (nor 44net IP)? It has been more than 12 hours since my
router got it's new IP and no joy yet!
Any ideas guys?
--
73 de SV1UY
Demetre Ch. Valaris
IP Coordinator for AMPRnet in Greece
e-mail: demetre.sv1uy(a)gmail.com
Radio e-mail: sv1uy(a)winlink.org
(to use my radio e-mail put //WL2K in the beginning of the subject line)
http://www.qsl.net/sv1uy
I was just curious, is the portal's DNS request page up and running,
or do I need to try to contact my coordinator directly?
I'd like to add a couple of A name records for my routing experiment.
router-3.k1qv.ampr.org A 44.4.36.3
router-5.k1qv.ampr.org A 44.4.36.5
These will be the two routers that will be connected to my gateway via OpenVPN.
Thanks for the update,
Blaine, K1QV
Sent from my iPhone
Anybody that knows about BGP & GRE, I was wondering if this would be useful
for us to look into (I am not that person).
http://www.rfc-base.org/txt/rfc-6836.txt
Jim A.
Michael,
At this point, ampr-ripd (C implementation) is the best thing out
there in my opinion.
Hessu, wrote the rip44d, and that required Perl and a multicast
package to run. So running this on a WRT54G, for instance was
probably not going to happen. I'd like to think with the C
implementation, this could be a reality.
Also, I am not sure, but do think the C implementation stands the
greatest chance to run cross platform. Hessu's perl one was kind of
locked to Debian installs.
Again, it's all so new, I personally haven't had they time yet to try
it on a bunch of different platforms.
I actaully am not sure why someone would go with amprd over ampr-ripd.
Perhaps others can comment.
Steve
Here are some random thoughts:
It would be interesting or maybe helpful if the ampr.org name server
did some statistics collection. These stats could be used to help
prune dead records? I am not sure how resource intensive that might
be however. It looks like you can use Cacti in conjunction with BIND.
It is also important that we have some idea what is on the amprnet,
what it used for. The Michigan Digital Radio group has some basic
activity polling : http://server1.nuge.com/~drg/network.html
Perhaps even something that can be installed on gateways that
promiscuously monitors well know ports/services, and can be configured
to report activity to a central page? If nothing else can the gateway
portion of the portal have some additional text boxes, so folks can
explain things a bit more like the old resource.txt?
There is a message showing on my RPI gateway 44.135.96.17 tunnel TTY0
saying
"ignored packet from 44.131.160.1: 520: 504" every 5 minutes or so. any
suggestion how to resolve this...
Luc VE3JGL in Ottawa
> Subject:
> Re: [44net] dd-wrt and ipip
> From:
> lleachii(a)aol.com
> Date:
> 08/13/2013 05:04 PM
>
> To:
> 44net(a)hamradio.ucsd.edu
>
>
> All,
>
> I think the reason that nodes on the 44 Network cannot reach me is that my router is not allowing connections from the Internet to pass through.
>
> My setup:
>
> Router 1
> WAN 76.114.216.250 <> LAN 192.168.x.x <>
>
> Router 2
> WAN 192.168.x.2 <> LAN 192.168.y.x
>
> AMPRGW
> 192.168.y.5
>
> In trying to setup IPTABLES commands to allow IPIP traffic, I've had no success thus far.
>
> On Router1:
> iptables -t filter -I INPUT -p ipip -j ACCEPT
> iptables -t filter -I FORWARD -p ipip -j ACCEPT
> iptables -t nat -I PREROUTING -i vlan1 -p ipip -j DNAT --to-destination 192.168.x.2
>
> On Router2:
>
> iptables -t filter -I INPUT -p ipip -j ACCEPT
> iptables -t filter -I FORWARD -p ipip -j ACCEPT
> iptables -t nat -I PREROUTING 1 -s 169.228.66.251 -p ipip -i vlan1 -j DNAT --to-destination 192.168.y.5
> iptables -t nat -I PREROUTING 2 -p ipip -i vlan1 -j DNAT --to-destination 192.168.y.5
>
> Any ideas?
>
Your problem is the protocol number used for encapsulation, I think.
The "ipip" protocol is protocol 94, the one that was registered mistakenly at a time when protocol 4,
which does exactly the same, already existed. Now the protocol 4 is used, which is in /etc/protocols
under its name "ip".
So use -p ip or just -p 4.
Rob
Greetings,
I've been doing some work to get the IPIP tunnel information into a router on
a daily basis, has anyone else automated this?
I was wondering how the reachability of this from the global routing table of
the public internet works, if at all. Everything I've been reading says this
is all separate, but we do interconnect at a couple locations. I must admit
I'm new to this, but is 44/8 intended to be totally separate a la the GRX
network?
Granted my use of this space is for high speed wireless networks on the ham
bands, I have little interest in the 9.6 kilobaud TCP/IP packet radio.
I've got some of the 900MHz FHSS gear hacked to run in a narrower channel, and
I've been experimenting with running some of the 5ghz units in the ham band at
5cm (5mhz channel is able to do about 10mbit/s). My intention is to have it
all work across hardware routers, ie cisco/ALU/juniper rather than maintain a
bunch of linux boxes.
Thoughts?
--
Bryan Fields
727-409-1194 - Voice
727-214-2508 - Fax
http://bryanfields.net
I've been trying add the following route to my "44" table to insure that
local packets get sent out the wireless interface.
ip route add 44.50.128.0/24 dev wlan0 table 44
However, I can't get it to be added when the system restarts.
Any suggestions would be appreciated.
Thanks.
-Neil
--
Neil Johnson -N0SFH
http://erudicon.com
When adding the route statement to the initialization sequence, make sure the wlan0 interface exists; don't put it too early in the sequence. Perhaps best to add it and its 'del' counterpart to the networking scripts that bring the wlan0 interface up and down, not to the rc-scripts?
P.
Sent from a mobile, sorry for any typoes...
-------- Original message --------
From: Neil Johnson <neil.johnson(a)erudicon.com>
Date: 2013/08/11 22:07 (GMT+01:00)
To: AMPRNet working group <44net(a)hamradio.ucsd.edu>
Subject: [44net] Trouble setting static route with ampr-ripd
ip route add 44.50.128.0/24 dev wlan0 table 44
However, I can't get it to be added when the system restarts.
