- 44net - mailman.ardc.net

Re: [44net] 44Net Digest, Vol 1, Issue 79

by kb9mwr＠gmail.com

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

13 years, 4 months

1
0
0 0

rip44

by kb9mwr＠gmail.com

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

13 years, 4 months

2
1
0 0

Cisco gateway/tunnel

by Jason R Begley

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

13 years, 4 months

2
1
0 0

New AUP/TOS

by John D. Hays

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>

13 years, 4 months

5
4
0 0

connection

by Kutche, Jerry (Mitchell) USA

I need a link to a couple others via JNOS.. Please email me and we can exchange info... www.qrz.com n9lya

13 years, 5 months

1
0
0 0

forwarding partners

by Glenn A. Bursell - KA0MOS/VE1

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

13 years, 5 months

8
9
0 0

Re: [44net] forwarding partners

by Don

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

13 years, 5 months

3
3
0 0

forwarding partners

by Don

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

13 years, 5 months

1
0
0 0

rip44d fedora 4

by Glenn Bursell

can someone shed some light on how i can get this working in fedora 4 thanks glenn

13 years, 5 months

4
10
0 0

Re: [44net] rip44d and centos

by lleachii＠aol.com

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 ************************************

13 years, 5 months

1
0
0 0

rip44d and centos

by kb9mwr＠gmail.com

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

13 years, 5 months

1
0
0 0

Raspberry Pi for Ham Radio Yahoo group.

by Kutche, Jerry (Mitchell) USA

Raspberry_Pi_4-Ham_RADIO-subscribe(a)yahoogroups.com I started this group to discuss The Raspberry Pi as a Computer for Ham Radio projects. Example.. John Wiseman has incorporated a TNCx onto one of his ... I am sure we could find or develop software/Hardware for many Ham radio Projects if we could gather the tallent in one location... Learn more here. www.raspberrypi.org 73 Jerry N9LYA HF Skipnet Coordinator HF Skipnet Midwest HUB ARRL Net Manager - Packet Indiana IP Coordinator Indiana Packet Coordinator Sysop N9LYA/K9BBS/W9BBS/W9OTR W9OTR Hoosier Amateur Radio Digital Society W9HU Hooiser Radio Society

13 years, 5 months

3
2
0 0

TAPR/ARRL DCC

by Brian Kantor

Will any of you folk be attending the TAPR/ARRL Digital Communications Conference next month (September 21-23) in Atlanta? <http://www.tapr.org/dcc.html> - Brian

13 years, 5 months

6
7
0 0

44 Network Gateway

by Mike Melnik

Hello all Can anyone explain to me how to get the Gateway IP Address? Mine is 44.92.35.12 Mike-N9PMO BPQ32 Moderator www.n9pmo.com

13 years, 6 months

3
2
0 0

MARA "gateways" archives offline?

by Brian Kantor

Does anyone know if the archives of this mailing list (and under its previous name, "gateways") that were located at www.mara.org will be coming back on line? The site has been unreachable for several weeks. - Brian

13 years, 6 months

1
0
0 0

jnos and ubuntu 12.04

by Daniel Curry

I am hearing from local hams that jnos and ubuntu 12.04 LTS are not compatible? Reasons: 1) unable to telnet tun0 port to the jnos application from the linux host 2) Something about module for tun not getting loaded 3) Response time from the radio side is slow on connections. Can someone shed some light if there is a compatibility issue and what are the hoops that must be configured, if any? -- Daniel Curry PGP: AD5A 96DC 7556 A020 B8E7 0E4D 5D5E 9BA5 C83E 8C92 San Francisco/Silicon Valley AmprNet Co-coordinator [44.4.0.0/16]

13 years, 6 months

8
8
0 0

rip updates?

by JJ

howdy gang....wondering how to get rip updates coming to my gateway? Just registered it 3 days ago on the gateway robot and waited...router is set to pass port 520 to jnos both ways, but not seeing anything being sent? monitored the router, linux, and jnos for anything on port 520udp/tcp...nothing (yet?) perhaps I need to wait longer...not dead in the water anyhow, kind help from a few admins (you know who you are, hi!) allowed me to at least ftp the recent encap file..... I'm all set up to grab ripv2 .. Cheers, John

13 years, 6 months

1
1
0 0

Re: [44net] jnos and ubuntu 12.04

by Russ WL7LP

ok I got the tun0 working in Ubuntu 12.04 gui version and also the tun0 is working in jnos as well. only problem I am having is getting out to the rest of the world and I believe it's just a router problem not having the new addresses for the new machine. haven't tested the radio's part yet to see if there slow. but at least the tun0 is up 73 Russ WL7LP ________________________________ From: Ted Gervais <ve1drg(a)gmail.com> To: Russ WL7LP <wl7lp(a)yahoo.com> Sent: Sunday, July 22, 2012 10:10 AM Subject: Re: [44net] jnos and ubuntu 12.04 Yes Russ. The server version works great especially where it doesn't need as much memory/resources etc.. That is why I went to that version. I have a very old computer here with limited memory so the server version fit the bill. On Sun, Jul 22, 2012 at 1:53 PM, Russ WL7LP <wl7lp(a)yahoo.com> wrote: Hi Ted. > > >Thanks Ted. that's good to know it works fine with the server version. I am running the GUI version. >though I may switch to the server version if can't get it working with the gui version. > > >73 Russ WL7LP > > >________________________________ > From: Ted Gervais <ve1drg(a)gmail.com> >To: Russ WL7LP <wl7lp(a)yahoo.com>; AMPRNet working group <44net(a)hamradio.ucsd.edu> >Sent: Sunday, July 22, 2012 9:32 AM >Subject: Re: [44net] jnos and ubuntu 12.04 > > > >Hi Russ. > >I run the latest Jnos on Ubunty 12.04LTS (server edition). >It works fine. No problems that I know of, in particular the tun0 feature. >That works without a problem. > > > >On Sun, Jul 22, 2012 at 12:22 PM, Russ WL7LP <wl7lp(a)yahoo.com> wrote: > >(Please trim inclusions from previous messages) >>_______________________________________________ >> >>I been trying to get jnos and ubuntu 12.04 LTS to work for a week now and no joy at it. >>tun0 will not loaded from jnos at all. only way I found it does is to start jnos as sudo >> >> >>sudo ./jnos that loads the tun0 sometimes but then another stuff don't work and crashes >>shortly after. some say to get both to work you need to load the tun0 before jnos. >>never tried it yet but have a coupe of files createtun0.c that you compile into a binary and run it >> >>that will load the tun0 with what name you give it. going to try that. a friend of mine did it and seem >>to be working good for him. but if there is a solution to jnos and ubuntu 12.04 I should would love >>to hear about it. >> >> >>73 Russ WL7LP >> >> >>________________________________ >> From: Daniel Curry <daniel(a)danielcurry.net> >>To: 44net(a)hamradio.ucsd.edu >>Sent: Saturday, July 21, 2012 7:51 AM >>Subject: [44net] jnos and ubuntu 12.04 >> >>(Please trim inclusions from previous messages) >>_______________________________________________ >> I am hearing from local hams that jnos and ubuntu 12.04 LTS are not >>compatible? >>Reasons: >> >>1) unable to telnet tun0 port to the jnos application from the linux host >>2) Something about module for tun not getting loaded >>3) Response time from the radio side is slow on connections. >> >> Can someone shed some light if there is a compatibility issue and what >>are the hoops that must be configured, if any? >> >> >>-- >>Daniel Curry >>PGP: AD5A 96DC 7556 A020 B8E7 0E4D 5D5E 9BA5 C83E 8C92 >> >>San Francisco/Silicon Valley AmprNet Co-coordinator [44.4.0.0/16] >> >> >> >>_________________________________________ >>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 >> > > >-- > >Ted Gervais (ve1drg) >1464 Luxury Ave >Windsor, Ont >N8P 0A9 >(519)956-9776 > > > -- Ted Gervais (ve1drg) 1464 Luxury Ave Windsor, Ont N8P 0A9 (519)956-9776

13 years, 6 months

1
0
0 0

Using a cisco to do the tunnelling

by renzorossi＠libero.it

Ciao Sam in CisarNet (http://www.cisar.it/radiowiki/index.php?title=Italian_Cisar_Radio_Amateur_W…) we are already using with success a Cisco router to "Gateway" our wifi national network to amprnet 44.0/8, with a lot of tunnel interfaces configured by means of a visual basic script and batch commands running by a normal windows xp computer. This script is easily adaptable for your needings. Sorry for my delay in the answer, but I have some trouble in receiving correctly 44net mailing list. Please discard my message if this is not useful anymore, or feel free to contact me to share our scripts. Ciao from Italy. IW0SAB Renzo. [44net] Using a cisco to do the tunnelling Rob Janssen pe1chl at amsat.org Thu Jun 7 13:32:21 PDT 2012 Previous message: [44net] Using a cisco to do the tunnelling Next message: [44net] dd-wrt setup for amprnet Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] VK4FQ/VK4TTT Sam wrote: > Hey Guys > > We have a surplus of cisco routers with dsl wics due to an upgrade. > We have put DSL into a few of our repeater locations and want to put packet (before the 12/13 storm season) > I am looking for a config that will do the ip tunnel encap for 44 net. > > If you have done it please email me vk4fq at smellyblackdog.com.au with destructions please I have studied the matter in the past and I think it will be a bit difficult. Cisco support only a single source and destination address for an IPIP tunnel interface. In other systems (NOS, Linux) the idea usually is that you setup a single tunnel interface and have a routing table that tells the system where to send packets for a certain subnet. But in a Cisco I think you would need to configure a separate tunnel interface for each gateway station. The problem is that the station list is not static, so you need to write some script that generates IOS config commands to insert, delete and modify tunnel interfaces to track the changes in the encap.txt. There are multipoint tunnels in IOS, like DMVPN, but those protocols are not in use in the amateur IP net. (unfortunate, because it could automate the entire encap.txt hassle and solve all problems for people with dynamic addresses) Correct me if I am wrong... We have an unused 887 at work that I would probable be able to get donated for home use, but I have hesitated to take the plunge. Rob

13 years, 7 months

1
0
0 0

Current Encap File

by VK4FQ/VK4TTT Sam

Guys Can someone please send me a current encap file please. If there is somneone lurking - please add me to the daily email list so I dont have to keep on asking Is there any desiginated address pool for ipv6 Sam

13 years, 7 months

2
1
0 0

Subnetmask /15

by Jann Traschewski

Hi Brian, since the line for routed prefixes of a single gateway at Jim Fullers mailing robot is limited, I combined the prefix of austria (44.143/16) and switzerland (44.142/16) to 44.142/15. Even the german HAMNET has 44.224/15. Marius, YO2LOJ, just told me that he doesn't receive these prefixes from "amprgw" by RIP. I guess the amprgw-code doesn't allow prefixes wider than /16. Can you check the code and allow even /15 subnet masks? I have no idea how to overcome this line limit :( Currently DB0FHN is the central gateway "translating" from IPIP-networks to the HAMNET and vice versa: db0fhn:~# grep 141.75.245.225 /opt/encap/encap.txt route addprivate 44.130/16 encap 141.75.245.225 route addprivate 44.142/15 encap 141.75.245.225 route addprivate 44.151/16 encap 141.75.245.225 route addprivate 44.161/16 encap 141.75.245.225 route addprivate 44.224/15 encap 141.75.245.225 route addprivate 44.134.189/24 encap 141.75.245.225 route addprivate 44.134.190/23 encap 141.75.245.225 I know that there is even some other software (with filters limiting to /16) out there, but I hope most of them will accept /15. Thank you, 73, Jann DG8NGN DL-IP-coordination Btw: I'll attend the HAM RADIO exhibition in Friedrichshafen if anyone wants to have an eyeball QSO. -- Jann Traschewski, Georgenschwaigstr. 10, D-80807 Munich, Germany Tel.: +49-911-696971, Mobile: +49-170-1045937, E-Mail: jann(a)gmx.de Ham: DG8NGN / DB0VOX, http://www.qsl.net/dg8ngn

13 years, 7 months

4
3
0 0

Active but quiet regions

by Jann Traschewski

Hi All, following the recent discussions on this list I like to remind that there are really active regions using net44. In preparation of the HAM RADIO in Friedrichshafen (www.hamradio-friedrichshafen.de/ham-en) I created an overview of such a region. Please find the "HAMNET Overview 2012" at http://db0fhn.efi.fh-nuernberg.de/doku.php?id=start&#hamnet --- As one of the IP-coordinators for this region I'm very happy to be able to use 44/8 for the allocations. Two reasons for that: * 44/8 will never clash with our radio amateurs private used RFC1918 addresses within 10/8, 172.16/12 or 192.168/16. They can fully integrate AMPR access into their LAN. * I can easily adjust my firewall rules to distinguish between radio amateurs (44/8) and the rest of the internet. Discussions about CIDR makes me nervous :D --- Currently I'm thinking about different tunnel mechanism for net44 and I don't know the answer :) On one hand we have our stable system to distribute information about IP-ENCAP (protocol #4) tunnels to net44-routes by E-Mail, FTP or RIP. Routing information will be updated through the robot once a day. --> no realtime On the other hand we have manual IP-ENCAP tunnels for our tunnels within the HAMNET (a part of the AMPRNet). We speak BGPv4 over these tunnels and get realtime routing information. --> no automatic tunnels I don't know what would be the best for tunneling. Isn't there a proper mesh protocol? I did have a look at OpenNHRP, but it will not fit our needs regarding a simple, automatic, realtime capable solution. --- I do like the posting from Hessu, OH7LZB, about the different technical solutions to do direct announcements on the Internet. Right questions to be answered... However at this stage I guess most AMPRNet-systems will not be able to directly communicate to net44-destinations with their own net44-ip-address. 73, Jann DG8NGN -- Jann Traschewski, Georgenschwaigstr. 10, D-80807 Munich, Germany Tel.: +49-911-696971, Mobile: +49-170-1045937, E-Mail: jann(a)gmx.de Ham: DG8NGN / DB0VOX, http://www.qsl.net/dg8ngn

13 years, 7 months

1
0
0 0

Re: [44net] Use of the network

by Bjorn Pehrson

Even better to make it one dedicated asn. VK4FQ/VK4TTT Sam <vk4fq(a)smellyblackdog.com.au> skrev: >(Please trim inclusions from previous messages) >_______________________________________________ >Easy >Restrict it to ASN's that belong to Radio Groups / Clubs individuals >----- Original Message ----- >From: "Brian Kantor" <Brian(a)UCSD.Edu> >To: "AMPRNet working group" <44net(a)hamradio.ucsd.edu> >Sent: Friday, June 08, 2012 11:39 PM >Subject: Re: [44net] Use of the network > > >> (Please trim inclusions from previous messages) >> _______________________________________________ >> On Fri, Jun 08, 2012 at 07:53:10AM -0400, Ralph wrote: >>> If I am a Ham, and have the right to use the space, and it is provided to >>> me >>> over Non-Amateur-Radio means (i.e. Routed to me by my ISP over wireless, >>> fiber, tin cans and a string), then I feel that I can and will use it for >>> what I want. >> >> That is precisely why it is necessary to have contractual restrictions to >> keep the network limited to ham radio related activities. >> >> One proposal was that all endpoints must be ham stations or facilities >> primarily provided by and for hams. >> >> I rather like that; it's fairly non-restrictive and allows for just about >> any >> kind of transport or intermediate routing but should keep the netspace >> from >> being subverted to commercial interests. >> - Brian >> _________________________________________ >> 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

13 years, 7 months

1
0
0 0

Re: [44net] 44Net Digest, Vol 1, Issue 49

by Max Lock

Hi Eric, I've done a lot of work making openwrt based hotspot networks in the past. ddwrt is useful, but there's a couple of issues that come to mind. Firstly with ddwrt using openvpn you'd have to make changes to mirrorshades to support openvpn and do you really need the overhead of encryption? Secondly with ddwrt the ability to tune to the ham band is only possible by using a paid for version that has 'superchannel' functionality. It should be fairly simple to create an openwrt image that sets up an unencrypted tunnel to mirrorshades, however I've never toyed with setting odd frequencies on them. Also given that you wouldn't have unused packages installed you could use the space to install something amateur radio related. Finally how would you stop non-ham access? -Max G7UOZ. On Thu, 2012-06-07 at 12:00 -0700, 44net-request(a)hamradio.ucsd.edu wrote: > Has anyone used ddwrt, especially the vpn version to setup a tunnel to ucsd > > then run rip to get routing announcements? just sounds like a neat low > > cost way to get a gateway running. This would be trivial if one could run > > openvpn to mirrorshades. > > > > Eric > > AF6EP

13 years, 7 months

25
54
0 0

Quick Test Request

by John Ronan

Hi, I've got two machines running here on the, 44.155.6.225 and 44.155.6.226. I'd appreciate if someone on the 44-net could just check they can reach 44.155.2.226 for me please (it could be slow, machine is going an apt-get update at the moment). Also, would anyone be in a position to tell me what the best wireless mesh protocol to use is at the moment. These are two Icom ID-1 D-star radios. I've two more that two local hams are going to put running for me on high points and I'd like to run something 'mesh' on the nodes to allow me to get back to the gateway (225) from anywhere within range of any three? Regards John EI7IG

13 years, 8 months

5
13
0 0

Re: [44net] 44Net Digest, Vol 1, Issue 51

by kb9mwr＠gmail.com

I am also interested in implementing some sort of openVPN tunnel with RIP listener on a OpenWRT platform. It's been ages since we had any wormhole connectivity here in Wisconsin (Wigate/KB9BYQ days). And back then it really wasn't implemented correctly in my opinion. As many know, a few of us here in Green Bay, Wisconsin have been experimenting with non-traditional alternatives to AX.25. More recently the 420 MHz 802.11 options. What I really am waiting for is someone to design some amplifiers for these things. We have been using 900 MHz 802.11 with a 5 MHz channel width for some point to multipoint links. In our mobile tests on 900 MHz, the throughput suffers with the multipath from being in motion, etc. So be aware of that, 56 k will quickly be come 10k or worse. At 5 watts on 900 MHz, we manage to pull off 5 mile non-line of site omni-to-omni links with strong signals. A configuration conducive to a Mesh Network. On 900 MHz noise is a problem though, which also results in reduced throughput. So I'd like to be doing 5 watts on 420 MHz. The RFM12BP looks like a way to pull of 19 to 24 kbps on 70cm cheap. Amplifiers for this should be much easier. Steve, KB9MWR > Message: 1 > Date: Fri, 8 Jun 2012 11:00:30 -0800 > From: Eric Fort <eric.fort(a)gmail.com> > To: AMPRNet working group <44net(a)hamradio.ucsd.edu> > Subject: Re: [44net] (no subject) > > Why would I or anyone else for that matter use anything that slow over > wireless when multi megabit radios that will link reasonably long distances > can be had for $50-100ea. These radios connect via ethernet with no > special software. No I don't have any 56k radios on order, I don't see > them as worth the cost to salvage from the trash bin next door. > > Eric > AF6EP > > Message: 3 > Date: Fri, 08 Jun 2012 12:26:04 -0700 > From: David Josephson WA6NMF <wa6nmf(a)josephson.com> > To: eric.fort(a)gmail.com, AMPRNet working group > <44net(a)hamradio.ucsd.edu> > Subject: Re: [44net] (no subject) > > On 6/8/2012 12:00 PM, Eric Fort wrote: >> Why would I or anyone else for that matter use anything that slow over >> wireless when multi megabit radios that will link reasonably long >> distances can be had for $50-100ea. These radios connect via ethernet >> with no special software. No I don't have any 56k radios on order, I >> don't see them as worth the cost to salvage from the trash bin next door. > > Two reasons: long point-to-point hops and mobile. > > I can see a real utility for a 56k backbone with 100+ mile hops which > can easily be done on 420 with fewer complications (except in PAVE PAWS > areas) than on the higher bands. Likewise, mobile service with omni > antennas is practical over 20+ miles on 420. > > David WA6NMF

13 years, 8 months

3
2
0 0

Re: [44net] OpenVPN or *VPN

by K7VE - John

First I think the idea here is to get more ways into 44 than mirrorshades. If ISPs are willing to take delegations for CIDRs of 44 then that is one side of the formula. This may be a few or possibly one per /16, I don't think we should be propagating this all the way to /30 subnets. The other side is to bring in pockets of activity (LANs) into these "edge routers", which will often be VPN servers for tunnels from the LANs. The problem we have now is that almost all of the tunnel configuration and methods are tied to non-standard, uncommon, or ancient technology. We don't have to have just one VPN solution, e.g. it doesn't have to always be IPIP using JNOS, or even OpenVPN. It just has to be a VPN/Tunnel protocol that the edge router or routers support for those LANs connecting to them. OpenVPN, L2TP, MPLS, ... the key is that it is a standard, widely deployed, authenticated, and easy to setup. I can take $60 router off the shelf, provide a standard configuration and deploy it very quickly using L2TP. A new LAN would be able to take a script, plug in their credentials (for a primary and fallback edge router) and be up in short order, whether they are on a public / private (natted) address, static or dynamic. Not everyone setting up a LAN will be a network engineer, so we need recipes for some common "off the shelf" routing solutions that are pretty solid for someone following directions. ------------------------------ 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> On Fri, Jun 8, 2012 at 4:28 PM, Elias V. Basse III <kd5jfe(a)gmail.com> wrote: > (Please trim inclusions from previous messages) > _______________________________________________ > What about an ipip server that links openvpn to the mirrorshades ipip link? > > This would allow coexistence of both protocols. > > 73 de KD5JFE > Elias > > Sent from my iPhone > _________________________________________ > 44Net mailing list > 44Net(a)hamradio.ucsd.edu > http://hamradio.ucsd.edu/mailman/listinfo/44net >

13 years, 8 months

4
4
0 0

Re: [44net] directly routed subnets

by William P.J. Bressette

As well all of a advertised block must me advertised only from a single asn. This is where this will start to get tricky. Sent from my Windows Phone ________________________________ From: Michael Fox - N6MEF Sent: 2012-03-16 12:56 To: 'AMPRNet working group' Subject: Re: [44net] directly routed subnets (Please trim inclusions from previous messages) _______________________________________________ There are different levels of peering. The policies below describe tier 1/2 peering between the big guys. Most peering relationships are not at that level. Many small businesses have peering with more than one service provider. It's quite common. The current startup I work for has a /24 that they announce to their colo provider in San Francisco, as well as the ISP that serves their HQ location further down the peninsula. (The colo and their HQ are tied together as one ASN). 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 Tim Pozar Sent: Friday, March 16, 2012 9:43 AM To: AMPRNet working group Subject: Re: [44net] directly routed subnets (Please trim inclusions from previous messages) _______________________________________________ On Mar 16, 2012, at 8:20 AM, Brian Kantor wrote: > Perhaps I should start collecting AUPs from various sources rather > than having to create one from scratch. > > URLs to model AUPs would be appreciated. In concern of BGP peering... You can see some of the hoops that ARIN requires for an ASN at: https://www.arin.net/policy/nrpm.html See section 5 <https://www.arin.net/policy/nrpm.html#five> for ASN requirements. Certainly there are policies for peering that other ASNs. Some of these policies are good to look at for requirements for announcing address space. Some of the requirements are a bit onerous and don't apply. Comcast has their set of requirements at: http://www.comcast.com/peering/ Certainly things like "Applicant must operate a US-wide IP backbone whose links are primarily 10 Gbps or greater" should not be a requirement. But points like: * Applicant must have a professionally managed 24x7 NOC and agree to repair or otherwise remedy any problems within a reasonable timeframe. Applicant must also agree to actively cooperate to resolve security incidents, denial of service attacks, and other operational problems. or * Applicant must maintain responsive abuse contacts for reporting and dealing with UCE (Unsolicited Commercial Email), technical contact information for capacity planning and provisioning and administrative contacts for all legal notices. may be a good idea. The latter one would be needed to help resolve poisoning of address space and getting listed on various RBLs. Other sites that have peering requirements can be seen at: ATT - http://www.corp.att.com/peering/ Verizon - http://www.verizonbusiness.com/terms/peering/ AOL - http://www.atdn.net/settlement_free_int.shtml MFN/Abovenet - http://www.above.net/peering/ If folks want can make a stab at a draft for requirements for someone announcing 44/8 space. Tim _________________________________________ 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

13 years, 8 months

7
23
0 0

Trim Inclusions - PLEEEEASE

by Kutche, Jerry (Mitchell) USA

Planning on switching to digest mode, so I do not continue to get such an uncanny amount of emails per hour.. But even at that we need to remember to be considerate and TRIM inclusions.. Perferrably all the way out.. Or at least severely miniize the amount of carry over. Or else in a 24 hour period we can have a digest too big to want to swim thru.... Or possibly one that exceeds our email inbox size limit.. Thanks Everyone have a good weekend.. Jerry

13 years, 8 months

1
0
0 0

Re: [44net] dd-wrt setup for amprnet

by Eric Fort

Hope this gets through as it bounced after sending to the old address at cows.net. Has anyone used ddwrt, especially the vpn version to setup a tunnel to ucsd > then run rip to get routing announcements? just sounds like a neat low > cost way to get a gateway running. This would be trivial if one could run > openvpn to mirrorshades. > > Eric > AF6EP > > >

13 years, 8 months

4
3
0 0

Re: [44net] directly routed subnets

by Tim Osburn

Brian and All, I always thought it was a waste of a routable /8 to not have it routed on the Internet, otherwise why are people just not using IANA space instead? However, if it is to be routed on the internet I think some ground rules must be established of what is and is not acceptable and penalties for not following the rules and established guidelines. Additionally, and I bring this up again, a RWHOIS server should/must be used (tied in with ARIN on the 44/8 allocation) so that people can query specific address space that will return the contact/owner of whatever space is being advertised for whatever reason. Additionally, IRR entries should also be required for anyone wanting to advertise space via BGP. Those should be some common sence polices that need to be followed at the very minimum. Obviously nothing smaller then a /24 should be advertised on the internet as most Tier 1 carriers will block any address space that is smaller in their BGP configs. I don't know what the whole breakup of space looks like within each coordinator's /16 space (for those that have a /16 of space), but I would think there surely is space in each that could be a usable /24 or larger that could be utilized for that. Alternatively there seems to be a lot of space at the upper end of the 44 block that could be used for internet routed blocks if we wanted to use that first? IP Space justification will be whole issue within it's self as well, because if you only REALLY need /28 or /27 of IP's, one will still need to advertise a /24. Perhaps who ever advertises space via BGP should accept the condition that if only a portion of the advertise space is being used that you will accept and allow another person needing the available space so that it's not wasted. This could be tracked and allocated via the rwhois server in conjunction with entries in IRR. UCSD can still advertise the 44/8, and of course if anyone advertises a more specific route, that will be preferred of the larger aggregate. Be nice if we were all on a IRC chat channel to bounce ideas around? If anyone is interested, how about channel #44net on IRC server network freenode (irc.freenode.net). I'm on there now. Tim Osburn www.osburn.com 206.812.6214 W7RSZ On Tue, 6 Mar 2012, Brian Kantor wrote: > Date: Tue, 6 Mar 2012 11:14:57 -0800 > From: Brian Kantor <Brian(a)ucsd.edu> > Reply-To: AMPRNet working group <44net(a)hamradio.ucsd.edu> > To: 44net(a)hamradio.ucsd.edu > Subject: [44net] directly routed subnets > > I've gotten several requests for directly routed subnets (ie, BGP announced > CIDR blocks as subnets of 44/8, not tunneled) for ham radio use. These are > people who want to set up HSMM networks in the ham bands, D-Star > constellations, etc. > > I thought I'd ask folks what they think of the idea of setting aside part of > the address space for that purpose? > > What issues do you see arising from doing so? > - Brian > _________________________________________ > 44Net mailing list > 44Net(a)hamradio.ucsd.edu > http://hamradio.ucsd.edu/mailman/listinfo/44net >

13 years, 8 months

12
28
0 0

Using a cisco to do the tunnelling

by VK4FQ/VK4TTT Sam

Hey Guys We have a surplus of cisco routers with dsl wics due to an upgrade. We have put DSL into a few of our repeater locations and want to put packet (before the 12/13 storm season) I am looking for a config that will do the ip tunnel encap for 44 net. If you have done it please email me vk4fq(a)smellyblackdog.com.au with destructions please Samantha vk4fq/vk4ttt

13 years, 8 months

2
1
0 0

Fwd: [44Net] AMPRnet node/gateway in a box

by C.J. Adams-Collier

Re-send Sent from my PDP-11 Begin forwarded message: > From: "C.J. Adams-Collier" <cjac(a)colliertech.org> > Date: June 1, 2012 11:57:13 AM PDT > To: 44Net(a)cows.net > Subject: Re: [44Net] AMPRnet node/gateway in a box > > Give me your fedex account number and I'll have them shipped COD. Would you like me to put squeeze on a 512M flash and send along a 150G spinny disk for larger data? It's a 1U chassis: > > http://wp.colliertech.org/cj/?p=1165 > > There are about 20 left. Get them while they're hot. > > There's one serial console (RJ-45) exposed on the front panel. There's a header on the mobo that I could stick a secondary serial jack (DB9) onto and run it to the back panel. > > I'm on freenode as 'cj' and efnet as 'cjac'. I'll be working on getting these deployed to you next week. > > 73, > > KF7BMP > > > On Thu, May 12, 2011 at 10:57 AM, Eric Fort <eric.fort(a)gmail.com> wrote: > I've been thinking that a single box with: > > 3 (or more) ethernet ports > 1 serial port (emergency console) > a couple USB ports (for USB hub, USB serial ports, USB disk, Etc.) > 1-2 SD Card slot(s) > > that could be easily configured by menu or web interface and acted as a plug and play node/gateway for those wanting to join and contribute to AMPRNET would be a good thing. Hardware wise USB serial adapters could run legacy hardware such as TNC's, modems, and even do such functions as rotor control and radio tuning for sat links, etc. Ethernet would connect the box to the local subnet(s) and the internet. Ideally one could plug a TCP/IP host or network in one port ( the local net... generally a PC or Mac but it really wouldnt matter), The Internet on the second port, and the local AMPRNET RF WiLAN on the 3rd port. AX.25/ROSE/NetRom/etc connectivity could be handled over USB serial to a KISS TNC. > > Now, if such a box appeared for sale at the local amateur radio candy store or elsewhere what does it need on board as far as software and protocol support? What does it need to do and what additional optional tasks would be desirable for it to do? what should it NOT do? > > I can think of the following: > > Routing: > IPv4/IPv6 native > > RIPv2 > OSPF > (IS-IS) > legacy AX.25 support > > Tunneling: > GRE > IPIP > (ssh - the binaries will likely be there anyway for other uses) > (netcat - not the usual choice but handy at times) > > Services: (should these run on this box or a seperate box connected to the LAN) > > HTTPS - needed for config > ssh/scp - needed for config > DHCP/BOOTP - for configuring other clients > > SMTP, FTP, DNS, IRC/converse,BBS, SIP, etc servers - should these run on said box or be on another box on the LAN? What services should run where? > > > Anything else such a box should do to provide easy AMPRNET connectivity and participation? Please contribute your ideas, I'm thinking of doing this as a project. > > Eric > AF6EP > > >

13 years, 8 months

1
0
0 0

44net is not just for tunneling

by Lin Holcomb

> > I am still in the holding pattern while ya'll work out things, but I share > Ralphs frustration. I see tunneling as a project that uses 44net not the > whole 44net project. It seems to me that this has been confused by many > and sent the 44net down one road. We need some highways and not 2 lane > dirt roads, sorry but 1200baud or even 9600 baud is a two land dirt road > compaired to 10-300 meg connections I can offer I spoke to several groups > at Dayton and there are many others who would love to have use of the IP > addresses Dstar, highspeed packet ect. (not tunneling all thru UCSD) > > The inability to have routeabil addresses from the net back to the > 44net( or the lack of desire do to the slow speeds) raises this question > how is it that the current tunneling network would be different if the > 44.x.x.x was replaced with a 10.x.x.x and the route point at UCSD was a > 44.x.x.x ? Really what advantage does a non-routabile 44 have over a 10 > with the way you are currently using the network? > > From perspective I see no difference....If I cant see a difference > why would ICANN? Folks this is 1/255 off all of the ipv4 addresses in the > world we are talking about. This is like 220 in the 80s use it or loose > it. > > Lin

13 years, 8 months

18
51
0 0

Re: [44net] 44net is not just for tunneling

by Ronny JJULIAN

Well Brian. You have fun. Take my name and email off the site and remove me from the list. I don't agee with what you are doing and i really do not care anymore.. Use it or loose it. Keep your Kingdom. K4RJJ Ronny Sent from a cheap lil Android Tablet Brian Kantor <Brian(a)ucsd.edu> wrote: >(Please trim inclusions from previous messages) >_______________________________________________ >On Mon, Jun 04, 2012 at 11:19:34PM +0200, Bjorn Pehrson wrote: >> Any progress towards an AMPRNet AS, an acceptable use policy that >> not-for-profit research and education networks would accept for >> peering and a fair delegation rulebook with both rights, obligations >> and sanctions that prevents delegated addresses to be not used or >> misused? > >As has been discussed at length on this mailing list, there are >things that have to be done before we can start delegating subnets. > >What is going on is that we (our nonprofit) is attempting to get >organized. That means getting the legal documents handled, setting >up an advisory committee, work out an agreement with ARIN regarding >our delegation policies, writing an acceptable use policy and subnet >delegation contract, establishing procedures to evaluate delegation >requests, and figure out some way to fund all of this. > >To get an ASN we will need to negotiate with ARIN regarding their >standard AS contract; it appears to require those applying for an ASN to >relinquish a significant amount of autonomy, an amount that I believe is >incompatable with the way we wish to continue to operate network 44. > >Note also that an ASN costs $500 plus an annual maintenance fee. >The nonprofit is already about $1k in the hole, financed entirely by me. >We have no source of funds; everything is being done by volunteers >including a significant amount of pro-bono work by a networking-policy-savvy >attorney who has kindly volunteered her time even though she is not >a ham radio licensee (yet). > >I'd really like to continue to do this all for free to hams if we can. > >We're also working on a web-based replacement for the mail robots that handle >DNS and subnet/gateway matters. > >We need to set up an rwhois server to advise of the delegations. This is >an ARIN requirement and good network citizenship. It should be integrated >with the web system. > >So we've not been idle; things are slowly moving forward. > >We *will* be delegating subnets when the necessaries are in place. Sorry it's >taking so long. Anyone want to help? > - Brian > >PS: perhaps I misunderstand Internet peering, but I don't see any >need to get an ASN before delegating subnets. It might be convenient >but I don't think it's a prerequisite. Perhaps someone knowledgeable >could comment on this. >_________________________________________ >44Net mailing list >44Net(a)hamradio.ucsd.edu >http://hamradio.ucsd.edu/mailman/listinfo/44net

13 years, 8 months

2
1
0 0

Re: [44net] 44net is not just for tunneling

by Tim Osburn

Tim & anyone else I'm also at Nanog and if anyone else is please speak up, lets get together and have a short meeting! Tim Osburn www.osburn.com 206.812.6214 W7RSZ On Tue, 5 Jun 2012, Tim Pozar wrote: > Date: Tue, 5 Jun 2012 10:20:25 -0700 > From: Tim Pozar <pozar(a)lns.com> > Reply-To: AMPRNet working group <44net(a)hamradio.ucsd.edu> > To: AMPRNet working group <44net(a)hamradio.ucsd.edu> > Subject: Re: [44net] 44net is not just for tunneling > > BTW… I am here at NANOG and representatives are here from ARIN (John Curran, > David Huberman, Mark Kosters, Carrie Marino, Leslie Nobile). I would be > happy to chat with them if needed.

13 years, 8 months

1
0
0 0

Re: [44net] 44net is not just for tunneling and more

by K7VE - John

*Disclosure* - I am affiliated with NW Digital Radio, but my comments here concerning features, design decisions, product direction, availability, price, or delivery are not guarantees, announcements, or binding upon the company unless specifically stated as such. Someone brought up the UDR56K-4 radio announced at Dayton Hamvention® a couple of weeks ago. So let me list some parameters and answer a couple of questions: - The model announced is specified as a half duplex radio, running 25W on 70cm band. - It has an integrated computer running a standard Linux server (Debian Squeeze) with additional drivers specific to the radio. - The software platform is open source and developers are free to create their own protocols and applications - Additional hardware and options can be added via USB or 10/100 Ethernet. - There will be a daughter card option to hold a vocoder (AMBE family card will be available from NW Digital Radio) - AX.25 and D-STAR network stacks are under development and test, supporting applications that use those network stacks. - Modulation choices include GMSK, FSK, 4FSK, and possibly one or two additional choices. The modulation is performed in a high integration RF IC which talks through a bus directly at digital logic levels (no analog/base-band layer) - The RF IC can accept up to 100 Kbps with bandwidth profiles based on modulation choice. The US regulations limit operation to 56 Kbaud and 100 KHz bandwidth. Higher bit rates that meet those requirements can be supported up to the 100 Kbps rate. The developer/operator is responsible for insuring data rate / modulation choice meet the regulations where the radio is deployed. Having addressed the basics relative to the radio. The idea is to have a platform to support multiple applications including AMPRnet. There is an interest in other common air interface (CAI) protocols for passing various data including Net-44 packets, we have at least one 3rd party developer who wants to add a low-overhead IP transport to the radio. Yahoo! Forum for discussions relative to the UDR are at http://groups.yahoo.com/group/UniversalDigitalRadio One thing to remember is that for a given power one must choose between distance, reliability, and speed. For example, using 4FSK it may be possible to push the raw bit rate above 80 Kbps within 100 KHz, however it might be worth using a forward error correcting code reducing the effective rate back to 56 Kbps while reducing retries on a given path due to bit errors. I think that Net44 as a replacement for broadband service is not a goal that we should be seeking. In the wireless space there are plenty of consumer devices (Part 15 in the US) that can provide high-speed/local service, e.g. WiFi, or even point-to-point links on some paths. There are a lot of applications where repurposing consumer devices makes sense, e.g. HSMM on amateur bands, or very local mesh networks in urban areas. Conversely, there are many applications where longer haul, higher power, modest data rate service is a better choice and this is where Amateur Radio can fill a need. I agree we should work to multi-home Net-44 to the rest of the Internet, but I don't believe we should do this on a LAN level. I think at most it should be the 256 /16 subnets and probably many fewer than that. Local LANs can tunnel using newer tunneling protocols that can use a dynamic IP on at least one end of the tunnel to these BGP'ed routers (with fail-over between them for tunnels from LANs). There is no reason to use roll-your-own routers or protocols -- there are very capable routers with tunneling in the US$60 range that can get the connection over the Internet tunnel to the local LAN, then use our various RF interfaces (WiFi/HSMM, AX.25, DSTAR, ...) out to individual nodes. A did a presentation on this subject earlier this spring -- http://www.microhams.com/digitalconf2012/K7VE_N7IPB_RebootNET44.pdf ------------------------------ 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>

13 years, 8 months

2
2
0 0

Re: [44net] 44net is not just for tunneling

by Ronny JJULIAN

Lin why don't you ake the lead fo Ga? Simply volunteer and I won't oppose. K4RJJ Ronny Sent from a cheap lil Android Tablet Lin Holcomb <lin(a)n4yci.com> wrote: >(Please trim inclusions from previous messages) >_______________________________________________ >> >> I am still in the holding pattern while ya'll work out things, but I share >> Ralphs frustration. I see tunneling as a project that uses 44net not the >> whole 44net project. It seems to me that this has been confused by many >> and sent the 44net down one road. We need some highways and not 2 lane >> dirt roads, sorry but 1200baud or even 9600 baud is a two land dirt road >> compaired to 10-300 meg connections I can offer I spoke to several groups >> at Dayton and there are many others who would love to have use of the IP >> addresses Dstar, highspeed packet ect. (not tunneling all thru UCSD) >> > > >> The inability to have routeabil addresses from the net back to the >> 44net( or the lack of desire do to the slow speeds) raises this question >> how is it that the current tunneling network would be different if the >> 44.x.x.x was replaced with a 10.x.x.x and the route point at UCSD was a >> 44.x.x.x ? Really what advantage does a non-routabile 44 have over a 10 >> with the way you are currently using the network? >> > > >> From perspective I see no difference....If I cant see a difference >> why would ICANN? Folks this is 1/255 off all of the ipv4 addresses in the >> world we are talking about. This is like 220 in the 80s use it or loose >> it. >> >> >Lin > >_________________________________________ >44Net mailing list >44Net(a)hamradio.ucsd.edu >http://hamradio.ucsd.edu/mailman/listinfo/44net

13 years, 8 months

3
2
0 0

Re: [44net] 44Net Digest, Vol 1, Issue 43

by Max Lock

Hi John, Thanks for the slides, Is there a video of the presentation available anywhere I think it'd make some good viewing. Rebooting the AMPRnet is whats needed, new products like the UDR56k are a great idea and I'd expect to see some poor mans clones of its functionality following in time. Thanks to the internet the general level of data comms knowledge has improved in the last 20 years, and a resurgence in interest seems to be occurring. Me personally, I've got internet burnout. :) As regards to tunnelling, I thought it was policy that to tunnel to /44 you need a static IP I read somewhere. Technically of course it's possible to tunnel to any accessable IP, I subscribe to a dynamic DNS service to track my VPN end points for example. -Cheers Max. G7UOZ. On Thu, 2012-05-31 at 12:00 -0700, 44net-request(a)hamradio.ucsd.edu wrote: > > Message: 2 > Date: Wed, 30 May 2012 14:41:22 -0700 > From: K7VE - John <k7ve(a)k7ve.org> > To: AMPRNet working group <44net(a)hamradio.ucsd.edu> > Subject: Re: [44net] Some newbie guidance. > Message-ID: > <CAN77r3xdL9DQv3XFH331PQ+YdBa2MaTu6PBnWq1ehCrvYcdYuA(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Slides from a presentation I gave a couple of months ago > http://www.microhams.com/digitalconf2012/K7VE_N7IPB_RebootNET44.pdf > > Some of the tunneling protocols don't require a fixed IP -- I tunnel a /24 > network from a data center to my home (and also a portable subnet) using > L2TP. > > ------------------------------ > 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>

13 years, 8 months

6
5
0 0

Some newbie guidance.

by Max Lock

Hi All, I'm interested in building a tcp packet network for my local town. Theres no packet activity here, apart from aprs. The local club are generally focused on competitions, but there is a local hackspace in it's infancy with a number of people interested in doing 'something cool' with packet. So, I've been in touch with the UK ampr co-ordinator, and am now administering our local /24. Given I have a clean slate what subnetting approaches have people found that work well, maybe subnets for different technologies dstar, ip over x25 packet etc. In the UK I understand there's essentially no routing, but have read about routing being used in the US, what are the reasons? I don't currently have a fixed IP, so am currently unable to provide 44 net access to the rest of the world unless I can come up with something clever, or a fixed IP. Has anyone successfully implemented a workaround, maybe an ip tunnel from another host with a fixed ip? If anyone has any documents on any aspects of ampr network design, or links I'd be very interested in taking a look. I want to get as much right first time as possible. -Cheers Max G7UOZ

13 years, 8 months

2
1
0 0

Help please

by Jerry

Hello. Does anyone have a working JNOS2 autoexec.nos. running under linux RedHat Fedora 4 Looking for the following minimum. 1 RF port com 1 1 Ethernet lan port Converse server Net 44 access. I would like to use it as a reference and or modify for my use.. Many Thanks Jerry

13 years, 8 months

2
1
0 0

44 AMPR email list issues..

by David Ranch

Hello Everyone, I noticed two things today when trying to invite a prospective packet user into the AMPR group: 1. The mailmail list manager at http://hamradio.ucsd.edu/mailman/listinfo/44net isn't responding 2. It seems the http://wiki.ampr-gateways.org/index.php?title=AMPRnet_contacts still points users to 44Net-owner(a)cows.net --David

13 years, 8 months

1
0
0 0

Unsuscribe

by Joshua Fuller

Sorry if this hits the list

13 years, 8 months

1
0
0 0

Building block for rebuild of AMPRNET

by John D. Hays

A new digital radio was announced at Dayton - http://nwdigitalradio.com http://groups.yahoo.com/group/UniversalDigitalRadio ------------------------------ 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>

13 years, 8 months

1
0
0 0

Re: [44net] Network map of active AMPR stations -- Packet "proxy arp" in Linux and/or JNOS?

by Kutche, Jerry (Mitchell) USA

Many thanks.. I bet you are correct.. I will see if I can fix it on my end.. Have a nice day... Jerry

13 years, 8 months

1
0
0 0

Network map of active AMPR stations -- Packet "proxy arp" in Linux and/or JNOS?

by David Ranch

Hello AMPR folk, I'm curious if there is an map of *active* geo-ip located AMPR stations out there? Ideally, I'm thinking of something like the various CONVERSE maps out there .. for example: http://www.wwconvers.ampr.org/ . The Michagan AMPR people do have a live monitoring system but it's text based: http://server1.nuge.com/~drg/network.html and I'm specifically looking for a Northern California map. Maybe there is something like an MRTG system that actively probes these systems from say the AMPR hub in San Diego? I'm also curious if anyone has ever heard of the following: I'm going on a vacation this summer where I know there isn't any reachable packet systems (both APRS or known packet systems) due to the mountain terrain. I know because I was there last year and though I could hear very faint packet stations, nothing could be decoded. What *is* available here is the commercial cell network and what I was thinking was tethering my Linux machine to the cell IP network and running an AXIP/AXUDP tunnel to re-link into the fairly extensive 145.050 KB2KB packet network: http://varmintal.com/ahamp.htm . I don't think this would be too difficult but what I'm trying to figure out is if it's possible to have my Linux machine send beacons, netrom updates, etc. from my machine via a tunnel to a remote AMPR station (proxy arp if you will) and then have all those AX.25 packets broadcasted on RF from there. There are a few Northern Califnornia Linux-based stations I know of that are on AMPR with JNOS that might be willing to try something like this but I wanted to run it by the group to see if it's been done / impossible / etc. --David

13 years, 8 months

6
6
0 0

Re: [44net] 64.27.62.53

by Jim Fuller - N7VR

Ok Don, 64.27.62.53 has been axed. Jim Fuller N7VR -- http://www.n7vr.org International TCP/IP Gateways Robot Operator -- http://www.ampr-gateways.org MTAPRS NET Server Operator -- http://www.mtaprs.net CWOP-2 -- http://www.wxqa.com IRLP Node 3398 - http://irlp.fuller.net Original ARECC contributor

13 years, 8 months

2
1
0 0

fwding partners

by Glenn Bursell

my gate is back up and im looking for a few links and forwarding partners from around the globe sent me a note if anyone is insterested thanks Glenn - ka0mos/ve1

13 years, 8 months

3
2
0 0

bogus encap.txt entries

by Rob Janssen

There again are bogus entries in the encap.txt: ip route add to 44.131.211.1/24 via 91.84.215.75 failed ip route add to 44.136.155/22 via 203.26.188.134 failed ip route add to 44.22.0.136/29 via 64.27.62.53 failed All of them specify incorrect subnets. Please make sure that all bits outside the subnet you are masking are zero! So, the first entry should be 44.131.211.0/24 instead of 44.131.211.1/24 Note that while JNOS may accept such entries, they are not correct and the Linux kernel will reject them. It also appears that the first two entries do not have any hosts in the ampr.org DNS within that address range. Note that only traffic for addresses that have a DNS entry is forwarded. Rob

13 years, 8 months

7
12
0 0

Jnos 2 Help

by VK4FQ/VK4TTT Sam

Guys Having issues attaching axip and axupd tunnels with the lastest version of jnos. If anyone has a working config I could use as a reference please email me ALso looking for examples of forward.bbs when forwarding woth a fbb system would also be helpful Thankyou in advance Samantha vk4ttt/vk4fq vk4fq(a)vk4fq.com

13 years, 8 months

2
1
0 0

Encap File

by VK4FQ/VK4TTT Sam

Hey Guys Had to rebuild our packet box after the storm season. I am missing the details for others we shared mail and netrom etc with Could you please send the info to vk4fq(a)vk4fq.com I am aslo looking for an encap.txt file if someone can send me a recent one please. Samantha VK4FQ/VK4TTT Cairns

13 years, 8 months

1
1
0 0

Setting up JNOS

by Elias V. Basse III

We are currently setting up three Jnos nodes in louisiana in districts 1 and 9 one will be at a tower site with no Internet for tunneling. This is our first adventure in setting up jnos outside of my testing system. Whom is responsible for tunneling and what tips can anyone provide regarding setting up the Internet connected nodes to tunnel and routing those that are not connected to the Internet to the 44 net backbone. I am looking for some documentation to pass to my district 1 and 9 coordinator as he would like to get started reading and familiarizing before I can assist in configuring. He is a Cisco certified engineer of 15 years so he grasps ip routing concepts which is a plus! Best regards, Elias Basse KD5JFE Sent from my iPhone

13 years, 9 months

1
0
0 0

tnos help

by Glenn Bursell

so i am attempting to set my gateway back up again and having issues attaching tnos to linux starting from scratch and have forgotten much over the last couple years :( running fedora 4 and tnos 2.40 any assistance would be greatly appreciated thanks in advance Glenn - ka0mos/ve1 feel free to contact me off list

13 years, 9 months

3
3
0 0

Robot Address for Ampr.org

by VK4FQ/VK4TTT Sam

Guys What is the email address for the robot for updating zone information? Sam Vk4FQ/VK4TTT

13 years, 9 months

4
6
0 0

Amprnet

by Jerry

Brian, Can you send me the email or instructions for AMPR assignments. Not used it in some time and forgot where I put them.. There has been new life in the desire to join Net44 here in Indiana.. 73 Thanks Jerry

13 years, 9 months

1
0
0 0

nntp access via browser / html

by Pedro Converso

Hello all, I like to share recent application that allows via HTML access to jnos2 nntp news. It does reading, replying, posting, etc, support multilanguages, additionally some external usenet groups have also been added with same functionality, including thread support. You can try at http://lu7abf.org.ar/news . I am running jnos 2.0k on ubuntu 11.04 with bbs, http and nntp support, handling VHF and UHF radio ports, besides bbs access, aprs and fwd via radio and internet. Newsreader used under jnos www is PHP newsreader 2.6.6 available on http://sourceforge.net/projects/pnews/ As Newsreaders operate under newer nntp RFC 3977, there are needed some commands not available on nntpserv.c , thus I rewrite and share some nntpserv.c recoding, available on http://lu7abf.org.ar/nntpserv.c Several users are trying and confident with the application, it seems to work ok, furthermore it is more fun and easy to access news this way. If there is need for details, questions or coments they are welcome. Appreciate reading and the work and effort of all that contributed to have this wonderfull piece of ham software that is nowadays jnos. Best 73, lu7abf, Pedro Converso pconver(a)gmail.com

13 years, 9 months

1
0
0 0

Fwd: Re: AX25 and related software's future in Debian

by David Ranch

Hello Everyone, There is a thread going on in the linux-hams@vger list where the Debian folks are thinking about renaming the long standing AX.25 "node" program in favor of the new Node.JS program as well as thoughts of deeper changes to the AX.25 packages. http://www.spinics.net/lists/linux-hams/ Though Debian is a smaller distribution, it's influence is far reaching to many Debian-related distros (Ubuntu, Mint, etc.) The current HAM packages maintainer is seeking input and what better list to get potential Linux feedback than the AMPR list! I encourage you to join the conversation and be heard! --David -------- Original Message -------- Subject: Re: AX25 and related software's future in Debian Date: Fri, 04 May 2012 11:14:24 -0400 From: Patrick Ouellette <pat(a)flying-gecko.net> To: Dan Smith <dsmith(a)danplanet.com> CC: linux-hams(a)vger.kernel.org, debian-hams(a)lists.debian.org, ralf(a)linux-mips.org, ax25(a)x-berg.in-berlin.de (I added Ralf DL5RB and Thomas DL9SAU to the Cc: line. They are the upstream maintainers of ax25 and I am not sure if they have seen the thread/discussions) On Fri, May 04, 2012 at 07:06:33AM -0700, Dan Smith wrote: > > > So, what inspiration can you give me to keep me from packing up the tent? > > Some of us continue to develop and deploy new systems based on this > stuff. Linux provides the most modern way to integrate AX.25 with other > IP networks (IMHO) and Debian provides a good platform on which to > build. Yes, you and I can install our own stacks, but if it goes away > from the base distro, it will be harder to encourage other folks to do > the same. > Dan, Playing Devil's advocate - the argument has been put forth in the "other discussion" that according to popcon (the Debian popularity contest), node has 81 installs, and 17 reporting as "active" while the nodejs package has 720 installs with 163 reporting as "active." So their conclusion is the node package is only used by a small community. Looking at the ax25 packages: libax25 - 234 installs/ 49 active ax25-tools - 74/19 ax25-xtools - 45/6 ax25-apps - 74/17 other ham packages depending on libax25: xastir - 89/16 aprsd - 33/13 ax25mail-utils - 22/4 fbb -16/3 linamc - 13/0 and a couple of other ham packages: hamlib - 349/119 qsstv - 80/8 gmfsk - 64/10 fldigi - 113/24 xlog - 72/12 gpredict - 650/90 for comparison, the bash shell - 121423/110245 judging by these numbers (and let me make it CLEAR I do not put much stock in them personally since the package does not have to be installed, the machine has to have an internet connection, and the file system has to record atime - so low power systems or ssd drive systems with the mount option noatime don't count) hamlib *might* currently be *safe* in terms of keeping it's name, and clearly is used by others. The other issue, the one I was thinking of was the active user counts. With the exception of hamlib and gpredict they are all low double digit or even single digit numbers. Even if I believe there are many more users of the software, I have no way to prove it. I know there are many Debian and Debian based systems running ax25. Unfortunately "the squeaky wheel gets the grease" and the ax25 users haven't been squeaking. Flawed as it is, the "other side" will continue to use the only tool they have - popcon - to justify their actions in disregarding the place of long term packages in the distribution in favor of the next new / hot thing. I would like to run my tried and true systems as they are, and not have to reinvent the wheel and debug scripts every few years when this issue comes up again. The same thing happened with listen in Debian, so now it is axlisten while the music player now has the executable named listen. Everyone agreed then that "listen" was a generic name and should not really be used, and yet it is. You claim the existence of the packages in Debian encourages others to try ax25, if this is so where are these people? Pat -- To unsubscribe from this list: send the line "unsubscribe linux-hams" in the body of a message tomajordomo(a)vger.kernel.org More majordomo info athttp://vger.kernel.org/majordomo-info.html

13 years, 9 months

1
0
0 0

Introducing YaCy Searchengine to HAMNET

by Michael Przybilla

Hi Folks I'd like to introduce a YaCy System as a distributed search engine for the HAMNET The important information on how to use it can be found here on our Webserver at DB0FHW: http://www.afu-ag.de/joomla/index.php?option=com_content&view=article&id=83… If you let Google translate the page, unfortunatelly, you do not get a very good translation... http://translate.google.de/translate?sl=de&tl=en&js=n&prev=_t&hl=de&ie=UTF-… ... So I'll explain it in a bit more detail. YaCy is a free dezentralized search engine that anyone can use to build a search portal for their intranet General information can be found here: http://yacy.net/en/ ... So lets consider HAMNET as a kind of intranet. We defined a root.unit for the system at DB0FHW, which has a quite good connection to the german HAMNET, an anybody can now connect a peer to this root.unit This unit is shared to all peers, so the network will stay alive, even if DB0FHW goes down. Peers temporarely connect each other like a full mesh, so a peer only needs to know one other peer to find its way back into the network. How do you connect peers now: 1. Download and install YaCy http://yacy.net/en/index.html 2. Do not start the YaCy Service, yet. 3. Edit the line "network.unit.definition" in your file "defaults/yacy.init". It should point to this URL now: http://yacy.db0fhw.ampr.org:8090/yacy.hamnet.unit 4. Start the YaCy Service Philosophy: There sould be (minimum) one YaCy peer in each AS of the HAMNET, crawling the Servers INSIDE ist own AS! How often you want to crawl is your free choice. Just depending on the changes of the servers content. It it holds "hot news", you may host you yacy peer quite close to it an crawl every hour. If content changes weekly, crawl weekly... (if you have a huge AS, you may have more peers and define which of them is crawling which server) So... Sounds not that hard at the end ;-) Give it a try 73 Micha, DD2MIC

13 years, 9 months

1
0
0 0

WI Domain cleanup

by kb9mwr＠gmail.com

Hello, Thought I'd introduce myself. I have taken over for as the regional IP coordinator for Wisconsin and the Upper Peninsula (44.092/16). I wrote a script to help identify expired callsigns, and have since removed those entries for my area. This script my be handy to other coordinators: http://pastebin.com/d0HFmcG5 I made all attempts to not delete any active domains. If anyone is experiencing a problem please contact me. Steve Lampereur, KB9MWR

13 years, 10 months

3
4
0 0

Re: [44net] WI Domain cleanup

by kb9mwr＠gmail.com

Rob, It isn't meant as an automated tool. It was to aide me in lookup of calls. It outputs a list of invalid calls, which I manually reviewed. Here in the US, when you lookup a call that has been changed, the databases reference that. ex: http://callook.info/n9nof What you describe sounds like a headache to keep track of.

13 years, 10 months

2
1
0 0

Re: [44net] Slides from Presentation

by Kenny Richards

We shot video of the presentations last week, when we get them processed and posted, I'll make sure the link gets sent out to the group. 73, Kenny, KU7M > Message: 1 > Date: Thu, 5 Apr 2012 11:23:43 -0700 > From: "John D. Hays" <john(a)hays.org> > To: AMPRNet working group <44net(a)hamradio.ucsd.edu> > Subject: [44net] Slides from Presentation > Message-ID: > <CAN77r3xzhdtYrJLZYj3LYM0H3Recxii3-3AgofVkyyiKPbWOGQ(a)mail.gmail.com > > > Content-Type: text/plain; charset="utf-8" > > http://www.microhams.com/digitalconf2012/K7VE_N7IPB_RebootNET44.pdf > > ------------------------------ > 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> >

13 years, 10 months

1
0
0 0

Slides from Presentation

by John D. Hays

http://www.microhams.com/digitalconf2012/K7VE_N7IPB_RebootNET44.pdf ------------------------------ 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>

13 years, 10 months

3
2
0 0

WWConvers Australia carns ???

by Janusz Przybylski SP1LOP

Hi Sam VK4FQ I ask look on side: http://www.wwconvers.ampr.org and write them for cairns all data not to be anonymous -- 73 de Janusz / SP1LOP ===== Janusz J. Przybylski, SP1LOP ========== Poland AmprNet Co-ordinator [44.165.0.0/16] =============================================

13 years, 10 months

1
0
0 0

Re: [44net] directly routed subnets

by lleachii＠aol.com

All, Many have posted good responses on what would be needed to continue this project. I don't want to repeat any good suggestions (which I am also re-reading); but wanted to add a few; as I originally requested a subnet for the purpose of peering with Amateur Digital Radio Communications, or up to consideration of a Layer 1 connections to PoPs (I am working on such arraignments for our area using multi-homed non-commercial means). I have polished up on my BGP routing concepts and found these things: - in the MDC section, we would be seeking local peers via other non-commercial backbones - Doing BGP, the assumption we were to arrange at least layer 1 connectivity (via wireless and/or terrestrial [our area is fiber or greater to peer] which we're working on), at least back to Brian, this will require an AS Number - the concern in my area, want to pursue non-commercial means of announcement, redundancy to the non-commercial/commercial backbone, etc, in case the commercial network went down - Internet2.edu is being built out from stimulus funds, it is primarily non-commercial - just a thought, and a path we're looking into - I am willing to assist in this endeavor, and would like to sit-in on a conference call, if convened - There are other networks I'm sure are willing to carry a VLANs over their fiber - BGP to a PoP for most who wishes to peer with us would require us to really lobby our CFR Title 47 §97.1(a), that we have other Peers willing to provide Layer 1 Transport (working on this) - I see no need for us to work seperately, and wanted to mention this Anyone interested in being homed with another Autonomous System, please consider working with together on a National Amateur Wireless Society, if we receive International Interest, we may have to see other regional interest. Also, would a regional authority be willing to donate us an AS number (made requests)? ~73, Lynwood KB3VWG

13 years, 10 months

2
2
0 0

Re: [44net] Mini ATX Intel BOXD525MW Intel Atom D525

by lleachii＠aol.com

I'm also using a standard Ubuntu Linux Server 11.10 using rip44d and a Web Application providing a GUI named Webmin. This is a quick overview on setup. This setup can be done with telent and SSH; for simplicity of those who know the command line syntax, I will omit the necessaries. 1.) - with IP forwarding (Routing) enabled in /etc/sysctl.conf # Uncomment the next line to enable packet forwarding for IPv4 net.ipv4.ip_forward=1 2.) - I installed webmin (a Web GUI application for servers) package to better enable on the fly IPtables Firewall configurations, NAT, masquerade, etc. (these configurations allowed me to have this server as router for my 44.60.44/24 subnet over AMPR, while having the ability to also have a private 192.168/24 subnet that uses my standard non-tunneled gateway IP address from my ISP. PE1CHL recommended table-based policy routing; it configures any 44/8 address to use a routing tabled named "44," all other traffic is routed on main. If you setup this router to use NAT or Masquerade for a private network using your ISP's gateway, there will also be entries in the "nat" table. An edit to the rip44d script is necessary to place the 44/8 routes into a routing table named "table 44." 3.) - eth0 was configured at setup as the device connected to the Gateway address. 4.) - In this example, eth1 is the Ethernet interface that will be used as you LAN side providing your 44 Addresses (in this example 44.128.0.0/24) of the router connection (if you do not have access to another NIC, you may also want to set this up virtually to the address on your LAN if this is not the routing device for your physical network). Interface tunl0 is the default Linux IPIP encapsulation tunnel. The example/testing subnet 44.128.0.0/24 will be the subnet assigned to the gateway on tunl0 and eth1 used here. 5.) - with the help of Brian and PE1CHL, I then created a script named /usr/local/sbin/startampr to run on boot (it can be setup to run at boot in the webmin GUI under "Bootup and Shutdown" ### Enables AMPR IPIP Tunnel Interface modprobe ipip ip addr add 44.128.0.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.128.0.0/24 on main route table ip rule add to 44.128.0.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 ### this can be omitted if your device will not provide separate local traffic - KB3VWG - This adds a route to the local subnet on the 44 route table ip route add 192.168.0.0/24 dev eth0 table 44 ### Begins the rip44d Router ./usr/local/sbin/rip44d_table44 -a <my public gateway IP> -p <the password> < /dev/null & 6.) Table rip44d_table44 is a script editing the rip44d file to place the AMPR routing table into "Table 44": 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"; 7.) The routers 'main' Firewall Accept If state of connection is ESTABLISHED Accept If state of connection is RELATED * Accept If protocol is ICMP and ICMP type is echo-request * Accept If protocol is UDP and destination port is 33434:33534 + Accept If protocol is TCP and destination port is 10000 + Accept If protocol is UDP and source is 44.0.0.1 and input interface is tunl0 and source and destination ports are 520 + Accept If protocol is TCP and destination destination port is 22 (if you have other services on your Router machine, you would accept their IP's, source, destinations, etc. here) + - enables: webmin, rip44d and SSH respectively, you may further restrict this access to SSH or Webmin configuration by specifying allowed hosts, subnets, etc. 8.) IP Forwarding [the Router's] Firewall Accept If state of connection is ESTABLISHED Accept If state of connection is RELATED * Accept If protocol is ICMP and ICMP type is echo-request * Accept If protocol is UDP and destination port is 33434:33534 Accept If source is 44.128.0.0/24 Accept If source is 192.168.0.0/24 (if you have services on devices inside your subnet, you would accept their destination IP's ports, source, destination ports, etc.) 9.) Network Address Translation Firewall (only needed if routing traffic from a private network [eg 192.168.0.0/24] not carrying 44 Traffic) Accept If source is 192.168.0.0/24 and destination is 44.128.0.0/24 Masquerade If source is 192.168.0.0/24 and destination is 0.0.0.0/0 Accept If source is 44.128.0.0/24 Accept If destination is 44.128.0.0/24 10.) as you create AX.25 interfaces, etc, ensure you enable those protocols, etc in the firewalls. NOTE: Accepting echo-request and protocol is UDP ports 33434-33534 enable Unix and windows based ping and traceroutes from the Internet, you can also place further restrictions on those rules. 11.) Typing the command # ip route list table 44 default via 169.228.66.251 dev tunl0 onlink <between here should be many lines of 44.x.x.x direct IPIP Encapsulated routes that are populated by rip44d from 44.0.0.1 over the tunnel (e.g. '44.x.x.x/x via x.x.x.x dev tunl0 onlink window 840')> 169.228.66.251 dev eth0 scope link 192.168.0.0/24 dev eth0 scope link ~73, KB3VWG

13 years, 10 months

2
1
0 0

Re: [44net] directly routed subnets

by lleachii＠aol.com

All, I actually had a thought on this before I read the current line of discussion. Alot has been highlighted on the nature of a 501(c)3 and what it can and cannot do (feel free to read up on the IRS.gov publications). A 501(c)7 is also a route we may wish to take (depending on California Law and if the filing for determination process had not already proceeded). I also noted that keeping it for Amateur use by Hams is a very good idea. Also recall that we need to keep the network flexible, as testing and development of new protocols and types of equipment, etc. is also something that may become of interest in the future. Also, if you are going to announce space, I am capable of having it housed; so agreements regarding equipment, etc. would be on an Intergovernmental network in my area that RACES and local Emergency Radio Foundation will petition for a seat on, we don't happen to have any carrier-grade network equipment in our shacks on the East Coast (lol).. HSMM-MESH seems like something we want to experiment on right now. In addition, we peer with non-commercial networks; NetworkMaryland is the ISP that we wish to approach for holding an announcement. And it will be Internally BGPed to my County. I'd like to talk with my State Coordinator about this. I know that we are a network neighbour to the Internet2.edu backbone and other carries as well. ~73, Lynwood KB3VWG 44.60.44/24

13 years, 10 months

15
28
0 0

directly routed subnets

by Brian Kantor

I've gotten several requests for directly routed subnets (ie, BGP announced CIDR blocks as subnets of 44/8, not tunneled) for ham radio use. These are people who want to set up HSMM networks in the ham bands, D-Star constellations, etc. I thought I'd ask folks what they think of the idea of setting aside part of the address space for that purpose? What issues do you see arising from doing so? - Brian

13 years, 11 months

8
9
0 0

Problem register gate - bad password..

by Janusz Przybylski SP1LOP

Hi N7VR I have to alter for Gateway IP I send mail there now copies, that bad password I ask about switch because your mail server n7vr throws aside my mail's <<< 450 4.7.1<n7vr(a)n7vr.org>: Recipient address rejected: IP still greylisted - Please try again later <n7vr(a)n7vr.org>... Deferred: 450 4.7.1<n7vr(a)n7vr.org>: Recipient address rejected: IP still greylisted - Please try again later -- 73 de Janusz / SP1LOP ===== Janusz J. Przybylski, SP1LOP ========== Poland AmprNet Co-ordinator [44.165.0.0/16] =============================================

13 years, 11 months

1
0
0 0

Re: [44net] netalyzr.icsi.berkeley.edu and packet loss

by lleachii＠aol.com

Bill, Thanks, I have installed multiple versions of JRE, I'm currently using Oracle JRE 1.7.0_03, still a connection reset to the analyser and any pages served on the domain http://netalyzr.icsi.berkeley.edu So, it's not simply a Java issue, as accessing non-Java content returns the same error. I'm using Linux w/ a firewall, so no Anti-Virus/Malware running preventing the connection. I can browse to the page if I connect the device a the non 44 node at my home QTH. I should note all other sites needing JRE to run (such as the Test your Java Page) work perfectly fine on all other network connections, all devices, with all versions of JRE tested, this only occurs if the device is connected to 44net. I just wanted to verify that the results you noted to me were obtained over the 44 connection before I contact Berkley.edu about inability to access the tool. ~Lynwood KB3VWG

13 years, 11 months

2
1
0 0

AMPRNet activity in Sweden?

by Brian Kantor

I've received a request regarding AMPRNet activity in Sweden. The email address I have for the coordinator there dates from back in 2000 and is no longer valid. There are over 1000 DNS entries for the 44.140 Swedish subnet; surely somebody must still be active. Any information would be appreciated. - Brian

13 years, 11 months

3
2
0 0

netalyzr.icsi.berkeley.edu and packet loss

by lleachii＠aol.com

All, Does anyone receive connection reset when navigating to http://netalyzr.icsi.berkeley.edu I wanted to examine my connection (and perhaps determine the source of my random packet loss [between 5-10%]). ~73, Lynwood KB3VWG

13 years, 11 months

2
1
0 0

Re: [44net] Intermittent host connectivity issues

by Chris Maness

On Sun, Feb 26, 2012 at 3:44 PM, Chris Maness <chris(a)chrismaness.com> wrote: > On Sun, Feb 26, 2012 at 12:01 PM, Raymond Quinn <w6ray(a)sbcglobal.net> wrote: >> Hmmm. I see you have a link with Brett, WA7V. >> >> He also has static addresses, and was able to assign a commercial IP address >> to his linux box, as well as his NOS side. >> >> You might want to consult him on how that is done. >> >> In the mean time, does your JNOS have a LAN address of 192.168.x.x ?? >> >> It is behind a DSL Modem/Router. It is a 2wire. However, I have 5 static >> IPs. It does not allow me to use one of the public IPs for Jnos. It does >> not add that IP to the local network list for configuration, and therfore >> does not permit traffic to Jnos. I therfore had to use the munge script to >> build tunnels in Linux. This is ok, because it does protect Jnos from >> attacks. >> >> >> Chris, >> >> It appears that you have the same or quite similar setup that I have. I have >> my Linux box with a public static IP address and use that in the POINTOPOINT >> line. Eventually, the Linux box will appear in the 2wire and when it does, >> should automatically allow all traffic to that static address. > > It does exactly that. > >> >> (Of course, at present JNOS is locking up after a few hours, but that is >> unrelated) >> >> If you don't hear from Brett, I am willing to share what I have worked out. >> I still have more to do, but it may get you started. As always, make sure >> you make a backup of your current setup should it not work as mine does. >> > > It works just fine save one host on AMPR-NET. I wouldn't care save he > is my friend and one of the closest *NOS BBS to my site. > > I had also been in touch with AT&T customer service. The suggested I > purchase a Motorola router from them. I wish my Linux box was back > behind a Cisco on a commercial T1 like it was in the beginning. I had > direct 44net-to-inet connectivity. However, the AT&T network is > controlled by the packet Gustapo goose stepping with their tight > firewall rules. I guess that is good for the brain dead masses, but > it kind of makes playing with the stuff we do a pain in the toosh. > > Thaks es 73's > de Chris KQ6UP My Linux box can ping his Linux box, so that is good. I am not sure I have the whole doted quad with a forward slash business down. I think this is his encap.txt entry: route addprivate 44.16.2.32/27 encap 173.60.166.190 Since I believe that 44.16.2.46 is included in that subnet. Is the above subnet 44.16.2.32-64? Thanks, Chris Maness

13 years, 11 months

3
4
0 0

test

by Rob Janssen

test (sorry folks)

13 years, 11 months

1
0
0 0

Re: [44net] Intermittent host connectivity issues Was: New to the Group

by William Lewis

Hmmm. I see you have a link with Brett, WA7V. He also has static addresses, and was able to assign a commercial IP address to his linux box, as well as his NOS side. You might want to consult him on how that is done. In the mean time, does your JNOS have a LAN address of 192.168.x.x ?? B At 10:42 AM 02/26/12, you wrote: >On Feb 26, 2012 10:20 AM, "William Lewis" ><<mailto:ec@n1oes.org>ec(a)n1oes.org> wrote: > > > > Chris: > > > > Is your station by chance sitting behind a home internet router? > >It is behind a DSL Modem/Router. It is a 2wire. However, I have 5 static >IPs. It does not allow me to use one of the public IPs for Jnos. It does >not add that IP to the local network list for configuration, and therfore >does not permit traffic to Jnos. I therfore had to use the munge script >to build tunnels in Linux. This is ok, because it does protect Jnos from >attacks. > >Thanks, >Chris KQ6UP >_________________________________________ >44Net mailing list >44Net(a)hamradio.ucsd.edu >http://hamradio.ucsd.edu/mailman/listinfo/44net

13 years, 11 months

3
2
0 0

Re: [44net] Intermittent host connectivity issues

by Chris Maness

On Sun, Feb 26, 2012 at 11:34 AM, William Lewis <ec(a)n1oes.org> wrote: > > Hmmm. I see you have a link with Brett, WA7V. > > He also has static addresses, and was able to assign a commercial IP address > to his linux box, as well as his NOS side. > > You might want to consult him on how that is done. > > In the mean time, does your JNOS have a LAN address of 192.168.x.x ?? > > B No, it does not have a 192.168.x.x address. If a host makes a DHCP request on the local lan, the router leases 192.168s and does NAT for them. I have configured the linux box with two IP's bound to the ethernet card 76.238.148.147 and 192.168.1.33. That way I can build static routes in all my desktops and laptops to be able to reach JNOS directly. I can connect with everyone accept for K6HR. It looks like our gatway PUBLIC IP's are not talking. If I try to telnet to my Linux box I get: tel 76.238.148.147 Trying... The escape character is: CTRL-T *** busy from 76.238.148.147:telnet Telnet is enabled as a service on my Linux box. I had noticed this error from almost everyone all the time when I tried to set up JNOS with a public IP. That is why I had set up my gateway with Linux doing the IP over IP tunnels. Now it is working with 99% of the hosts. Chris

13 years, 11 months

1
0
0 0

Intermittent host connectivity issues Was: New to the Group

by Chris Maness

On Feb 26, 2012 10:20 AM, "William Lewis" <ec(a)n1oes.org> wrote: > > Chris: > > Is your station by chance sitting behind a home internet router? It is behind a DSL Modem/Router. It is a 2wire. However, I have 5 static IPs. It does not allow me to use one of the public IPs for Jnos. It does not add that IP to the local network list for configuration, and therfore does not permit traffic to Jnos. I therfore had to use the munge script to build tunnels in Linux. This is ok, because it does protect Jnos from attacks. Thanks, Chris KQ6UP

13 years, 11 months

1
1
0 0

Re: [44net] New to the Group

by William Lewis

Chris: Is your station by chance sitting behind a home internet router? At 07:57 AM 02/26/12, you wrote: >I can't connect or ping k6hr.ampr.org, nor can he ping me. > >I can ping and connect to GVCITY.ampr.org, but pinging towards my side >is flakey for him.

13 years, 11 months

1
0
0 0

New to the Group

by Chris Maness

Hello everyone, I am new to the group. I am the sysop of a new BBS kq6up.ampr.org. I just recently got back in to packet radio, and found a lot of renewed interest in packet radio in my local area. I decided to put up another JNOS BBS. It has been about 10 years since I have had a BBS. I have had more users in the past month (from the radio port) than I did over entire lifetime of my last BBS. I can connect to almost everyone that I have tried to in the ampr-net world. I am building my tunnels in Linux. I am having connectivity issues with two host (both have fresh encap.txt files). I can't connect or ping k6hr.ampr.org, nor can he ping me. I can ping and connect to GVCITY.ampr.org, but pinging towards my side is flakey for him. Should I try running RIP and forget about it, or are these problems fairly easy to track down and fix? Thanks, Chris Maness

13 years, 11 months

1
0
0 0

On the Issue of Subnets

by Geoff Joy

I wrote a paper back in the 1995-1999 time frame when packet was fairly active in my area regarding when and why to subnet. I received about an equal number of complaints from the linear-allocation advocates versus the subnetting advocates with good reasons on both sides for doing one or the other. I have searched my old hard drives for my original document but I can't seem to find it so I will outline the basic scheme again. My first plan was to dedicate bits in the address plan for geography/frequency and other factors but Brian talked me out of making any plan more complex than it already was. He also informed me of his reservation of the first 2 bits in the third octet for his use in future, something I was unaware of when I assumed the post. This made the CIDR mask 44.18.0.0/18 instead of the expected /16. This gave me effectively only 6 bits in the third octet to play with. Next came the question of how big to make the subnets. I don't have multiple counties to play with and I don't coordinate a whole state so topologically my region is pretty flat, being two counties, but still geographically very large, San Bernardino being the largest county in the U.S. but sparsely populated. Considering the population of hams in the region and the number of hosts addresses within 44.18/16 I didn't expect to have a problem running out of addresses no matter what scheme we chose. I was pretty much stuck with subnet 0, being the linear assignment scheme I inherited from the previous coordinator and we simply followed the pattern initiated in Los Angeles County where the ham population was more active and dense. My research into the RFCs and the nature of subnets and CIDR masks led me to a proposal to mask the subnet bits downward and the host bits upward, I don't recall the source of the document at this time but it might have been an RFC. Thus, the zeroeth subnet could stay in place as two-meter and mobile nodes and the _first_ subnet would be 32, not 1 as you might expect in a linear scheme. The bits map as follows: 44.18.0.0/18 The S.B. & Riverside Co. Group 6 bits reserved for CIDR subnets within the group. c = CIDR, x = hosts 00101100.00010010.00cccccc.xxxxxxxx The CIDR mask for the subnets becomes 44.18.0.0/24 and the total number of subnets is 64. The CIDR bits are allocated in sequence from MSB to LSB, thus: Subnet Bitmap 0 00101100.00010010.00000000.xxxxxxxx 44.18.0.x/24 1 00101100.00010010.00100000.xxxxxxxx 44.18.32.x/24 2 00101100.00010010.00010000.xxxxxxxx 44.18.16.x/24 3 00101100.00010010.00110000.xxxxxxxx 44.18.48.x/24 4 00101100.00010010.00001000.xxxxxxxx 44.18.8.x/24 5 00101100.00010010.00101000.xxxxxxxx 44.18.40.x/24 ... 63 00101100.00010010.00111111.xxxxxxxx 44.18.63.x/24 By growing the subnets downward and the hosts upward linearly, if a subnet were to become overpopulated with hosts, it can expand upward into another subnet: 2 00101100.00010010.00010000.11111111 44.18.16.0/24 rolls over into x 00101100.00010010.00010001.00000000 44.18.33.0/24 I then becomes possible to allocate entire subnets to a single group, (e.g., ARES, RACES) and a single band (6 meters) without regard to the number of hosts needed in that subnet. Connectivity and routing in Southern California can be sparse and geographically large, for instance, a 2 meter and 6 meter digipeater on Big Bear covering San Bernardino and Ontario California and reaching into Arizona and Nevada but seeing less than two dozen active nodes. The implications for static routing are straight forward. To get to any subnet one merely needs to route to the nearest host in 44.18/18 and the most any host needs is 63 routes. This was my solution, your mileage may vary. I never received any feedback regarding this solution until I googled this: http://www.snarked.org/~scdcc/tcpip-18.html I'll be interested in reading the comments from the list.

13 years, 11 months

6
13
0 0

Re: [44net] On the Issue of Subnets (fwd)

by Tim Osburn

This might be a good time to implement a rwhoisd server for the whole 44/8 network. This way for the people who want to register a block of any size we can have an easily accessible and viewable whois entries. Also anyone, anywhere can find out what is assigned to who regardless of it's block size and regardless if there are DNS entries or not. Then it would fall back to the regional coordinator if no entries were made for the query being checked, and then back to the top parent of Brian for 44/8 of no coordinator assigned. This is a proven method as ARIN has been using this for years on their whois server. Works very well. Assuming that if 44.X.X.0 is assigned something in DNS that it's broken into a /24 I believe is not a good idea as it might actually be a smaller or larger subnetmask. /24 can be very wasteful if you're not using most of it. I would say it would be more common to hand out /27's or /26's. This would also lend it's self nicely into IPv6, since that is supported as well if we get space. Tim Osburn www.osburn.com 206.812.6214 W7RSZ On Sat, 25 Feb 2012, Brian Kantor wrote: > Date: Sat, 25 Feb 2012 10:13:48 -0800 > From: Brian Kantor <Brian(a)ucsd.edu> > Reply-To: AMPRNet working group <44net(a)hamradio.ucsd.edu> > To: AMPRNet working group <44net(a)hamradio.ucsd.edu> > Subject: Re: [44net] On the Issue of Subnets > > So it seems to me that we have two classes of people requesting address > allocations from their local coordinators: > > 1. those who are planning to operate a regional router (radio- or > tunnel-based gateway) > > 2. those who are planning to use an existing router. > > How should we handle these? > > It's apparent that some scheme like Geoff's for allocating a subnet block to > the first group is wise. It's probably not necessary to actually register > the network (0'th) address nor the broadcast (all-ones) in the DNS but > they're still part of the allocation. Still, the entire block (a /24 in > Geoff's scheme) should be reserved by the coordinator for that router > operator. > > Do we (for a /24) enter 254 addresses into the DNS every time we register a > router block? I don't think that's necessary, although we've done it for a > select few blocks. > > At our current level of usage, perhaps it's enough to register only the first > 4 or 8 or 16 addresses in the block so that experiments can begin, and > register more as activity grows. > > In effect, this makes each router/gateway operator a delegated coordinator > for his subnet block, as all further allocation from his block has to be > coordinated with him. > > Is this getting too complicated? > > Ideas? > - Brian > _________________________________________ > 44Net mailing list > 44Net(a)hamradio.ucsd.edu > http://hamradio.ucsd.edu/mailman/listinfo/44net >

13 years, 11 months

1
0
0 0

mailing list protocol change

by Brian Kantor

I've set the 'reply to list' option ON for this list, so by default your replies to discussions should from now on be automatically directed to the list rather than to the original poster. You'll probably have to take specific action in your mail client if you want to reply privately only to the person posting the message. I think this is more in keeping with the spirit of the list, and it had been asked for by a few of the subscribers. If this causes difficulties, please let me know and I can turn it back OFF. - Brian

13 years, 11 months

3
2
0 0

Re: [44net] Gateway ip/netmask pair

by William Lewis

Sorry: I crossed my outgoing with Brian and Davids incoming. You're already on it Bill -------------------------- Well, for starters, it looks like the address you posted here is: 44.9.0.1, and you state belongs to WA6NMF. However, I show no such address on the network. I do show an address for WA6NMF, but it is 44.4.9.1 not 44.9.0.1. wa6nmf IN A 44.4.9.1 wa6nmf-1 IN A 44.4.9.2 wa6nmf-2 IN A 44.4.9.3 wa6nmf-3 IN A 44.4.9.4 Now, I also show the 44.9.x.x as a discontinued range. I also DO NOT show any entries at Fullers for either WA6NMF or for any address starting with 44.9.x.x or any with 44.4.9.x So, I'm curious as to where your entry came from ?? At 02:49 PM 02/22/12, you wrote: >No, I never said it belons to me. >I just got an error regarding that address while checking my routing infos. >It belongs to wa6nmf and should be corrected because it is wrong. > Wm Lewis (KG6BAJ) AMPR Net IP Address Coordinator - Northern and Central California Regions (A 100% Volunteer Group) (530) 263-1595 (Home/Office) ______________________________________________ ---------- This message is for the designated recipient only and MAY CONTAIN PRIVILEGED OR CONFIDENTIAL INFORMATION. If you have received it in error, please notify the sender immediately and delete the original. Any other use of this E-mail is prohibited.

13 years, 11 months

6
7
0 0

Gateway ip/netmask pair

by Marius Petrescu

Is it just me or we have a error in the gateway routing table? entry: 44.9.0.1/255.255.255.252 via 207.111.203.194 This gives a invalid subnet/netmak pair and gets ignored by rip44d. Should be either 44.9.0.1/255.255.255.255 or 44.9.0.0/255.255.255.252 73 de Marius, YO2LOJ

13 years, 11 months

12
15
0 0

Re: [44net] Gateway ip/netmask pair

by William Lewis

Well, for starters, it looks like the address you posted here is: 44.9.0.1, and you state belongs to WA6NMF. However, I show no such address on the network. I do show an address for WA6NMF, but it is 44.4.9.1 not 44.9.0.1. wa6nmf IN A 44.4.9.1 wa6nmf-1 IN A 44.4.9.2 wa6nmf-2 IN A 44.4.9.3 wa6nmf-3 IN A 44.4.9.4 Now, I also show the 44.9.x.x as a discontinued range. I also DO NOT show any entries at Fullers for either WA6NMF or for any address starting with 44.9.x.x or any with 44.4.9.x So, I'm curious as to where your entry came from ?? At 02:49 PM 02/22/12, you wrote: >No, I never said it belons to me. >I just got an error regarding that address while checking my routing infos. >It belongs to wa6nmf and should be corrected because it is wrong. > Wm Lewis (KG6BAJ) AMPR Net IP Address Coordinator - Northern and Central California Regions (A 100% Volunteer Group) (530) 263-1595 (Home/Office) ______________________________________________ ---------- This message is for the designated recipient only and MAY CONTAIN PRIVILEGED OR CONFIDENTIAL INFORMATION. If you have received it in error, please notify the sender immediately and delete the original. Any other use of this E-mail is prohibited.

13 years, 11 months

1
0
0 0

Re: [44net] Gateway ip/netmask pair

by Marius Petrescu

No, I never said it belons to me. I just got an error regarding that address while checking my routing infos. It belongs to wa6nmf and should be corrected because it is wrong. From: Daniel Curry [mailto:daniel@danielcurry.net] Sent: Thursday, February 23, 2012 00:41 To: Marius Petrescu Subject: Re: [44net] Gateway ip/netmask pair I found that you do not have 44.9.0.1 register to you. ftp://hamradio.ucsd.edu/pub/amprhosts On 02/22/2012 02:33 PM, Marius Petrescu wrote: Is it just me or we have a error in the gateway routing table? entry: 44.9.0.1/255.255.255.252 via 207.111.203.194 This gives a invalid subnet/netmak pair and gets ignored by rip44d. Should be either 44.9.0.1/255.255.255.255 or 44.9.0.0/255.255.255.252 73 de Marius, YO2LOJ _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net -- Daniel Curry PGP: AD5A 96DC 7556 A020 B8E7 0E4D 5D5E 9BA5 C83E 8C92

13 years, 11 months

1
0
0 0

strange traffic

by Rob Janssen

At the moment, I receive a continuous stream of packets like this: Frame 1: 118 bytes on wire (944 bits), 118 bytes captured (944 bits) Arrival Time: Feb 22, 2012 18:05:47.069526000 CET Epoch Time: 1329930347.069526000 seconds [Time delta from previous captured frame: 0.000000000 seconds] [Time delta from previous displayed frame: 0.000000000 seconds] [Time since reference or first frame: 0.000000000 seconds] Frame Number: 1 Frame Length: 118 bytes (944 bits) Capture Length: 118 bytes (944 bits) [Frame is marked: False] [Frame is ignored: False] [Protocols in frame: eth:ip:ip:data] Ethernet II, Src: ThomsonT_1e:e4:ca (00:14:7f:1e:e4:ca), Dst: AsustekC_b4:b4:6d (00:1d:60:b4:b4:6d) Destination: AsustekC_b4:b4:6d (00:1d:60:b4:b4:6d) Address: AsustekC_b4:b4:6d (00:1d:60:b4:b4:6d) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) Source: ThomsonT_1e:e4:ca (00:14:7f:1e:e4:ca) Address: ThomsonT_1e:e4:ca (00:14:7f:1e:e4:ca) .... ...0 .... .... .... .... = IG bit: Individual address (unicast) .... ..0. .... .... .... .... = LG bit: Globally unique address (factory default) Type: IP (0x0800) Internet Protocol, Src: 169.228.66.251 (169.228.66.251), Dst: 80.101.113.129 (80.101.113.129) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 104 Identification: 0x1924 (6436) Flags: 0x00 0... .... = Reserved bit: Not set .0.. .... = Don't fragment: Not set ..0. .... = More fragments: Not set Fragment offset: 0 Time to live: 49 Protocol: IPIP (4) Header checksum: 0xc1a8 [correct] [Good: True] [Bad: False] Source: 169.228.66.251 (169.228.66.251) Destination: 80.101.113.129 (80.101.113.129) Internet Protocol, Src: 76.114.219.34 (76.114.219.34), Dst: 169.228.66.251 (169.228.66.251) Version: 4 Header length: 20 bytes Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00) 0000 00.. = Differentiated Services Codepoint: Default (0x00) .... ..0. = ECN-Capable Transport (ECT): 0 .... ...0 = ECN-CE: 0 Total Length: 21504 Identification: 0x0000 (0) Flags: 0x00 0... .... = Reserved bit: Not set .0.. .... = Don't fragment: Not set ..0. .... = More fragments: Not set Fragment offset: 512 Time to live: 43 Protocol: IPIP (4) Header checksum: 0x3b1e [incorrect, should be 0x2746] [Good: False] [Bad: True] [Expert Info (Error/Checksum): Bad checksum] [Message: Bad checksum] [Severity level: Error] [Group: Checksum] Source: 76.114.219.34 (76.114.219.34) Destination: 169.228.66.251 (169.228.66.251) Data (64 bytes) 0000 45 00 00 54 00 00 40 00 3e 01 8e 79 2c 3c 2c 0a E..T..@.>..y,<,. 0010 2c 89 29 61 08 00 3d 1d 27 45 41 f6 70 20 45 4f ,.)a..=.'EA.p EO 0020 af 34 02 00 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 .4.............. 0030 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 ............ !"# Data: 45000054000040003e018e792c3c2c0a2c89296108003d1d... [Length: 64] It appears to be an IPIP packet from the gateway, which then contains another IPIP packet sent by 76.114.219.34 to the gateway, which again has another IPIP packet that my trace tool no longer shows. I don't understand why the gateway delivers these packets to me. As it looks like 76.114.219.34 is indeed a valid gateway in the system, I assume a misconfiguration rather than malice for now. But probably it would be better when amprgw just rejected all IPIP traffic that includes another layer of IPIP within it. Rob

13 years, 11 months

2
1
0 0

Linux tunnel gateway configuration?

by Brian Kantor

Does anyone have a step-by-step set of instructions for configuring a Linux host as a tunnel subnet gateway for AMPRNet? I'd like to have a proven list of all the commands that have to be entered to set one up. I think it would be very helpful and I don't have such a document in my archives. Thank you! - Brian (PS: this is the first message through the new mailing list setup; if you encounter any difficulties please let me know.)

13 years, 11 months

7
7
0 0

Re: [44net] Linux tunnel gateway configuration? (minor correction in last paragraph)

by Jay Nugent

Greetings Brian, On Tue, 21 Feb 2012, Brian Kantor wrote: > Does anyone have a step-by-step set of instructions for configuring a > Linux host as a tunnel subnet gateway for AMPRNet? > > I'd like to have a proven list of all the commands that have to be > entered to set one up. > > I think it would be very helpful and I don't have such a document in > my archives. Here is the snippett from the /NOS/AUTOEXEC.NOS where it sets up the TUN0 interface. Below that, I show the output of IFCONFIG and ROUTE on the Linux box, for your reference. In this example, 192.168.0.5 is the address of the Linux ethernet card and 192.168.0.44 is the address of the JNOS application running on Linux. BOTH address "appear" to exist on your LAN as if they were two independent machines. # -------------------------- # - TUN0 Configuration - # -------------------------- # NOTE: Remember to turn on IPv4 Forwarding in the kernel !!!! # echo 1 > /proc/sys/net/ipv4/ip_forward # attach tun tun0 1500 0 # # Whenever any host on your ethernet sends an ARP asking "Who-Has # 192.168.0.44", the ethernet in the Linux box will respond that it knows how # to reach this address. This 'feature' negates the need to assign an Alias # address to the Linux box's Eth0 interface (eth0:44), nor the need to put # anything special in the Linux route table :) # ifconfig tun0 ipaddress 192.168.0.44 ifconfig tun0 netmask 255.255.255.0 ifconfig tun0 mtu 1500 ifconfig tun0 description "TUN0 to Ethernet" # shell ifconfig tun0 192.168.0.5 pointopoint 192.168.0.44 mtu 1500 up # # Shouldn't be any need to ARP on a Point-to-Point link # so this has been commented out. # Note: The MAC addr would be that of the Linux eth card ##shell arp -s 192.168.0.44 00:11:43:c4:b3:48 pub # echo ***** TUN0 Configuration Complete ***** pause 2 # # All done! # ifconfig eth0 Link encap:Ethernet HWaddr 00:11:43:c4:b3:48 inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::211:43ff:fec4:b348/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:60 errors:0 dropped:0 overruns:0 frame:0 TX packets:54 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:14669 (14.3 KB) TX bytes:7099 (6.9 KB) Interrupt:16 tun0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:192.168.0.5 P-t-P:192.168.0.44 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1500 Metric:1 RX packets:7 errors:0 dropped:0 overruns:0 frame:0 TX packets:7 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:392 (392.0 B) TX bytes:526 (526.0 B) # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.6 0.0.0.0 255.255.255.255 UH 0 0 0 tun0 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.0.1 0.0.0.0 UG 100 0 0 eth0 On your gateway router remember to port forward (to 192.168.0.44) Telnet, Finger, and any other 'services' you want to reach on your JNOS application from the Internet. I do *not* recomend forwarding SMTP unless you have a solid way to prevent spam from the public Internet getting out onto your RF network. If your JNOS application is running the ENCAP.TXT route table and uses the 'encap' interface, DO NOT PORT FORWARD ANYTHING! Instead, define the 192.168.0.44 ip address of the JNOS application as your "DMZ Host" so that ALL protocols (TCP, IPIP Protocol-4, and others) will be automatically routed to the JNOS application where JNOS'es 'ip access' and 'tcp access' firewall rules will decide what gets through for processing/routing. Hope this helps! --- Jay Nugent WB8TKL o Chair, ARRL Michigan Section "Digital Radio Group" (DRG) [www.MI-DRG.org] () ascii ribbon campaign in /\ support of plain text e-mail +------------------------------------------------------------------------+ | Jay Nugent jjn(a)nuge.com (734)484-5105 (734)649-0850/Cell | | Nugent Telecommunications [www.nuge.com] | | Internet Consulting/Linux SysAdmin/Engineering & Design/ISP Reseller | | ISP Monitoring [www.ispmonitor.org] ISP & Modem Performance Monitoring | | Web-Pegasus [www.webpegasus.com] Web Hosting/DNS Hosting/Shell Accts| +------------------------------------------------------------------------+ 02:01:01 up 170 days, 8:39, 3 users, load average: 0.07, 0.14, 0.06

13 years, 11 months

1
0
0 0

my KA9Q NOS tunnel driver for OpenBSD on i386 and macppc is available

by Isao SEKI - JM1WBB

Hello gateway operators, A few days ago, I fixed a bug of my KA9Q NOS tunnel driver for OpenBSD for Little Endian CPU and my gateway, 44.129.192.1 returned into ampr.org. That is very light weight and running kernel land. My package is available at "Nostun Project" in my home page, http://gongon.com/JM1WBB/ but I'm sorry documents and patch file are very old... 73, Isao / JM1WBB

13 years, 11 months

1
0
0 0

Welcome to the mailing list

by Brian Kantor

This is the "44Net" mailing list for use by the AMPRNet 44net working group.

13 years, 11 months

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net