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.
> 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
> Subject:
> Re: [44net] 44Net Reboot (DNS)
> From:
> Neil Johnson <neil.johnson(a)erudicon.com>
> Date:
> 09/15/2013 12:51 AM
>
> To:
> AMPRNet working group <44net(a)hamradio.ucsd.edu>
>
>
> So what do you propose ?
>
> -Neil
We need to have a system where multiple persons can handle
the task in case the one originally assigned to it gets overloaded
or otherwise not available.
Or maybe we could use the login credentials of another system within
the amateur radio world (qrz.com? eqsl?) and trust a user immediately.
(so they can reconfirm their IP addresses without manual confirmation
by the coordinator)
Rob
> Subject:
> Re: [44net] 44Net Reboot (DNS)
> From:
> Chris <chris(a)g1fef.co.uk>
> Date:
> 09/15/2013 09:56 AM
>
> To:
> AMPRNet working group <44net(a)hamradio.ucsd.edu>
>
>
> The migration of the gateway entries has gone quite well, we matched up a good proportion of the old entries. If anyone still has a gateway entry they need to claim, they only have to ask - as far as I am aware all such requests have been processed. If anyone is aware of any "gateway claim" emails that have gone unanswered please let me know.
>
> Thanks,
> Chris
When I login to the portal and get a list of registered gateways, I see
several IP addresses for which there are two entries, usually one of them
with only a description and no subnets. I presume that those are the ones
that correspond to currently open claims for the gateway entry.
(for a new portal user it is possible to setup a new gateway entry, including
external IP address and description, but once they try to enter their subnets
they get stuck because the subnets are already in use on their old entry)
A friend tried to e-mail you several times, but did not get a reply. Then he
tried to guess his old password for the mail robot and after several tries he
got a mail from Maiko who then fixed the situation. Probably not everyone
got that far.
Rob
Thomas,
In lue of an email robot, what if you could submit data using curl?
I understand the you need, but I also understand how complex it could
be two run to update mechanisms
On Fri, Sep 13, 2013 at 02:28:08PM +0200, Thomas Osterried wrote:
> We need the bot. We can't live with a web frontend.
Just curious, has anyone played with the more oddball things that can be done using DNS servers?
I'm aware that DNS requests can be used to tunnel traffic (often used to get around governmental censorship in some countries), and that E.164 can be used to route VoIP calls, but how about some REAL fringe stuff?
I was just thinking that, we're ham radio guys, and we don't really have a standardized way to do something like call CQ and have keyboard-to-keyboard or voice chats! Maybe something can be done using DNS that hasn't really been done before.
Anyone have ideas?
Blaine, K1QV
Sent from my iPhone
I would use my IP 44.144.195.1 via Internet to my JNOS how to use this
IP is there a gateway? a special procedure is it required? it's been
decades that I find space this procedure? or find the information?
Vy73s ON4HU
--
http://on4hu.be/ ftp://ftp.on4hu.be http://on4hu.be:81
COMPUTER ARE LIKE AIR-CONDITIONNERS THE
STOP WORKING AS SOON YOU OPEN WINDOWS
Hi guys..
IP Coordinator for Indiana...
Most of the assignments in our 44.48.x.x range are nolonger in operation... I know we were planning something to address this... what was that plan?
73 jerry
Jerry Kutche
Electrical Supervisor
Lehigh Cement Company LLC
180 N. Meridian Road
Mitchell, IN 47446
Phone: (812) 849-2191 ext. 251
Fax: (812) 849-5007
Cell: (812) 583-0445
jkutche(a)lehighcement.com<mailto:jkutche@lehighcement.com>
www.lehighcement.com<file:///C:\Documents%20and%20Settings\kmundy\Application%20Data\Microsoft\S…>
This e-mail may contain confidential and/or legally privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Yes
44.48.0.46 encap 69.27.54.92
Have you seen the aprs group.
AMPRNet working group (44net(a)hamradio.ucsd.edu)
I can email Brian and see if you can get added to the group..
I need to also get you the link to the amprnet webportal...
73
-----Original Message-----
From: John Wiseman [mailto:john.wiseman@cantab.net]
Sent: Thursday, September 12, 2013 2:30 PM
To: n9lya(a)blueriver.net
Subject: IP Gateway
Jerry,
The IPGateway code in LinBPQ seems be to working ok. It switches packets
between BPQ Ports.
Config is simply
IPGATEWAY
IPPorts 2,4 # List of Ports to be used for IP
****
https://dl.dropboxusercontent.com/u/31910649/linbpq
Do you have an allocation in the 44 network? I'm thinking of trying to add
the amprnet tunnelling code to LinBPQ.
73, John
