44net

44net@mailman.ampr.org

3194 discussions

Re: [44net] INP3 recent work?
by Matt VK2RQ 19 Dec '12

19 Dec '12

> howdy all, have been looking into inter-operability of INP3 with netrom > quality-based routing, and see there has been work done for older > kernels but cannot find anything recent: > > http://sharon.pi8zaa.ampr.org/users/pe1rxq/inp3.html > > > Maiko has ported this code to jnos I believe, but I don't see any > linux-native ports of the code more recent than kernel 2.6.4...I'm > running linux mint 10 and > mint 13 in my machines, and the kernel is much newer, haven't tried the > patch yet on the newer 3.0+ kernels, anyone had any experience with this? > Cheers, > John Hi John, I ported the patch to kernel 2.6.35, which I believe is what Mint 10 is based on. However, I found serious deadlock issues that arise when nodes are withdrawn. For details, and a link to the ported patch, see my post here: http://www.spinics.net/lists/linux-hams/msg03116.html 73, Matt VK2RQ

2 1

Gateway entry / pub routing
by Jason R Begley 12 Dec '12

12 Dec '12

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

2 3

Re: [44net] AMPRNet Gateways update
by Kutche, Jerry (Mitchell) USA 29 Nov '12

29 Nov '12

?? ----- Original Message ----- From: 44net-bounces+jkutche=lehighcement.com(a)hamradio.ucsd.edu <44net-bounces+jkutche=lehighcement.com(a)hamradio.ucsd.edu> To: 'AMPRNet working group' <44net(a)hamradio.ucsd.edu> Sent: Thu Nov 29 01:33:46 2012 Subject: Re: [44net] AMPRNet Gateways update (Please trim inclusions from previous messages) _______________________________________________ Hi Chris, I have an existing entry I need transferred so that I can manage it as I need to change my tcpip address. Username on new system is eddie. Entery to transfer is route addprivate 44.147/16 encap 121.98.130.16 73 and thanks Eddie Olson ZL2AQY -----Original Message----- From: 44net-bounces+eddie=olson.net.nz(a)hamradio.ucsd.edu [mailto:44net-bounces+eddie=olson.net.nz@hamradio.ucsd.edu] On Behalf Of Chris Smith Sent: 09 October 2012 21:45 To: AMPRNet working group Subject: Re: [44net] AMPRNet Gateways update (Please trim inclusions from previous messages) _______________________________________________ Another point I should mention concerning the new portal and Gateways robot: All of the current Gateway data has been imported into the new system. This means that if you already have a gateway registered on the current system, it will be present on the new system, so there is no need to add it. The downside to this, is that if you register on the portal to manage your gateway, it will not simply "appear" on your account. This is because it is already present on a default account. The solution is to contact me with your gateway details (Username as registered on the portal, Gateway IP and Subnets serviced) and I will transfer it across to your account. Thanks, Chris G1FEF _________________________________________ 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 1

Re: [44net] AMPRNet Gateways update
by Eddie Olson 29 Nov '12

29 Nov '12

Sorry ignore the previous message it went to the wrong address. my apologies. Eddie ZL2AQY

1 0

AMPRNet Gateways update
by brian＠UCSD.Edu 29 Nov '12

29 Nov '12

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.

7 7

R: DRAFT directly routed subnets supplemental information form
by renzorossi＠libero.it 22 Nov '12

22 Nov '12

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 >

1 0

gateways wiki
by kb9mwr＠gmail.com 22 Nov '12

22 Nov '12

http://wiki.ampr-gateways.org/ isn't responding :-( http://wiki.ampr.org/index.php/Main_Page Empty. Were there plans to move Jim's wiki to the main ampr site, or ?

5 6

20 Nov '12

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

1 0

DRAFT directly routed subnets supplemental information form
by Brian Kantor 20 Nov '12

20 Nov '12

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.)

4 5

Re: [44net] Gateway entry / pub routing
by Kutche, Jerry (Mitchell) USA 13 Nov '12

13 Nov '12

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

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net