44net

44net@mailman.ampr.org

3196 discussions

Re: [44net] DMVPN routing for 44/8 subnets
by Bryan Fields 01 Jul '13

01 Jul '13

On 6/27/13 2:26 PM, K7VE - John wrote: > Great idea - wrong platform. Cisco specific solutions aren't reachable for > many. > > Look at Linux (Raspberry Pi) solutions or powerful, affordable routers like > MIkroTik and common tunneling protocols like OpenVPN, L2TP, GRE, etc. I take issue with that. MikroTik is just as much of a closed platform as Cisco/JNPR/ALU/Fond-cade/etc. Cisco is ubiquitous, to a lesser extent Juniper (though I have to favor ALU for MPLS/core!). I'd say what we need is an open standards based solution that works across linux/cisco/jnpr (maybe an o-series? :) Something custom protocol wise to tie the 44net together is not ideal either as we cannot expect the big router vendors to support amprnet protocols. I know I'm able to slap a 1ru router (ie c2[6-9]00) in lots of places with good connectivity I could never put a server. I belive there is a way to do this via NHRP with BGP. I know I have a customer doing something like this. Since we don't need crypto for 44net I suspect it would work for us. just my .02 73's -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net

6 10

DMVPN routing for 44/8 subnets
by jesse＠hindmarsh.cc 29 Jun '13

29 Jun '13

I am working on a lab design to add some flexibility and test other connection methods to the 44.0.0.0/8 network. I currently have a Linux gateway running rip44d for my main connectivity to the other 44/8 subnets. I have setup a Cisco based DMVPN where I can route other subnets to and route back to the Linux gateway for access to other subnets. This configuration also allows access from the public Internet to the allocated subnets via a Linux gateway. I have a diagram with a working layout and is in testing now. I am looking to see if anyone might be interested in connecting up to my cloud and see what and if any problems we may encounter. I use a very similar setup with my customers and there are some distinct advantages: - The end user would only need an internet connection and a Cisco DMVPN capable router. I have used 800, 1800, 2800, 3700 series Cisco routers. - The DMVPN works when you plug the Cisco router into a direct Internet or NAT connection. You can plug it in at home behind your Netgear home router, use DHCP and a private address on the router "public" interface. - Many subnets can be routed through a single Linux gateway and distributed easily. - No issues with dynamic IP address from your provider. If you are interested or have any comments or suggestions, take a look at the network diagram I made at http://www.hindmarsh.cc/images/wc3xs-ampr44.png 73 de WC3XS - Jesse

5 7

Re: [44net] 44Net Digest, Vol 2, Issue 78
by Rob Janssen 28 Jun '13

28 Jun '13

Jesse Hindmarsh <jesse(a)hindmarsh.cc> wrote: > > > > > > Rob, > > I like your thinking. Are you a Cisco guy too? I have been for too long :-) > > I am still partial to hardware based solutions. > > Jesse - WC3XS, CCNP Voice, CCNP RS, CCDA I learned networking with the KA9Q software and later when I got a job as a sysadmin I worked with existing Cisco routers and found many things very familiar. I learned the Cisco stuff myself from the manuals, have no CC certifications. I converted our existing network at work from leased lines to VPN some 10 years ago over Internet using DMVPN and it worked very well. (now we have dedicated lines again, but that wasn't affordable at megabit speeds 10 years ago) I suggested DMVPN before on this list, and I still think it could be a good option at least when an open implementation is available. I don't know if it is today, it has been in the works for some time. (the specs are open) In the performance class we are operating in, "hardware based" is not really required. A suitable box (processor and ethernet interfaces) and software (e.g. Linux plus some usermode tools) can do the same thing. I run IPsec tunnels between Ciscos, between Linux boxes, and between Cisco and Linux, and it is all inter-operating well. Of course we don't want to tie outselves to "only Cisco". But a solution where Cisco and open implementations (on systems like Linux and BSD) inter-operate is a very good thing. IMHO we don't need to consider compatibility with DOS (e.g. JNOS on DOS) as critical anymore. Rob

2 1

Re: [44net] 44Net Digest, Vol 2, Issue 77
by Rob Janssen 27 Jun '13

27 Jun '13

K7VE - John <k7ve(a)k7ve.org> wrote: > Great idea - wrong platform. Cisco specific solutions aren't reachable for many. > > Look at Linux (Raspberry Pi) solutions or powerful, affordable routers like MIkroTik and common tunneling protocols like OpenVPN, L2TP, GRE, etc. The big advantage of Cisco DMVPN is that it can create a fully meshed tunnel network with endpoints on dynamic addresses, with only one (or a few) central hubs on static addresses, fully automatically. It is like what you have with a JNOS or Linux route importing encap.txt all the time, but without the hassle. Other VPN solutions are usually hub-and-spoke, where all internode traffic goes through the central hub. It is like connecting to net-44 by tunneling everything to 169.228.66.251 instead of loading a routing table. Rob

3 2

Re: [44net] Basic help needed with Linux and rip44d
by lleachii＠aol.com 27 Jun '13

27 Jun '13

Jesse, Take a look at my startup script at http://44.60.44.13/startampr It seems you have a similar setup, although one line of your configuration seems incorrect: ip route add 44/8 via 169.228.66.251 dev tunl0 onlink src 44.64.192.253 You should remove this route, it's invalid inside AMPR. You should not reach 44.0.0.0/8 via AMPRGW (169.228.66.251), you should reach each subnet via its gateway WAN IP address, as populated by rip44d. The return packet would come in the same manner, via their 44GW that has a route configured for you. My router: @kb3vwg-001:~# ip route get 44.64.192.253 44.64.192.253 via 24.229.88.252 dev tunl0 src 172.31.255.254 My route table shows: 44.64.192.0/24 via 24.229.88.252 dev tunl0 onlink window 840 73, Lynwood KB3VWG

4 5

Contact needed please
by Brian Rogers 26 Jun '13

26 Jun '13

Greetings list; Could the coordinator for 44.135/16 contact me off-list please? Thanks in advance. -- Brian Rogers Phone: 860-673-4537 Email: n1uro(a)gmx.com Web: http://www.n1uro.net/ Ampr1: http://n1uro.ampr.org/ Ampr2: http://nos.n1uro.ampr.org/ Platform: Linux

1 0

Re: [44net] ampr.org dns zone delegation
by kb9mwr＠gmail.com 26 Jun '13

26 Jun '13

What about someone wanting to setup a dynamic DNS, with rather short lived record TTL's? For many gateway's they rely on an external service (dyndns, no-ip, etc) and many other ham applications (IRLP has it's own dynamic DNS etc) I have often wished the ARRL or QTH/QSL,net would offer a Dyn-DNS service for hams. ------------ >> How can one establish one or more NS records in the ampr.org hierarchy such >> that dns for *.mycallsign.ampr.org could be self managed? >Generally I prefer not to delegate zones in the "forward" lookup; >we're hoping to obviate the need for that with the self-management >of DNS records that the portal will provide. That will also solve the >issues of the 44.in-addr zone being kept in sync. >- Brian

1 0

ampr.org dns zone delegation
by Eric Fort 26 Jun '13

26 Jun '13

How can one establish one or more NS records in the ampr.org hierarchy such that dns for *.mycallsign.ampr.org could be self managed? Eric AF6EP

2 1

address block assignments for groups
by Eric Fort 23 Jun '13

23 Jun '13

Must a block of 44net IP space be assigned to an individual or could it be assigned to a club or other group? Say a club station had the callsign w6xyz assigned. could w6xyz then be assigned a /24 block to build out a lan serving a given geographic area? Eric AF6EP

5 6

Basic help needed with Linux and rip44d
by jesse＠hindmarsh.cc 20 Jun '13

20 Jun '13

I have followed the instructions on the wiki pages to the exact detail, and am having issues with the setup. I am at the point where I can receive routing updates but cannot send any data over the tunnel. I am not the best when it comes to Linux but have a better understanding of networking, routers, and routing (Cisco). I have eth0 on a public address. I have eth1 on 44.64.192.253/24 I have tunl0 on 44.64.192.254/8 I am running Ubuntu 10.04 on VMWare. 1. When I create the tunl0 interface with the class A netmask, how is rip44d using this and where does the tunnel "endpoint" get defined? (remote endpoint address?) 2. I have the Linux machine running rip44d and another linux machine on the same assigned 44.64.192.x subnet. I can ping between them until I bring up the tunl0 interface. If I down and up the tunl0 interface, I can ping as expected. Can anyone explain this behavior? 3. The tunl0 interface is registering collisions equal to the number of packets transmitted. I cannot find a reason why this is happening. Thanks in advance, Jesse

2 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net