44net

44net@mailman.ampr.org

1 participants
3195 discussions

Re: [44net] 44Net (no subject)
by Rob Janssen 26 Aug '13

26 Aug '13

> Subject: > Re: [44net] (no subject) > From: > kb9mwr(a)gmail.com > Date: > 08/24/2013 10:06 PM > > To: > "44net(a)hamradio.ucsd.edu" <44net(a)hamradio.ucsd.edu> > > > The tunnel interface is a gateway to the rest of the class A network. > You have to allow this by setting a netmask of netmask 255.0.0.0 > > An your second ethernet interface to your radio LAN, you may set a > smaller netmask. > > Steve > > > Subject: > Re: [44net] 44Net (no subject) > From: > "Marc, LX1DUC" <lx1duc(a)rlx.lu> > Date: > 08/24/2013 10:12 PM > > To: > 44net(a)hamradio.ucsd.edu > > > Netmask surely has a relation to broadcast packets, but not multicast. > > Several user on this list use /32 (255.255.255.255) netmask on their > tunl0 interface. > > 73 de Marc It is not completely clear to me what the netmask on tunl0 really does. I understand what it does on a local network, but not for tunl0. For the routing, it does not appear to influence anything. And at least by setting it this way, I avoid having that unclear route for 44.0.0.0/8 that is added when tunl0 is created. Maybe it breaks multicast, but I don't know how. The non-working multicast could as well be the result of something else, e.g. the limited config included with the Raspberry Pi that is not really intended to be a complex router (but quite capable of it). With the -r option to ampr-ripd things appear to work OK. I use the policy-routing configuration, not a flat routing table. There is a main routing table with routes for the local network (at the datacenter), and the default gateway. There is a separate route table 44, with the default route to amprgw, the specific route for my subnet at home and the local running NET, and the ampr-ripd also adds all the specific tunnel routes in that table. There are policy routing rules that select this routing table when the source or the destination of the packet is in network 44: 44: from 44.0.0.0/8 lookup 44 45: from all to 44.0.0.0/8 lookup 44 Rob

2 1

Portal Feature Request
by Neil Johnson 26 Aug '13

26 Aug '13

Can I request a feature for the portal ? It would be nice for a co-ordinator to have the ability to add an IP address allocation on the behalf of someone else. I'm in the process of cleaning up the database for the US State of Iowa, and some users are e-mailing me directly to keep their allocations rather than registering it via the portal. I suspect that explaining how to register through the portal might be confusing or they don't feel comfortable registering on the portal. Thanks. -Neil -- Neil Johnson -N0SFH http://erudicon.com

2 1

Routing Tables
by Demetre SV1UY 25 Aug '13

25 Aug '13

Hi all, My routing table after my AMPRnet GATEWAY has got all the routes via RIPv2 using rip44d, looks like this: ------------------------------------------------------------------------------------------------------- Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.15.1 0.0.0.0 UG 0 0 0 eth0 44.0.0.0 169.228.66.251 255.0.0.0 UG 0 0 0 tunl0 44.0.0.0 0.0.0.0 255.0.0.0 U 30 0 0 rose0 44.0.0.1 169.228.66.251 255.255.255.255 UGH 0 0 0 tunl0 44.2.1.32 76.14.161.185 255.255.255.248 UG 0 0 0 tunl0 44.2.10.0 71.130.72.52 255.255.255.248 UG 0 0 0 tunl0 44.2.11.1 71.130.72.52 255.255.255.255 UGH 0 0 0 tunl0 44.2.14.0 50.79.156.221 255.255.255.248 UG 0 0 0 tunl0 44.2.14.100 50.79.156.221 255.255.255.255 UGH 0 0 0 tunl0 44.2.50.0 68.189.32.222 255.255.255.248 UG 0 0 0 tunl0 44.2.50.0 208.74.106.137 255.255.255.0 UG 0 0 0 tunl0 44.4.2.152 173.167.109.217 255.255.255.255 UGH 0 0 0 tunl0 44.4.2.153 173.167.109.217 255.255.255.255 UGH 0 0 0 tunl0 .... More routes ------------------------------------------------------------------------------------------------------------- Is this correct or am I dending all AMPRnet traffic through UCSD.EDU ? -- 73 de SV1UY Demetre Ch. Valaris e-mail: demetre.sv1uy(a)gmail.com Radio e-mail: sv1uy(a)winlink.org (to use my radio e-mail put //WL2K in the beginning of the subject line) http://www.qsl.net/sv1uy

2 1

FW: RIP from teqsys.net
by Hugh Golding 25 Aug '13

25 Aug '13

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

3 3

Re: [44net] 44Net (no subject)
by Rob Janssen 24 Aug '13

24 Aug '13

> 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

2 1

Dynamic Routing: LISP
by Jim Alles 23 Aug '13

23 Aug '13

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

2 1

(no subject)
by kb9mwr＠gmail.com 23 Aug '13

23 Aug '13

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

1 0

Re: [44net] Something simple
by Rod Ekholm 23 Aug '13

23 Aug '13

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

2 1

Re: [44net] Who is teqsys.net and why is he sending me RIP?
by Heikki Hannikainen 22 Aug '13

22 Aug '13

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

1 0

Re: [44net] Radio-based networking
by Paul Delaney - K6HR 21 Aug '13

21 Aug '13

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

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net