44net

44net@mailman.ampr.org

1 participants
3192 discussions

by Hugh Golding

Hi Guys, Sorry about the RIP routes. After some work on my router the RIP was turned on for all interfaces. I have now rectified this and all should have stopped. Apologies. Best Regards, Hugh G7UOD ) +44 7841 749345 * g7uod(a)onlineham.net

12 years, 7 months

Re: [44net] 44Net (no subject)

by Rob Janssen

> Subject: > [44net] (no subject) > From: > kb9mwr(a)gmail.com > Date: > 08/24/2013 02:59 AM > > To: > "44net(a)hamradio.ucsd.edu" <44net(a)hamradio.ucsd.edu> > > > --- Quote --- > > For some reason, I cannot get it to receive the 44.0.0.1 -> 224.0.0.9 > transmissions. > The socket is listening on port 520, when I trace tunl0 I see the > packets arriving > every 5 minutes, but the rip44d (running with -v) remains absolutely silent. > Any idea what that can be? > ------ > > The first thing that comes to mind is something wrong with the tunl0 netmask. > Ah is that the reason? The netmask on tunl0 is 255.255.255.255. I have only a single address on my tunnel endpoint. Is that not allowed? What should it be instead? In the meantime I have solved it by using ampr-ripd instead of rip44d. It has the -r option to use a raw socket to receive everything on tunl0 and picking out the RIP datagrams itself. That works OK. I have a Rasperry Pi that is located in a datacenter. It is directly on Internet. Now I am running the net-44 tunnel stuff on it, it acts as my gateway for two single addresses and a subnet. There is a local copy of NETCHL running there as well, on 44.137.40.1. I can access the different amprnet systems from there. It is running under "screen" so I can take over the console from where I like. My subnet is routed to my home system via an IPsec tunnel, where I still run some services that I want to move there. The default route for net-44 traffic at home is now to my Pi. It runs beautifully. Now my system at home is a lot less complicated, and I can more easily upgrade to a newer Linux version without disturbing all the special networking stuff. Rob

12 years, 7 months

Dynamic Routing: LISP

by Jim Alles

In another thread, it was said: >> everyone in the mesh ought to be running a dynamic routing protocol thus >> increasing redundancy and reliability. >This is a good idea. I'm not up on the latest RFCs concerning routing in >tunneled (VPN, GRE, etc) networks. Do you have a recommendation? I am not an expert to answer this question, but I have stumbled on an emerging method for routing that has remarkable similarities to threads here. Along with the connections/associations I list below, it is experimental communications, and I believe we (Hams) have something to contribute. RFC 6830, LISP (Locator/ID Separation Protocol - see [http://www.lisp4.net/] ) decouples Location from unique IDentifier in IP addressing. I first saw the need for this concept with APRS messaging, but that is for another group. "LISP follows a network-based map-and-encapsulate scheme ... both identifiers and locators can be IP addresses or arbitrary elements like a set of GPS coordinates or a Mac address." {or call sign?} The LISP Papers at [http://blog.pattincon.com/lisp-papers/] seems to be a good place for me to start to understand the application of this protocol. It is implemented in recent versions of Cisco IOS/NX-OS (out of my reach at this time) and LISPmob (Mobile Node) at [http://lispmob.org/] runs on OpenWRT/Linux. I am working on experimenting with something from here. Peace, Jim A. KB3TBX

12 years, 7 months

(no subject)

by kb9mwr＠gmail.com

--- Quote --- For some reason, I cannot get it to receive the 44.0.0.1 -> 224.0.0.9 transmissions. The socket is listening on port 520, when I trace tunl0 I see the packets arriving every 5 minutes, but the rip44d (running with -v) remains absolutely silent. Any idea what that can be? ------ The first thing that comes to mind is something wrong with the tunl0 netmask.

12 years, 7 months

Re: [44net] Something simple

by Rod Ekholm

Pedja, If I add the encap.txt file you provided (realizing is is truncated..) and adding it to my files list in my router, and running the txt file you provided as a scipt in my MT, it does nothing. Is this the intended method of your files? i see the script count increment, but I don't see any routes get added. In the first line of the script file, I edited the IP Address to be my local (inside address). Should it be the inside address, my outside WAN address or my AMPR address? Thanks for clarifying, and great job, if this works! -- Rod Ekholm KC7AAD

12 years, 7 months

Re: [44net] Who is teqsys.net and why is he sending me RIP?

by Heikki Hannikainen

On Sun, Aug 18, 2013 at 5:54 PM, David Ranch <amprgw(a)trinnet.net> wrote: > Going to www.teqsys.net and looking at the Orange tab, there is the callsign > G7UOD for "Hugh Golding". There is an email address for him on QRZ too. I sent an email to Hugh, he confirmed he has removed his RIP transmit configuration now, and teqsys.net should not be sending those packets any more. - Hessu

12 years, 7 months

Re: [44net] Radio-based networking

by Paul Delaney - K6HR

Same here, all dressed up with nowhere to go! I maintained 6 radio ports for quite a long time utilizing HF/VHF/UHF 1200/9600/PACTOR3, even satellite. No users. No more fun. I eventually reinvested that money in other areas of the hobby. Judging by the replies so far I think it's fairly safe to say there is little to no tcp/ip over radio in use anymore. Paul Delaney - K6HR http://k6hr.dyndns.org:8080 On 08/21/13, JJ wrote: (Please trim inclusions from previous messages) _______________________________________________ On 13-08-21 11:19 AM, Brian Kantor wrote: > > Is anyone actually using the network over radio at this point? > Could you supply some details? > I have 4 RF ports, 2 hf, 2 vhf, all ip capable, but there's no-one in my area to route to over the air...and forget trying tcipip @ 300 baud hf, lol, that wud be painful...but I cud turn the beam and route to ka0mos over vhf... prolly not very helpful, but yes, I use/would use ip over RF, I have b4, and I will again! _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html

12 years, 7 months

Re: [44net] Radio-based networking

by Paul Delaney - K6HR

An HTML attachment was scrubbed... URL: <http://hamradio.ucsd.edu/mailman/private/44net/attachments/20130821/7ee0c10…>

12 years, 7 months

Re: [44net] Radio-based networking

by kb9mwr＠gmail.com

------ Quote ------ Is anyone actually using the network over radio at this point? Could you supply some details? We had been using the 44 net space and TCP/IP over radio (1200/9600) for many years here in Wisconsin. We even ran Webservers on those links. This made the 1999 CQ and CQ-VHF magazine. Our original packet organization's (WAPR) webpage was accessible via radio. http://www.qsl.net/kb9mwr/wapr/ Now most of the 1200 baud portions of the network are dead, and only a few have moved on to 802.11 options. I and four others in Green Bay have been mostly doing remote backups using rsync over 802.11 for several years now. A few years back I ran a PBX with a 802.11 trunk to my friends house.

12 years, 7 months

Re: [44net] Radio-based networking

by Brian Rogers

Hello Brian et al; > I'm in the process of preparing a new document on the AMPRNet. > I'd like to include a section on the radio-based portions of the > network. > > Is anyone actually using the network over radio at this point? > Could you supply some details? You may be interested in this link: http://bythebays.net/neflexnet/howtotcp.htm It's a document I drafted with k2mf a few years back. ********************** 73 de Brian N1URO ********************** Spam {n}: an entity using smtp via internet to force humans to revert back to paper, pencil, and postage for mail communications.

12 years, 7 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net