On 11/26/13 5:28 PM, Brian Kantor wrote:
Not really. We probably should. I'm a little unclear on exactly what would be required and how much it's going to cost.
- Brian
I'm happy to help out, as it's quite easy to fill out the SWIP forms and then submit it. We could setup rwhois for the 44/net space, but that might be a bit much for us as the portal is not always available.
ARIN should not charge a fee to administrator resources for legacy users:
10. I have legacy resources registered in ARIN's Whois database but have no plans to sign the LRSA. Will ARIN continue to maintain my records, and can I still make database changes to my records if I need to?
ARIN will continue to process requests from the authorized points of contact of legacy resources for updates to their registration records. Currently, there is no community driven policy specifically prohibiting ARIN from processing updates to records that are not covered under a LRSA or RSA, although that could change in the future.
info on swip is here https://www.arin.net/resources/request/reassignments.html
Basically you could swip the regional blocks to the regional admins, and when they assign them they swip the assigned blocks to end users. This would fix the in-addr.arpa mapping too, which as of now does not exist for anything on AMPRNET.
Thoughts?
We could setup rwhois for the 44/net space, but that might be a bit much for us as the portal is not always available.
The portal is supposed to be 7/24; with a few outages it's been quite readily available as far as I know. There is a project (currently dormant, I think) to provide a whois service on the portal.
in-addr.arpa mapping too, which as of now does not exist for anything on AMPRNET.
I don't understand what you mean by that; I thought we were doing a good job of providing in-addr entries for every registered host. What am I missing?
- Brian
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
You may want to look at:
http://modwhois.sourceforge.net/
mod_whois enables Apache (version 2) to receive standard WHOIS queries, and rewrites them to standard HTTP requests. The request can then be processed by the usual means (static content, CGI's, PHP, tomcat, whatever).
We could be providing more specific information then what's possible via ARIN. Especially if an IP is not part of a BGP "sub-announcement" and has not reverse DNS, we could just return that this IP is NOT connected to the Internet, however when queried from within AMPR/44net, we could return more information. The internet really doesn't need to know about unconnected addresses.
Also we don't collect addresses and phone numbers etc, we register IP addresses mainly to callsigns. At the end some privacy should be guaranteed to the outside, we may still provide more information if queried from within AMPR/44net.
73 de Marc, LX1DUC
On 26/11/2013 23:41, Bryan Fields wrote:
(Please trim inclusions from previous messages) _______________________________________________ On 11/26/13 5:28 PM, Brian Kantor wrote:
Not really. We probably should. I'm a little unclear on exactly what would be required and how much it's going to cost. - Brian
I'm happy to help out, as it's quite easy to fill out the SWIP forms and then submit it. We could setup rwhois for the 44/net space, but that might be a bit much for us as the portal is not always available.
ARIN should not charge a fee to administrator resources for legacy users:
- I have legacy resources registered in ARIN's Whois database
but have no plans to sign the LRSA. Will ARIN continue to maintain my records, and can I still make database changes to my records if I need to?
ARIN will continue to process requests from the authorized points of contact of legacy resources for updates to their registration records. Currently, there is no community driven policy specifically prohibiting ARIN from processing updates to records that are not covered under a LRSA or RSA, although that could change in the future.
info on swip is here https://www.arin.net/resources/request/reassignments.html
Basically you could swip the regional blocks to the regional admins, and when they assign them they swip the assigned blocks to end users. This would fix the in-addr.arpa mapping too, which as of now does not exist for anything on AMPRNET.
Thoughts?
On Wed, 27 Nov 2013, Marc, LX1DUC wrote:
Also we don't collect addresses and phone numbers etc, we register IP addresses mainly to callsigns. At the end some privacy should be guaranteed to the outside, we may still provide more information if queried from within AMPR/44net.
Not sure how other countries handle privacy but at least in the US all amateur radio operator licensee data is publicly searchable on the FCC website:
http://wireless2.fcc.gov/UlsApp/UlsSearch/searchAmateur.jsp
Hello All
I have downloaded Maiko's JNOS2_0 Native windows test version
I hope experiment to use it to drive my TH7De and TS2000e internal TNC's or a TNC2 clone, as I use years ago with a DOS version.
Using an 'old' legacy com2 port (D9/D25 socket I would use an attach statement in the following format to drive a TNC attach asy 0x2f8 3 ax25 tnc0 2048 256 9600 cr Running under windows XP
So the question I am asking. How would one connect using a USB/Serial com adapter.
The Radios work find in ax25 packet using a DOS program PaKet which I have used for decades.
Which I recently have it running Under Ubuntu/DOSBOX and Win7 PRo/XP mode/DOS.(Because a club member wanted to do this)
I do not want to use a soundcard at the moment on the 1200bd and 9600bd Radio Interfaces here.
It's going to be a challenge to 'rebrew' a suitable autoexec.nos file anyway.
Of course this may not be supported in the test jnos2 windows version
Look forward to comments. Paul G4APL (SysOP GB7CIP)
-
Antonio Querubin -
Brian Kantor -
Bryan Fields -
Marc, LX1DUC -
Paul Lewis