44net

44net@mailman.ampr.org

3198 discussions

WWconvers Node Registry
by Charles Hargrove 10 Jan '13

10 Jan '13

The sysops of the following WWconvers nodes need to contact SP1LOP, by registering at http://www.wwconvers.ampr.org/wwcbook/addwwc.html, with station details to be accurately placed on the map at http://www.wwconvers.ampr.org (or else your station will be lost at sea in the South Pacific). :-) BWATER_NS LAXNET_US N9LYA WARDCOVE2 -- Charles J. Hargrove - N2NOV NYC ARECS/RACES Citywide Radio Officer/Skywarn Coord. NYC-ARECS/RACES Net Mon. @ 8:30PM 147.360/107.2 PL http://www.nyc-arecs.org and http://www.nyc-skywarn.org NYDXA SWL & Scanner Net Wed. @ 9PM 147.360/107.2 PL http://www.n2nov.net "Information is the oxygen of the modern age. It seeps through the walls topped by barbed wire, it wafts across the electrified borders." - Ronald Reagan "The more corrupt the state, the more it legislates." - Tacitus "Molann an obair an fear" - Irish Saying (The work praises the man.) "No matter how big and powerful government gets, and the many services it provides, it can never take the place of volunteers." - Ronald Reagan

5 5

[cisarnet.ampr.org] - Filtering OSPF Hellos from CisarNet solved
by renzorossi＠libero.it 01 Jan '13

01 Jan '13

Ciao Don, we are tuning CisarNet for managing directly delegated CIDR 44.208/16...So I missconfigured our main gateway.. Now it should be OK. Please let us know. Sorry ;-) Ciao from Italy. IW0SAB Renzo. >----Messaggio originale---- >Da: ve3zda(a)gmail.com >Data: 31/12/2012 17.51 >A: <44net(a)hamradio.ucsd.edu> >Ogg: [44net] (no subject) > >(Please trim inclusions from previous messages) >_______________________________________________ >Whoever owns station iq0rf.cisarnet.ampr.org. please top transmitting >to ve3zda.ampr.org. >It's been repeatedly sending encapped lines since yesterday and getting >nowhere of course.... > >here's an example of the line I'm getting...ever second or two..... > >16:37:34.478957 IP 94.101.48.134 > 192.168.1.150: IP 44.208.0.1 > >224.0.0.5: OSPFv2, Hello, length: 56 (ipip-proto-4) > >73, Don - ve3zda >_________________________________________ >44Net mailing list >44Net(a)hamradio.ucsd.edu >http://hamradio.ucsd.edu/mailman/listinfo/44net >

1 0

(no subject)
by Don Moore 31 Dec '12

31 Dec '12

Whoever owns station iq0rf.cisarnet.ampr.org. please top transmitting to ve3zda.ampr.org. It's been repeatedly sending encapped lines since yesterday and getting nowhere of course.... here's an example of the line I'm getting...ever second or two..... 16:37:34.478957 IP 94.101.48.134 > 192.168.1.150: IP 44.208.0.1 > 224.0.0.5: OSPFv2, Hello, length: 56 (ipip-proto-4) 73, Don - ve3zda

1 0

Discussion about JNOS 'slowness' ...
by Maiko Langelaar 28 Dec '12

28 Dec '12

Just something I've noticed, I'm sure there are gurus on here that can add to it, or totally take it apart - I'd like to hear your thoughts. > First of all, I hope everyone had an okay christmas. As well, I > would like to wish everyone the best for the upcoming new year. > > Has JNOS always been 'slow' ? > > This might be hard for me to explain, but when you are connected > to a JNOS station and you hit enter to send a command, you may have > noticed it might take a 'second' for it to be 'processed'. It's not > a lightning fast response time is it now. I noticed this while trying > to connect to my own JNOS via a 3 'wire' led/phototransistor dummy > serial load (bounces data right back at the same interface). And to > be frank, I've noticed it in many other occasions. Forwarding should > never take so long, netrom is always painfully slow, and so on. > > Was it always like this (for the linux version) ? > > Or did this start happening back when I did the kernel change, back > when I was somewhat forced to use the setcontext() functions instead > of setjmp() calls and such. Version 2.0e and earlier use setjmp() > methodology, 2.0f and older use the setcontext() functions. > > Was the DOS version the same too ? > > SOOOO - Want to see JNOS go like lightning ? It's easy enough : > > edit timer.h, change MSPTICK to 1 (normally it's 55) > > rm domain.o main.o rspf.o timer.o unix.o > > make > > CONSEQUENCES - your timers will expire much faster now, but the system > clock will be fine. But as an experiment, give it a try, tell me what you > think. Not sure if this was always the way it was, perhaps due to inadequate > CPU for it's time, I don't know. > > I'm going to play with this a bit, a patch will be released in the near > future so that the timers behave, but JNOS will suddenly come to life ! > > I've known about this for some time, but my experimenting that I've been > doing over the christmas holidays kinda brought it up again. Never thought > how noticing the delay between laser diode flashes can refresh one's memory > on the topic. > > Maiko Langelaar / VE4KLM >

1 0

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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net