Hi,
Thanks for writing this program and your support.
Turns out I had the wrong netmask on my tunnel interface.
Seems to be working now.
73'
Steve, KB9MWR
Not all that long ago I installed the new rip44d on a CentOS install.
It did receive the broadcasts as I saw them in debug mode. However it
didn't seem to install these routes to the local routing table.
I assume that has to with networking working slightly different on the
various flavor of Linux.
So now I am trying with Ubuntu 10.04 server, but I can't even seem to
receive the broadcasts. It just sits there in the main loop waiting
for broadcasts. Yet when I watch with tcpdump, there are things going
on. But I am mostly concerned by the udp port unreachable that I am
responding with:
(For now) I have the Linux firewall completely disabled (as far as I
know... more of a RedHat guy) and connected directly to the outside
world.
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
13:30:00.337401 IP amprgw.sysnet.ucsd.edu.route >
cpe-174-103-224-97.new.res.rr.com.38700: RIPv2, Response, length: 504
13:30:00.337442 IP cpe-174-103-224-97.new.res.rr.com >
amprgw.sysnet.ucsd.edu: ICMP cpe-174-103-224-97.new.res.rr.com udp
port 38700 unreachable, length 540
13:30:00.337454 IP amprgw.sysnet.ucsd.edu >
cpe-174-103-224-97.new.res.rr.com: IP gw.ampr.org.route >
rip2-routers.mcast.net.route: RIPv2, Response, length: 504
(ipip-proto-4)
13:30:00.337606 IP amprgw.sysnet.ucsd.edu.route >
cpe-174-103-224-97.new.res.rr.com.38700: RIPv2, Response, length: 504
13:30:00.337624 IP cpe-174-103-224-97.new.res.rr.com >
amprgw.sysnet.ucsd.edu: ICMP cpe-174-103-224-97.new.res.rr.com udp
port 38700 unreachable, length 540
13:30:00.337632 IP amprgw.sysnet.ucsd.edu >
cpe-174-103-224-97.new.res.rr.com: IP gw.ampr.org.route >
rip2-routers.mcast.net.route: RIPv2, Response, length: 504
(ipip-proto-4)
13:30:00.337976 IP amprgw.sysnet.ucsd.edu.route >
cpe-174-103-224-97.new.res.rr.com.38700: RIPv2, Response, length: 504
13:30:00.338000 IP cpe-174-103-224-97.new.res.rr.com >
amprgw.sysnet.ucsd.edu: ICMP cpe-174-103-224-97.new.res.rr.com udp
port 38700 unreachable, length 540
13:30:00.338008 IP amprgw.sysnet.ucsd.edu >
cpe-174-103-224-97.new.res.rr.com: IP gw.ampr.org.route >
rip2-routers.mcast.net.route: RIPv2, Response, length: 504
(ipip-proto-4)
13:30:00.338015 IP amprgw.sysnet.ucsd.edu.route >
cpe-174-103-224-97.new.res.rr.com.38700: RIPv2, Response, length: 504
13:30:00.338026 IP cpe-174-103-224-97.new.res.rr.com >
amprgw.sysnet.ucsd.edu: ICMP cpe-174-103-224-97.new.res.rr.com udp
port 38700 unreachable, length 540
13:30:00.339133 IP amprgw.sysnet.ucsd.edu >
cpe-174-103-224-97.new.res.rr.com: IP gw.ampr.org.route >
rip2-routers.mcast.net.route: RIPv2, Response, length: 504
I am looking for tips on what I am doing wrong, or what distribution
and steps those who are doing this had success with.
Thanks,
Steve, KB9MWR
I found this topic back in the archives, and can shed a little light on
it from my testing. If you are looking to fully convert the encap.txt
for use on a cisco device, you will need a 2600 or better to handle the
large number of tunnels needed. I used an old encap.txt file and
converted about 320 tunnels which brought a 2610 to a screeching halt. I
will be testing with a 2651XM to see how results differ, hopefully I
will not need to get out any of the big stuff. Below is the output of a
converted line from an old encap.txt:
!
interface tunnel 750190592 <--tunnel number created from converting ip
to decimal
description Link to 44.183.0.0
ip unnumbered loopback1 <-- using the loopback as the assigned 44
address space (could use a physical)
tunnel source 99.119.146.20
tunnel destination 130.208.168.63
tunnel mode nos <-- compatible with jnos
!
ip route 44.183.0.0 255.255.0.0 tunnel750190592
!
The next issue is RIP updated to jnos. I get updated sent to jnos, but
it does not add them to the routing table. The error states that the
routes are not from IPIP and they are domain 0. I will make the
conversion script available when I get it a little more polished.
Jason
http://www.ampr.org/tos.txt
Still a little technical work to be done but start your planning for new IP
focused amateur radio networks.
Need a HSMM network space?
Need a fixed IP for a repeater, remote control station, gateway, ROIP, etc.
Need a few routable IP addresses for multiple instances of an application
that uses a well known TCP or UDP port?
I have a few slides from my short presentation at DCC today that I will
make available in the next few days.
A small working group, to which I was honored to be included, worked out
guidelines for the creation of this AUP over the last few months and it was
published today.
------------------------------
John D. Hays
K7VE
PO Box 1223, Edmonds, WA 98020-1223
<http://k7ve.org/blog> <http://twitter.com/#!/john_hays>
<http://www.facebook.com/john.d.hays>
hi group
im looking to add a few more links/forwarding partners. need european.
latin america and aus and or nz
but will welcome anyone :)
i am also interested in hf forwarding if anyone is still doing it anymore
thanks
glenn - ka0mos/ve1
It looks like you missed one so I'll sum it up...
I can ping Jim but cannot telnet to him. A password issue of some sort.
Don - ve3zda
-----Original Message-----
From: Don [mailto:ve3zda@gmail.com]
Sent: Tuesday, September 04, 2012 7:44 PM
To: '44Net(a)hamradio.ucsd.edu'
Subject: [44net] forwarding partners
Hey Glenn,
I can ping him no problem.
Don - ve3zda
-----Original Message-----
From: 44net-bounces+ve3zda=gmail.com(a)hamradio.ucsd.edu
[mailto:44net-bounces+ve3zda=gmail.com@hamradio.ucsd.edu] On Behalf Of Glenn
A. Bursell - KA0MOS/VE1
Sent: Tuesday, September 04, 2012 12:18 PM
To: AMPRNet working group
Subject: Re: [44net] forwarding partners
(Please trim inclusions from previous messages)
_______________________________________________
hi jim
good to hear from you
i am not able to ping you
glenn
_______________________________________________ Glenn i am getting my
system back up Can you check connectivity to me? Jim af5ca ex wu3v
44.108.3.30 Jim Sent from my iPhone On Sep 4, 2012, at 10:45 AM, "Glenn
A. Bursell - KA0MOS/VE1" <ka0mos(a)eastlink.ca> wrote:
>> (Please trim inclusions from previous messages)
>> _______________________________________________
>> hi group
>>
>> im looking to add a few more links/forwarding partners. need european.
latin america and aus and or nz
>> but will welcome anyone :)
>> i am also interested in hf forwarding if anyone is still doing it anymore
>>
>>
>> thanks
>> glenn - ka0mos/ve1
>> _________________________________________
>> 44Net mailing list
>> 44Net(a)hamradio.ucsd.edu
>> http://hamradio.ucsd.edu/mailman/listinfo/44net
> _________________________________________
> 44Net mailing list
> 44Net(a)hamradio.ucsd.edu
> http://hamradio.ucsd.edu/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
Hey Glenn,
I can ping him no problem.
Don - ve3zda
-----Original Message-----
From: 44net-bounces+ve3zda=gmail.com(a)hamradio.ucsd.edu
[mailto:44net-bounces+ve3zda=gmail.com@hamradio.ucsd.edu] On Behalf Of Glenn
A. Bursell - KA0MOS/VE1
Sent: Tuesday, September 04, 2012 12:18 PM
To: AMPRNet working group
Subject: Re: [44net] forwarding partners
(Please trim inclusions from previous messages)
_______________________________________________
hi jim
good to hear from you
i am not able to ping you
glenn
_______________________________________________ Glenn i am getting my
system back up Can you check connectivity to me? Jim af5ca ex wu3v
44.108.3.30 Jim Sent from my iPhone On Sep 4, 2012, at 10:45 AM, "Glenn
A. Bursell - KA0MOS/VE1" <ka0mos(a)eastlink.ca> wrote:
>> (Please trim inclusions from previous messages)
>> _______________________________________________
>> hi group
>>
>> im looking to add a few more links/forwarding partners. need european.
latin america and aus and or nz
>> but will welcome anyone :)
>> i am also interested in hf forwarding if anyone is still doing it anymore
>>
>>
>> thanks
>> glenn - ka0mos/ve1
>> _________________________________________
>> 44Net mailing list
>> 44Net(a)hamradio.ucsd.edu
>> http://hamradio.ucsd.edu/mailman/listinfo/44net
> _________________________________________
> 44Net mailing list
> 44Net(a)hamradio.ucsd.edu
> http://hamradio.ucsd.edu/mailman/listinfo/44net
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
KB9MWR,
I have had success using Ubuntu Linux 12.04 LTS and rip44d to make an AMPR router. It seems at the point you executed rip44d, your tunl0 interface was not yet properly configured and the interface placed into UP status.
There were only a few main things I had to do in setup:
1.) Enable IPv4 forwarding
2.) create a startup script that: starts the IPIP tunnel as tunl0 and specifies its IP address, specify routing to AMPRGW and setup a Kernel route 'table 44' that has all 44/8 traffic use this routing table (thanks to Brian and PE1CHL for this information)
3.) at the end of this script, have it execute rip44d which was modified on line 201 to places routes on 'table 44'
You should be able to use the commands in this script on the CLI to enable the tunnel and rip44d in verbose mode to see the paswword, then just place it and your AMPR IP assignments (your 44 IP address/CIDR, the password and your Gateway address) into the script in the proper places.
These instructions do not cover the setup of eth0 and eth1, which during my setup, eth0 was a dynamically assigned IP by my residential gateway router that forwards tunnel packets into the subnet, eth1 is now configured to provide an Ethernet interface for my 44.60.44.0/24 LAN.
########################################################
### Enables AMPR IPIP Tunnel Interface
modprobe ipip
ip addr add 44.60.44.2/24 dev tunl0
# gives tunnel its own TTL enabling traceroute over tunnel
ip tunnel change ttl 64 mode ipip tunl0
ip link set dev tunl0 up
### Creates AMPR Default Routes on main Route Table
#route to 44.60.44.0/24 on main route table
ip rule add to 44.60.44.0/24 table main priority 1
### Specifies Routes to and from 44/8 are entered on Route Table 44
ip rule add from 44.0.0.0/8 table 44 priority 44
ip rule add to 44.0.0.0/8 table 44 priority 45
### Creates Default Route to the AMPRGW and the
### Internet At-large, on the 44 Router
## Per PE1CHL: 'This is "required" to get routing of the net-44 traffic correct
## and have a default route for the tunneled traffic different from the default
## route of the system. It may be possible to get it working without this,
## but policy based routing is so much easier'
# AMPRGW connects via eth0
ip route add 169.228.66.251 dev eth0 table 44
# Connection to 0/0 by 44/8 Hosts on AMPRGW, commenting disables Internet access for your 44 subnet
ip route add default dev tunl0 via 169.228.66.251 onlink table 44
### Begins the rip44d Router Dameon ###
./rip44d_table44 -a <YOUR PUBLIC IP> -p <THE PASSWORD> < /dev/null &
########################################################
########################################################
### EDIT rip44d Line 201
### - $cmd = "LANG=C $routebin route add $rkey via $nexthop dev $tunnel_if window $tcp_window onlink";
### + $cmd = "LANG=C $routebin route add $rkey via $nexthop dev $tunnel_if window $tcp_window onlink table 44";
########################################################
73,
Lynwood Leach
KB3VWG
-----Original Message-----
From: 44net-request <44net-request(a)hamradio.ucsd.edu>
To: 44net <44net(a)hamradio.ucsd.edu>
Sent: Mon, Aug 20, 2012 2:58 pm
Subject: 44Net Digest, Vol 1, Issue 69
Send 44Net mailing list submissions to
44net(a)hamradio.ucsd.edu
To subscribe or unsubscribe via the World Wide Web, visit
http://hamradio.ucsd.edu/mailman/listinfo/44net
or, via email, send a message with subject or body 'help' to
44net-request(a)hamradio.ucsd.edu
You can reach the person managing the list at
44net-owner(a)hamradio.ucsd.edu
When replying, please edit your Subject line so it is more specific
than "Re: Contents of 44Net digest..."
Today's Topics:
1. rip44d and centos (kb9mwr(a)gmail.com)
----------------------------------------------------------------------
Message: 1
Date: Sun, 19 Aug 2012 19:55:28 -0500
From: kb9mwr(a)gmail.com
To: 44net(a)hamradio.ucsd.edu
Subject: [44net] rip44d and centos
Message-ID:
<CAK4XxyQiY5m+_f3fi2HD2Nd6Pie1qTwbMM_crsyfz14wS_Hz6g(a)mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Hello,
I decided I am going to try and setup a gateway for the first time. I
like the rip44d idea, but I didn't get very far. Can anyone provide
some pointers?
I am trying to do it on CentOS 5 install directly connected to the
outside world.
http://wiki.ampr-gateways.org/index.php?title=Rip44d
[root@ham ~]# rpm -i perl-IO-Interface-1.04-1.el5.rf.i386.rpm
[root@cpe-174-103-214-209 ~]# rpm -i
perl-IO-Socket-Multicast-1.12-1.rhel5.i386.rpm
[root@ham ~]# ./rip44d -v
Prototype mismatch: sub main::AF_INET: none vs () at
/usr/lib/perl5/5.8.8/constant.pm line 99.
found local address: 174.103.214.209
found local address: 127.0.0.1
opening UDP socket 520...
unknown or unconfigured interace tunl0 at ./rip44d line 469
Thanks,
Steve, KB9MWR
------------------------------
_______________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
End of 44Net Digest, Vol 1, Issue 69
************************************
