With the kind assistance of Jim Fuller, Maiko Langelaar and Chris Smith
have been working on an update of the AMPR gateways processing system.
That project is now ready for service.
Beginning October 15th 2012, updates to the gateways will be processed
on a new host, portal.ampr.org, and the encap file will be distributed
from there. Both email distribution and ftp retrieval are supported,
as they were with the previous ampr-gateways host.
The new gateways robot mailing address is
gateways(a)ampr.org
Your logins and passwords from the previous gateways system should continue
to work on the new portal. The syntax and content of the various commands
and parameters for the robot are quite similar to the previous version; you
can get the details from the manual page for the new robot.
https://portal.ampr.org/gateways_manpage.php
I would like to personally thank Jim Fuller for his many years of service
to the AMPRNet gateways community and wish him well. We couldn't have
done it without you! Thank you, Jim!
- Brian
PS: My apologies if you receive more than one copy of this note.
Could be useful to distinguish, as an Internet domain registration, the
Organization (Registrant), from Legal representative (admin contact), from Tech
representative (tech Contact), and NSP references (as a Registrar contact) ? In
this way should be:
Organization name:
Organization postal address:
Organization email:
[Modified] Admin Representative name:
[Modified] Admin Representative callsign:
[Modified] Admin Representative email:
[Modified] Admin Representative telephone:
[New] Tech Representative name:
[New] Tech Representative callsign:
[New] Tech Representative email:
[New] Tech Representative telephone:
Width of network requested (CIDR Notation):
Estimated number of subnets this will be divided into:
Estimated number of hosts on all subnets combined:
Network Service Provider name:
NSP postal address:
NSP telephone:
NSP email contact:
NSP ASN:
Ciao from Italy!
IW0SAB Renzo
>----Messaggio originale----
>Da: Brian(a)UCSD.Edu
>Data: 20/11/2012 19.21
>A: <44net(a)hamradio.ucsd.edu>
>Ogg: [44net] DRAFT directly routed subnets supplemental information form
>
>(Please trim inclusions from previous messages)
>_______________________________________________
>Here's a draft copy of the form that we're going to be asking people
>applying for directly routed subnets (BGP folks) to complete so that
>we can get the show on the road. I hope to start allocating those in
>early December.
>
>Anyone have suggestions or objections?
> - Brian
>
>===========================================================================
>Amateur Radio Digital Communications Inc
>
>Application for Directly Routed (CIDR delegated) Subnet
>
>Please provide the requested information regarding the organization/person
>to whom the addresses will be licensed.
>
>By submitting this form you affirm that you have read and agree to the
>Acceptable Use and Terms of Service attached herein.
>----------------------------------------------------------------------------
>
>Organization name:
>
>Organization postal address:
>
>Organization email:
>
>Representative name:
>
>Representative callsign:
>
>Representative email:
>
>Representative telephone:
>
>Width of network requested (CIDR Notation):
>
>Estimated number of subnets this will be divided into:
>
>Estimated number of hosts on all subnets combined:
>
>Network Service Provider name:
>
>NSP postal address:
>
>NSP telephone:
>
>NSP email contact:
>
>NSP ASN:
>
>----------------------------------------------------------------------------
>
>(TOS would be attached here.)
>_________________________________________
>44Net mailing list
>44Net(a)hamradio.ucsd.edu
>http://hamradio.ucsd.edu/mailman/listinfo/44net
>
In response to advice from some of you, we've added two new
clauses to the terms of service. These are
> ARDC's license of address(es) to You grants You a limited, non-exclusive,
> non-transferrable, non-assignable, and terminable right to use the
> address(es) in accordance with this Agreement and Terms solely for the
> purposes stated herein. The duration of this license is five (5) years,
> renewable upon Your request and consent to these Terms and Agreement
> and subject to the discretion of ARDC.
and
> You may cancel this license at any time and for any reason by contacting
> ARDC in writing and receiving acknowledgement of such request. Usage of
> the address(es) must cease effective with the license cancellation.
The full Terms of Service Agreement may be found on the AMPR web site
http://www.ampr.org/
And may I gently remind folks that there is a DONATE button on that web site;
we're still over $1,000 in debt at this point, all of it out of my pocket.
Any amounts would be greatly appreciated.
- Brian
Here's a draft copy of the form that we're going to be asking people
applying for directly routed subnets (BGP folks) to complete so that
we can get the show on the road. I hope to start allocating those in
early December.
Anyone have suggestions or objections?
- Brian
===========================================================================
Amateur Radio Digital Communications Inc
Application for Directly Routed (CIDR delegated) Subnet
Please provide the requested information regarding the organization/person
to whom the addresses will be licensed.
By submitting this form you affirm that you have read and agree to the
Acceptable Use and Terms of Service attached herein.
----------------------------------------------------------------------------
Organization name:
Organization postal address:
Organization email:
Representative name:
Representative callsign:
Representative email:
Representative telephone:
Width of network requested (CIDR Notation):
Estimated number of subnets this will be divided into:
Estimated number of hosts on all subnets combined:
Network Service Provider name:
NSP postal address:
NSP telephone:
NSP email contact:
NSP ASN:
----------------------------------------------------------------------------
(TOS would be attached here.)
I am interested.. If no one else is...
----- Original Message -----
From: 44net-bounces+jkutche=lehighcement.com(a)hamradio.ucsd.edu <44net-bounces+jkutche=lehighcement.com(a)hamradio.ucsd.edu>
To: 44net(a)hamradio.ucsd.edu <44net(a)hamradio.ucsd.edu>
Sent: Tue Nov 13 16:26:45 2012
Subject: [44net] Gateway entry / pub routing
(Please trim inclusions from previous messages)
_______________________________________________
There is a tunnel on the encap list that needs correction (recursive
routing):
route addprivate 44.131.192/29 encap 44.131.192.1
I have also noticed that routing from the public internet doesn't go any
further than the 132.239.255.131 host at UCSD, but I've only spot test a
few hosts other than myself.
If anyone is interested in using a Cisco router for GW connectivity, I
have a 7206 (non VXR) chassis(empty) up for grabs/trade.
73
Jason
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net
> Actually, ampr encap uses proto 4 (IPIP), proto 94 being obsolete.
> 73s de Marius, YO2LOJ
Thanks for clarifying that for me Marius! KA9Q still gets a mention in
IOS 12.4 though.
73
Nick.
Jason,
This is my IOS config for a 1721 but should work on other routers with
an AUX port.
The aux port corresponds to line 5 (show line will identify it).
Encapsulation is set to slip but you can also set it to ppp. Connection
to a PC serial port is via a normal Cisco (blue) rollover cable.
!
interface Async5
ip address 192.168.44.1 255.255.255.0
encapsulation slip
async mode dedicated
!
!
line aux 0
modem InOut
transport input all
flowcontrol hardware
rxspeed 19200
txspeed 19200
!
!
I would be most interested to see your perl script
Regards,
Nick.
Hello,
New to the list although I do have some JNOS experiences from 12+ years
ago. FIrstly, I seem to have volunteered myself as co-ordinator for
amprnets in my part of the UK - 44.131.[56-62] so I'd like to thank my
predecessor John G1HTL for his efforts over the past couple of decades.
I'm trying to discover what the best practice is for routing 44net
traffic based upon what I can see in the encap file. Presumably each one
of these is a tunnel, what would be defined in Cisco-speak as "tunnel
mode nos" (protocol 94)?
I'm experimenting here with the G8PZT Xrouter software which runs under
dos and provides ip connectivity to radio links. I have a spare Cisco
1721 that I've connected to Xrouter with a SLIP link to the aux port on
the router and once I figure out how to get encap routing up and running
I may be able to provide 44net access via a radio port (subject to UK
licensing of course ) .
I'm interested to know what other folks are using to route 44net over
the internet?
Regards,
Nick.
Guys
Wish to notify our site is down -
Due to an adsl fault - the cable was cut and awaiting it to be rejoined.
The temp fix they did a few months back has failed
Regards
Sam
Amateur Radio Callsign: VK4FQ / VK4TTT
Owner: VK4RCN P25 Repeater Cairns
Sysop: APRS Cairns
Mobile: VK4FQ-9 (vhf) VK4FQ-15 (Hf)