44net

44net@mailman.ampr.org

4 participants
3198 discussions

Re: [44net] 44Net Digest, Vol 5, Issue 12
by f5pbg＠free.fr 12 Jan '16

12 Jan '16

Le 12/01/2016 20:00, 44net-request(a)hamradio.ucsd.edu a écrit : > The original suggestion was that there was a way to bypass simple > address assignment by automating the process. No possible i think, because we must verify the real identity of the persons requesting IPand if this verification is automatic it will be very easy to pirat the system... For example if I have a doubt about the person, I phone him to check the identity. An automatic system can do this. ;o) Best regards, Ludovic - F5PBG.

1 0

Re: [44net] Verifying the identities of IP coordinators
by ve1drg 12 Jan '16

12 Jan '16

Third ed it.. --Ted Gervais 1464 luxury aveWindsor OntarioN8p0a9 -------- Original message -------- From: ve1jot <ve1jot(a)eastlink.ca> Date: 2016-01-12 12:00 AM (GMT-05:00) To: AMPRNet working group <44net(a)hamradio.ucsd.edu> Subject: Re: [44net] Verifying the identities of IP coordinators (Please trim inclusions from previous messages) _______________________________________________ seconded! On 16-01-10 01:40 PM, Paul Lewis wrote: > (Please trim inclusions from previous messages) > _______________________________________________ > Thank you Brian for those kind words > and also for the work you do and your team in the background support > for the past 25+ years > paul g4apl > In message <20160110145927.GA32116(a)UCSD.Edu>, Brian Kantor > <Brian(a)UCSD.Edu> writes >> (Please trim inclusions from previous messages) >> _______________________________________________ >> There seems to be some confusion here. The discussion was never about >> verifying the identities of coordinators. >> >> The original suggestion was that there was a way to bypass simple >> address assignment by automating the process. >> >> I explained at the time that the coordinators perform a valuable service >> that can't be automated in any practical way. >> >> In fact, many coordinators do far more than assign addresses - they >> consult with users and provide assistance in getting their stations on >> the net. Many of the people currently using AMPRNet would not have been >> able to do so without the help of their local coordinator. >> >> I think the coordinators, many of whom have been performing that service >> for years, deserve a round of thanks from the community. They certainly >> have my appreciation for their hard work and dedication. >> - Brian >> >> _________________________________________ >> 44Net mailing list >> 44Net(a)hamradio.ucsd.edu >> http://hamradio.ucsd.edu/mailman/listinfo/44net > _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net

1 0

mail relay for *.ampr.org adress or IP ?
by R P 10 Jan '16

10 Jan '16

Id there any SMTP server (mail relay) that can pickup any from *.ampr.org email adrss or any 44.** IP adtress and can send it to the outside world ? If yes what its ip adress ? Thanks Forward Ronen - 4Z4ZQ http://www.ronen.org

1 0

Verifying the identities of IP coordinators
by Bill Horne 09 Jan '16

09 Jan '16

> The question of automating address assignment has been looked into; > about the only way it could be done would be if we had a secure method > of making sure that the applicant is a bona fide ham radio operator. > At the moment, the only known automated way of doing this is to use > Logbook of the World certificates, which greatly restricts the number > of people who could prove their eligibility and has its own set of > problems. Brian, The problem of knowing who we're corresponding with is as old as the written word. I feel that PKI provides the best solution available. I'm not familiar with LOTW, but I know the PKI process well, and I'm confident that it provides a simpler and more robust solution. There are, of course, many different ways to implement a secure process: for the moment, I'll ask that we leave aside the implementation details and talk about the idea. We could use a secure web site to give access to coordinators, or restrict ssh access to key holders, or accept only signed emails: the process is essentially the same for all. It boils down to authentication: we can issue private keys to every coordinator who seeks to use an automated process to issue IP addresses. * PGP/GPG users have access to "Keysigning parties" where other keyholders will verify their meatspace identities by inspecting their drivers license, passport, etc. * SSH and SSL users could, in theory, employ the keysigning process to verify their identity, even though it's not customary. They could also provide letters from attorneys or ministers or other public figures, attesting to their identities, in the same manner that Thawte used to verify X.509 certificates. Long story short, LOTW isn't the only way to verify an identity. There are other methods, already implemented and available, which can be used instead. Bill, KW4OC

2 1

Re: [44net] Coord delay
by f5pbg＠free.fr 09 Jan '16

09 Jan '16

Le 08/01/2016 20:00, 44net-request(a)hamradio.ucsd.edu a écrit : > Delays of months and years by coordinators continues to be heard Some coordinators works very slow... For me i validate IP ask in few hours and sometimes few days (week-end...). I create a subnet for some friends in order to have an IP more faster for them because the coord does not validate the IP. It will be nice to have an alert to the big admin of ampr.org when a IP ask is not validate after two weeks (for example). Then, itwill be nice to change the local coordif he does not do his job in ham'spirits conditions... ;o) Best regards, Ludovic - Coord 44.151

1 0

locked
by Dale Yanz 08 Jan '16

08 Jan '16

Hi All Question is that am I being locked out ? 44.125.10.0/24 0 0.0.0.0 E 0 0 Locked Dale KJ6IX

8 13

Re: [44net] Is someone read the contact us in the portal ?
by Rob Janssen 08 Jan '16

08 Jan '16

> Subject: > Re: [44net] Is someone read the contact us in the portal ? > From: > Brian Kantor <Brian(a)UCSD.Edu> > Date: > 01/08/2016 06:53 PM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu> > > > The question of automating address assignment has been looked into; > about the only way it could be done would be if we had a secure method > of making sure that the applicant is a bona fide ham radio operator. > At the moment, the only known automated way of doing this is to use > Logbook of the World certificates, which greatly restricts the number of > people who could prove their eligibility and has its own set of problems. Also the experience with automation projects is that they often get stranded partly completed, for all kinds of reasons. The question often is what is better: a working manual system or a partially finished automated system that does not offer the flexibility that a manual system has. (e.g. w.r.t. correcting mistakes, accommodating special situations, handling a large batch of updates, etc) Rob

1 0

Re: [44net] How to update the AMPR.ORG DNS records ?
by Steve L 07 Jan '16

07 Jan '16

Kind if wondering the status of this myself. Perhaps the easiest would be to amend the present email robot to ask for a username and password field (kind of how the old gateways robot worked) so the end user can edit their own entries? >Hi there >How do I update the AMPR.ORG DNS records ? >The Portal write that the web page that there is a test and records will >not apear in the real AMPR.ORG zone file >and the email system i used to sent updates to reply with error >Please advice >Thanks Forward >Ronen - 4Z4ZQ >http://www.ronen.org

7 6

IPR Net44
by Dale Yanz 06 Jan '16

06 Jan '16

Hi When I perform a IPR this is what I show for me 44.125.10.0/29 0 0.0.0.0 E 0 0 Locked I don't understand ? what it is showing ? My IP is 44.125.10.1 Network 44.125.10.0/24 Also how do I make sure or determine the correct IPNETMASK ? Is this the same as my subnet mask when I perform a ipconfig ? Then what would be my correct IPNetmask ? On my BPQ32 config file do I still MAP to a IP ADDRESS ? My NAT 44.125.10.2 (Within my APRNET) 192.168.0.198 ( My ip address of my BPQ32 computer) ;====================================================================== ;AMPR Gateway ;====================================================================== IPGATEWAY Adapter \Device\NPF_{0A50287E-EBE5-456D-BDDF-84BC5F7DB088} 44ENCAP 192.168.1.10 # Enable AMPRNET Tunnels and RIP44. Use 192.168.1.10 as Tunnel IPAddr 44.125.10.1 # IP address of the BPQ32 switch on your LAN IPNetmask 255.255.255.248 # Netmask of your AMPRNet allocation IPPorts 1,9 # BPQ Ports to be used for links to IP systems. List of ports, separated by commas NAT 44.125.10.2 192.168.0.198 **** Dale Yanz KJ6IX Nevada State Emergency Communication Volunteer Douglas County, Nv. Packet Coordinator KJ6IX(a)ARRL.NET

8 9

44net Lock
by Dale Yanz 06 Jan '16

06 Jan '16

Ok let see. I'm going to say correct me if I'm wrong is that I need to upgrade my Router to a more current model. I'm using a D-Link DIR-615 that I picked up at a thrift store for $7.00 U.S.. Don't laugh !!! Ok what would be a choice for a router that would fit the bill !! Still showing up 44.125.10.0/24 0 0.0.0.0 E 0 0 Locked Dale Yanz KJ6IX Nevada State Emergency Communication Volunteer Douglas County, Nv. Packet Coordinator KJ6IX(a)ARRL.NET

6 9

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net