44net

44net@mailman.ampr.org

3194 discussions

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 25 Jun '13

25 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 25 Jun '13

25 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

Re: [44net] Basic help needed with Linux and rip44d
by kb9mwr＠gmail.com 20 Jun '13

20 Jun '13

Jesse, Here are my notes: http://www.qsl.net/k/kb9mwr//wapr/tcpip/rip44d.html The endpoints are populated by the RIP routes that are received. You can run the dameon in verbose mode, and periodically check how the route table is being manipulated with the command "route" As for why you can ping two machines on the same subnet, it sounds like a conflicting route. Again what does "route" show you? Steve, KB9MWR

1 0

rip44d
by sp2lob＠tlen.pl 19 Jun '13

19 Jun '13

Hello, Been curious and just wanted to give a try running rip44d... Downloaded: https://github.com/hessu/rip44d Followed exactly procedure decribed here: http://wiki.ampr.org/index.php/Rip44d Executed: linux~/rip44d$sudo ./rip44d -v found local address: 192.168.0.101 found local address: 44.165.2.1 found local address: 127.0.0.1 found local address: 44.165.2.2 found local address: 44.165.2.2 found local address: 44.165.2.2 found local address: 44.165.2.2 found local address: 44.165.2.2 opening UDP socket 520... entering main loop, waiting for RIPv2 datagrams Waited more than half an hour and... nothing happend at all. According to a/m source, “Amprgw transmits the RIP routing table updates every 5 minutes” Does Amprgw still broadcasts RIPv2 info? Best regards Tom - sp2lob

3 8

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net