44net June 2015

44net@mailman.ampr.org

41 participants
47 discussions

Reverse Delegation
by Fredric Moses 02 Oct '15

02 Oct '15

I know a couple of groups now have proper reverse delegation of DNS for their subnets… Wondering who to drop a line to so I can get 44.103.0.0/19 delegated to a.ns.mi6wan.net and b.ns.mi6wan.net ? Didn’t see it in the portal or wiki and my notes from a few months ago are foggy... -- Fredric Moses - W8FSM - WQOG498 fred(a)moses.bz

6 6

Not able to fill subnet IP
by Libor Berka 29 Jun '15

29 Jun '15

I am trying to register amprnet gate at IP 147.229.242.130 (ok0nmg.ddns.net) at portal.ampr.org but there is no offer to put a subnet (here 44.177.10.254/32). I ahve already registered 2 gateways before succesfully with their subnets but this a/m one its not possible to put a subnet. (The ampr-ripd system is running well on ok0nmg.ddns.net.) I need some help please. Best 73 Libor OK2PEN (PY2ZEN) sysop of gates ok2koj.ampr.org, ok2pen.ampr.org and ok0nmg.ampr.org

2 1

Test New Tool - APRS Code Recovery
by lleachii＠aol.com 24 Jun '15

24 Jun '15

All, I've added a new tool that I'd like you to test. This web application should provide the registration code required by APRS software suites. In order to use it, you must browse to: http://kb3vwg-010.ampr.org/tools/aprscode or http://44.60.44.10/tools/aprscode If you're on AMPRNet, you should be able to enter the callsign and look up the registration code. If you access it from outside of AMPRNet, you will be prompted for an access code (1234). Please let me know how it works 73, KB3VWG

39 87

Re: [44net] attacks on 44 net !
by Gustavo Ponza 24 Jun '15

24 Jun '15

> Hi Maiko and all, > > since from three or more years I'm visited from many > attackers which I mainly identified as government agencies > and/or research/industrial groups... just note the inbound and > the outbound traffic below. > A very big attack at 23.30 - 00.30 is shown > > gus i0ojj > > > ----------------- ***Image 'attacks.png' deleted*** The tonight visitor(s) was the following: org. 128054 IN NS b2.org.afilias-nst.org. org. 128054 IN NS b0.org.afilias-nst.org. org. 128054 IN NS c0.org.afilias-nst.info. org. 128054 IN NS d0.org.afilias-nst.org. org. 128054 IN NS a2.org.afilias-nst.info. org. 128054 IN NS a0.org.afilias-nst.info. a0.org.afilias-nst.info. 128054 IN A 199.19.56.1 a0.org.afilias-nst.info. 128054 IN {28} a2.org.afilias-nst.info. 128054 IN A 199.249.112.1 a2.org.afilias-nst.info. 128054 IN {28} b0.org.afilias-nst.org. 128054 IN A 199.19.54.1 b0.org.afilias-nst.org. 128054 IN {28} b2.org.afilias-nst.org. 128054 IN A 199.249.120.1 b2.org.afilias-nst.org. 128054 IN {28} c0.org.afilias-nst.info. 128054 IN A 199.19.53.1 c0.org.afilias-nst.info. 128054 IN {28} d0.org.afilias-nst.org. 128054 IN A 199.19.57.1 d0.org.afilias-nst.org. 128054 IN {28} ---------------- ... and in the past few days as below: ---------------- www.google.it. 0 IN A 74.125.206.94 . 93348 IN NS b.root-servers.net. . 93348 IN NS j.root-servers.net. . 93348 IN NS i.root-servers.net. . 93348 IN NS e.root-servers.net. . 93348 IN NS k.root-servers.net. . 93348 IN NS m.root-servers.net. . 93348 IN NS d.root-servers.net. . 93348 IN NS c.root-servers.net. . 93348 IN NS g.root-servers.net. . 93348 IN NS f.root-servers.net. . 93348 IN NS a.root-servers.net. . 93348 IN NS l.root-servers.net. . 93348 IN NS h.root-servers.net. dnsscan.shadowserver.org. 0 IN A 184.105.143.133 satellite.cs.washington.edu. 41243 IN A 198.48.92.101 satellite.cs.washington.edu. 41243 IN A 198.48.92.103 satellite.cs.washington.edu. 41243 IN A 198.48.92.102 satellite.cs.washington.edu. 41243 IN A 198.48.92.104 cs.washington.edu. 0 IN A 128.208.3.200 www.google.com. 0 IN A 64.233.184.103 www.google.com. 0 IN A 64.233.184.106 www.google.com. 0 IN A 64.233.184.105 www.google.com. 0 IN A 64.233.184.99 www.google.com. 0 IN A 64.233.184.104 www.google.com. 0 IN A 64.233.184.147 a.root-servers.net. 473340 IN A 198.41.0.4 b.root-servers.net. 473340 IN A 192.228.79.201 c.root-servers.net. 473340 IN A 192.33.4.12 defcon.org. 197093 IN SOA dns-1.datamerica.com. hostmaster.defcon.org. 2015051025 43200 600 86400 86400 defcon.org. 197093 IN TXT =v=spf1 defcon.org. 197093 IN MX 10 mail-1.datamerica.com. defcon.org. 197093 IN A 162.222.171.206 ----------------------

1 0

Power outage
by Jerry Kutche 22 Jun '15

22 Jun '15

Today's power outage seems to have left my net 44 link DOA... If so I wanted everyone to know I may be back.. No time to fix right now.. Just spent over a week getting everything working after a virus attack. And was not really done still had two systems down.. Now I have this.. I need a break, also.. May pick this back up in July... May not. Anyone linked to me I will be back eventually.. Maybe Maybe not. But now I have to figure out a few things. Why does my Pi lose all its free space within 30 minutes of boot up. Went from 73% to 100% cannot connect to it without rebooting over and over... So until I feel like being a slave to linux and the PI I am off line. 73 Jerry N9LYA

6 8

K3MMB
by Brian 21 Jun '15

21 Jun '15

Does anyone know the status of K3MMB? His system appears to be offline and has been for a couple weeks or so. -- 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.

1 0

Re: [44net] portal purge
by Rob Janssen 21 Jun '15

21 Jun '15

> Subject: > Re: [44net] portal purge > From: > Don Fanning <don(a)00100100.net> > Date: > 06/20/2015 01:40 AM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu> > > > There is so much cruft in the DNS tables > that I imported the information into a database and ran the FCC > database against it. There were roughly 1800 entries out of 3700-ish > that matched expired/cancelled/revoked callsigns. And that's just for > the US alone - not including active licensees who just lost interest > in 44net. As BrianK would point out, there is no way that the DNS > table should be this big. I do regular checks of the registered addresses in the 44.137.0.0/16 subnet against the list of callsigns published by our local authority. I also delete registrations when "silent key" announcements appear in the club magazine. And a few weeks ago I deleted all dangling MX and CNAME records, most of them for US hams. (see discussion on the list) It appears to have been standard practice to create MX records for new registered addresses, and to not delete them when addresses are deleted. Do you have valid "callsign change" tables in the US? A problem for me is that there is no official information on that from our authority, apparently for privacy reasons. So sometimes I delete an address because the callsign is no longer valid, to find later that the operator has changed to a higher license class or vanity callsign. And not everyone changing their callsign notifies me. Rob

4 5

Re: [44net] Model gateway system
by Rob Janssen 20 Jun '15

20 Jun '15

> Subject: > Re: [44net] Model gateway system > From: > Steve L <kb9mwr(a)gmail.com> > Date: > 06/19/2015 10:06 PM > > To: > "44net(a)hamradio.ucsd.edu" <44net(a)hamradio.ucsd.edu> > > > IPIP gateways should not use amprgw default route. > Ex: ip route add default dev tunl0 via 169.228.66.251 onlink .... That is incorrect. Such a route is OK as long as it is in an alternative routing table for AMPRnet traffic. It can be to amprgw or to a more local gateway. Such a route is required when you are on a source-address filtered internet connection and want to be reachable on your AMPRnet address from other internet systems. Rob

1 0

Model gateway system
by Michael E Fox (N6MEF) 20 Jun '15

20 Jun '15

So is the architectural debate over, or are people just tired of arguing? Frankly, there's been so much back and forth that I don't know what's expected any more. As I understand it, some nodes are on the IPIP mesh, some not. Some are reachable through amprgw, some not. What a mess. If the debate is over and there is consensus on a standard gateway architecture, then someone needs to publish it. I'm thinking the design should include a diagram of how to address the interfaces (which tunnels need AMPR addresses, which don't), where NATing occurs, what the ampr routing table should look like, what the ip rules should look like, etc. Otherwise, I guess it's up to each individual person to parse through the last 100 or so emails to figure out what they're going to do. Maybe I'll find time to do that . Someday. And folks wonder why there's not more participation . Michael N6MEF

3 2

portal purge
by Brian Kantor 19 Jun '15

19 Jun '15

At my request, we're cleaning out obsolete entries from the portal. A reminder is sent after 3 and 6 months with no login. A warning is sent after 9 months with no login. A notice is sent after 12 months with no login. After 15 months, the user, their network allocations, and any gateways belonging to them are deleted. At the current time, there are 3 gateways and 70 allocations to be so deleted. - Brian

8 20

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net June 2015