44net September 2013

44net@mailman.ampr.org

48 participants
32 discussions

44.133.48.66 !!!
by Maiko Langelaar 12 Apr '14

12 Apr '14

Good afternoon, It would see that 44.133.48.66 is popping, snmpding, and other amounts of traffic from time to time to various ampr.org systems and doing so *without warning* type of thing. I just got hit with a bunch of SNMP requests, others have been hit with POP requests. Can anyone find out who the owner of that particular system or network is, so that I can contact the entity or person. Or perhaps a bit more draconian, can someone deal with it. Thanks in advance. Maiko Langelaar VE4KLM

4 5

Re: [44net] How to use my IP 44.xx.xx.xx
by Robbie De Lise 28 Sep '13

28 Sep '13

Andre, Please register a new subnet or ip at the portal first. If you like you can connect your new subnet/ip to the internet through hamnetbe vpn or 5ghz wifi link if a node is available in your area. We are currently not yet linked to the rest of ampr but are looking into it. https://portal.ampr.org/networks.php?a=region&id=304 Thank you Robbie ON4SAX 44.144 Coordinator Op 15 sep. 2013 12:58 schreef "on4hu" <on4hu.0(a)gmail.com> het volgende:

4 13

community-wide networking discussion group
by Brian Kantor 23 Sep '13

23 Sep '13

Projects such as HAMWan are community-wide networking. Are there any mailing lists where people who are actively working on or planning to construct such networks, or should I start one such? - Brian

3 2

Portal
by Brian Rogers 22 Sep '13

22 Sep '13

Is the portal offline? I don't appear to get a connect to it. -- 73 de Brian Rogers - N1URO email: <n1uro(a)n1uro.ampr.org> Web: http://www.n1uro.net/ Ampr1: http://n1uro.ampr.org/ Ampr2: http://nos.n1uro.ampr.org Linux Amateur Radio Services axMail-Fax & URONode AmprNet coordinator for: Connecticut, Delaware, Maine, Massachusetts, New Hampshire, Pennsylvania, Rhode Island, and Vermont.

2 2

DNS
by ian 22 Sep '13

22 Sep '13

Hello, I am new to this and would like to ask the following question : - What is considered a reasonable time for a response to change/add a DNS ?? Ian..

1 0

(no subject)
by Robbie De Lise 22 Sep '13

22 Sep '13

44.144.123.7 add a ups.on3dga 44.144.123.11 add a bi.on3dga 44.144.123.12 add a voipserver.on3dga 44.144.123.2 add a coreswitch.on3dga

1 1

TAPR/ARRL DCC 2013
by Brian Kantor 20 Sep '13

20 Sep '13

I'll be at the TAPR/ARRL DCC 2013 is this Friday-Sunday in Seattle. I'd be happy to get together with any of the AMPRNet folks; I'll be at both of the lunches, the Friday night social event, and the banquet. Perhaps we can find some place to gather and chat about what's going on and what's in the future for network 44. At this point there is only a preliminary schedule posted on the TAPR web site so I don't know exactly when and where we will meet, but feel free to stop me and chat. - Brian

3 2

Att: Chris G1FEF
by Brian Rogers 17 Sep '13

17 Sep '13

Chris; I sent you an email as per your request, but no reply. Just want to insure you received this one ok. -- 73 de Brian Rogers - N1URO email: <n1uro(a)n1uro.ampr.org> Web: http://www.n1uro.net/ Ampr1: http://n1uro.ampr.org/ Ampr2: http://nos.n1uro.ampr.org Linux Amateur Radio Services axMail-Fax & URONode AmprNet coordinator for: Connecticut, Delaware, Maine, Massachusetts, New Hampshire, Pennsylvania, Rhode Island, and Vermont.

3 3

(no subject)
by Robbie De Lise 17 Sep '13

17 Sep '13

on0ck del

2 1

Re: [44net] 44Net Reboot (DNS)
by Rob Janssen 16 Sep '13

16 Sep '13

> Subject: > Re: [44net] Reboot (DNS) > From: > Brian Kantor <Brian(a)UCSD.Edu> > Date: > 09/13/2013 01:59 PM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu> > > The goal is to have every DNS entry belong to someone who is registered > with the portal, so that when that person becomes inactive (defined > as no longer keeping their portal registration current despite annual > reminders), the DNS entry will also become inactive, and after a year > or so, be expunged. That way we can reclaim addresses and also prevent > the DNS from being full of obsolete data. > > What we have to work with is a database that has only the DNS information > for the vast majority of its entries. For the past few years, it has > also been recording the timestamp and author of the entry. So the plan > in general (details are still to be worked out) is to convert entries > which match registered portal users either in the hostname or in the > author field. That will have the effect of leaving out most of the > obsolete entries but should retain most relevant (active) ones. What we have (again) learned from the first step, the migration of the gateway entries, is that the method of matching and validating the existing entries with the new portal users cannot be "send an e-mail to a single person who will handle it". I tried to convince a couple of operators to refresh their info in the portal but when they can only create a new entry and cannot move their existing info into it, and have no reply to their mail after a month, they lose interest and won't be pursuing this anymore. And I am not going to ask them over and over again. When the same has to be done for all the end-user registrations, it will be a nightmare to get it completed. But of course *some* validation has to be done. Rob

9 9

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net September 2013