44net

44net@mailman.ampr.org

2 participants
3170 discussions

by Chris Smith

Hi Folks, A new Wiki was setup a little while ago: http://wiki.ampr.org Unfortunately it got vandalised and there were only a couple of minor contributions. I've reset it, this time with restricted edit rights. If you wish to contribute ( and the hope is that many will ), please drop me an email and I will set you up a login. All I need is your preferred username and email address, I will assign a random password and email it back to you. Thanks, Chris - G1FEF

11 years, 11 months

Zconvers Map

by Kutche, Jerry (Mitchell) USA

I was lost and now I am found! 73 Thanks everyone for the help.. And push to try again.. Jerry Kutche Electrical Supervisor Lehigh Cement Company LLC 180 N. Meridian Road Mitchell, IN 47446 Phone: (812) 849-2191 ext. 251 Fax: (812) 849-5007 Cell: (812) 583-0445 jkutche(a)lehighcement.com<mailto:jkutche@lehighcement.com> www.lehighcement.com<file:///C:\Documents%20and%20Settings\kmundy\Application%20Data\Microsoft\S…> This e-mail may contain confidential and/or legally privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

11 years, 11 months

WWconvers Node Registry

by Charles Hargrove

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

11 years, 11 months

[cisarnet.ampr.org] - Filtering OSPF Hellos from CisarNet solved

by renzorossi＠libero.it

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 >

11 years, 11 months

(no subject)

by Don Moore

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

11 years, 11 months

Discussion about JNOS 'slowness' ...

by Maiko Langelaar

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 >

11 years, 12 months

Re: [44net] INP3 recent work?

by Matt VK2RQ

> 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

12 years

Gateway entry / pub routing

by Jason R Begley

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

12 years

Re: [44net] AMPRNet Gateways update

by Kutche, Jerry (Mitchell) USA

?? ----- 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

12 years

Re: [44net] AMPRNet Gateways update

by Eddie Olson

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

12 years

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net