44net

44net@mailman.ampr.org

3194 discussions

Re: [44net] ENCAP ro BGP
by Steve L 19 Aug '15

19 Aug '15

Brian Kantor, Concerning hosts with no DNS entries can only use the IPIP mesh system. Couldn't this be tweaked at UCSD to allow only 44net traffic for hosts with no DNS entries? Thus letting BGP'd 44 hosts be able to communicate with IPIP 44 hosts regardless of DNS entries? And of course if there is a DNS entry then (like now) allow general/all inbound traffic. Just a thought, not sure if it raises any other issues. Steve, KB9MWR marius at yo2loj.ro wrote: >John, > >Yes, you should be able to send encapsulated data via amprgw and get the >correct replies, but only for specific BGP announced and registered >subnets. > >Arbitrary 44net targets not in those BGP announced networks are NOT >forwarded via amprgw, and only DNS registered hosts will be able to use >the gateway (as you correctly assume). > >Hosts with no DNS entries can only use the IPIP mesh system, since there >is usually no check for that criteria on the gateways, and any subnet >match is accepted. > >Marius, YO2LOJ

2 1

Re: [44net] OpenWRT
by Steve L 16 Aug '15

16 Aug '15

Bill, I don't know what Lynwood has, but as a winter project I was going to attempt the same thing on a Netgear WNR3500Lv2 running OpenWRT. It too has: 5 GigE Ports, and a USB 2.0 Port 128 MB NAND flash and 128 MB RAM Steve, KB9MWR

4 3

OpenWRT
by lleachii＠aol.com 15 Aug '15

15 Aug '15

Also, I forgot one step - I created a bridge interface between tunl0 and a new VLAN, I named it 'amprnet'. I assigned the bridge 44.60.44.1. - Lynwood KB3VWG

1 2

OpenWRT
by lleachii＠aol.com 15 Aug '15

15 Aug '15

Dani, That is EXACTLY what I'm seeking...! Has anyone compiled ampr-ripd v1.13 for MIPS 74Kc - Linux? - Lynwood KB3VWG On 08/13/2015 03:00 PM, 44net-request(a)hamradio.ucsd.edu wrote: > My router happens to be PPC instead of the more common MIPS. If your > router is also PPC by chance, then I can send you the ampr-ripd binary > to save you the process of cross-compiling.

3 6

New Linux Boot Scripts for Testing
by Steve L 08 Aug '15

08 Aug '15

Should anyone care for more tools for their own testing. feel free to use: http://44.92.21.1/tools/

3 3

GB7CIP
by Brian 06 Aug '15

06 Aug '15

Anyone know the status of G4APL's node? I haven't seen it on for a couple weeks now. -- A computer once beat me at chess, but it was no match against me in kick-boxing - Emo Phillips 73 de Brian Rogers - N1URO email: (see above) Web: http://www.n1uro.net/ Ampr1: http://n1uro.ampr.org/ Ampr2: http://nos.n1uro.ampr.org Linux Amateur Radio Services axMail-Fax & URONode http://uronode.sourceforge.net http://axmail.sourceforge.net AmprNet coordinator for: Connecticut, Delaware, Maine, Maryland, Massachusetts, New Hampshire, Pennsylvania, Rhode Island, and Vermont.

8 17

DNS question
by Christopher Munz-Michilein 05 Aug '15

05 Aug '15

Howdy all, I’ve got a question about DNS and rDNS - I submitted a request to the portal to have DNS addresses added for my subnet a couple of months back and have not received any feedback regarding the status and was just wondering if there was something else I needed to do to move things along. I’ve also noticed recently that there appears to be an incorrect rDNS record associated with the subnet and was wondering if that was just old info or if some DNS records had been added incorrectly. The subnet in question is 44.135.193.0/24 and the DNS record I found is ve8jl.ampr.org <http://ve8jl.ampr.org/> Cheers, Chris VE7ALB & VA7OL

2 1

Scripts
by Rob Janssen 05 Aug '15

05 Aug '15

> Subject: > [44net] Scripts > From: > Steve L <kb9mwr(a)gmail.com> > Date: > 08/05/2015 03:57 AM > > To: > "44net(a)hamradio.ucsd.edu" <44net(a)hamradio.ucsd.edu> > > So that got me thinking maybe this same concept could be applied to > the BGP'd subnets, forcing them to use masquerading. But rather a > rule on the source address, we set it for destinations. > > Here is what I came up with. (Untested) > > http://www.qsl.net/kb9mwr/wapr/tcpip/startampr-bgp > > Basically I download a list of all the BGP'd subnets, and set a flag > like before and force them out as masqueraded. > I think it is preferable to IPIP encapsulate the traffic to a place where it can be sent with its original source address, over masquerading it to the public IP. When you have a default route in table 44 pointing to AMPRGW it will work OK without requiring exceptions for BGP routed subnets and it will also work to public internet. When you want to route only to AMPRnet you can use a 44.0.0.0/8 route to AMPRGW instead. (instead of AMPRGW, you can also use a more specific gateway that is on a not source-address filtered host and is closer to you, when they want to provide that service. e.g. for 44.137.0.0/16 hosts our gateway can be used for that) Unfortunately this still breaks in case an IPIP gateway is using an endpoint address within 44.0.0.0/8 Rob

1 0

Re: [44net] New Linux Boot Scripts for Testing
by Rob Janssen 05 Aug '15

05 Aug '15

> Subject: > Re: [44net] New Linux Boot Scripts for Testing > From: > lleachii(a)aol.com > Date: > 08/04/2015 11:17 PM > > To: > 44net(a)hamradio.ucsd.edu > > > Nigel, > > - I should be a properly configure IPIP gateway. > > Can you reach me? > > 44.60.44.0/24 > 44.60.44.1 - router > 44.60.44.3 - DNS > 44.60.44.10 - HTTP At the time you wrote that it was not yet working, but now I can reach you from here! So it appears you have fixed it. Good! Rob

1 0

Re: [44net] New Linux Boot Scripts for Testing
by Rob Janssen 05 Aug '15

05 Aug '15

> Subject: > Re: [44net] New Linux Boot Scripts for Testing > From: > Tom Hayward <esarfl(a)gmail.com> > Date: > 08/04/2015 09:34 PM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu> > > > On Tue, Aug 4, 2015 at 12:19 PM, Rob Janssen<pe1chl(a)amsat.org> wrote: >>> >>The hamwan.org remain unreachable >> > >> >It goes via radio to our 44.137.0.0/16 gateway and from there over plain >> >internet (it is BGP routed). >> >You may have trouble trying to access this with some of the typical tunnel >> >setups because they provide no tunnel endpoint. > Indeed, this is what you should be seeing for hamwan.org at the > moment. Since our gateway was deleted from the portal we have not gone > in and rebuilt things. > > We are properly BGP routed, so any machine on the internet (and not > behind amprgw) should be able to access it. The system where I tested this (our gateway system) can send internet traffic from 44.137.0.0/16 without source address filtering issues. However, the typical ISP line here is source address filtered, so I cannot send traffic from a 44.137.x.x address directly from my home line to you on your BGP routed network. Traffic to other IPIP gateways is encapsulated in an outer header with my public IP and the public IP of the tunnel endpoint I route to, so my ISP does not filter such traffic. However, when I want to send from my 44.137.x.x address to any other system, either outside 44.x.x.x or in the 44.x.x.x network but not routed via IPIP, I need to encapsulate it and send it to some system that can send that traffic without source address filter. Before we had our own gateway, it was usual to send this traffic to AMPRGW. But that did not work for this case. That appears to have been resolved now. Our own gateway could already do this. However, there is still the issue of "what to do with traffic" (encapsulate it or not, what source address to use) sent to 44.x.x.x. It was difficult to do it right when the tunnel endpoint falls within the 44.x.x.x network. This was the actual reason why your tunnel endpoint was removed after discussion here. I think when you bring back the tunnel endpoint (which of course is preferable), you should try to get an IP outside 44.x.x.x for the tunnel endpoint, as most users have done. That reduces the risk of problems. I do not believe in setting up exception lists for ranges that are BGP routed or are used as tunnel endpoints but are within 44.x.x.x, that is just making everything complicated and makes it break down when people are not always on the watch for changes in the network. The automatic handling provided by (ampr-)ripd is much preferred over such manually maintained configuration. Rob

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net