| |
PA2AGA > HDDIG 15.10.99 19:23l 214 Lines 7231 Bytes #-9717 (0) @ EU
BID : HD_99_260C
Read: DL6KCF GUEST
Subj: HamDigitalDigest 99/260C
Path: DB0AAB<DB0ZKA<DB0ABH<DB0BOX<DB0MAK<DB0ERF<DB0NHM<DB0SHG<DB0SM<PI8DAZ<
PI8GCB<PI8HGL<PE1MVX<PE1NMB<EA7URC<PE0MAR<PI8VNW
Sent: 991015/1330Z @:PI8VNW.#ZH2.NLD.EU #:8132 [HvHolland] FBB7.00g $:HD_99_260
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : HDDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA21348 ; Fri, 15 Oct 99 12:29:14 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.67/7.5.3) with SMTP
id AA00016415 ; Fri, 15 Oct 99 08:04:02 MET
Date: Fri, 15 Oct 99 08:01:01 MET
Message-Id: <hd_99_260C>
From: pa2aga
To: hd_broadcast@pa2aga
Subject: HamDigitalDigest 99/260C
X-BBS-Msg-Type: B
> >
> > I have Linux.
> > Did not find any such software.
> > Most hams do not (and will not) have Linux.
> > So Linux is not of interest to me.
>
> Didn't find: Well, you need the package called "ax25-utils".
> The file [/usr/src/]linux/Documentation/networking/ax25.txt tells you
> where to get this, and the "how-to" file.
I have ax25-utils.
Where is NET/ROM?
Where is a HAL P38 / PCI400 driver?
Where is the server to gateway telnet <-> net/rom <-> CLOVER <-> PACTOR?
Where is the BBS message <-> smtp gateway?
Where is the BBS bulletin <-> nntp gateway?
Where is NET/ROM over Ethernet?
Where is IP over NET/ROM?
> Software: Except for above, everything else comes in the "network"
portion of
> the distribution. Also, recompile the kernel for AX.25 support.
I did this. Simple. And I had nothing useful.
It did not route IP over NET/ROM, just for one example.
See above "Where is".
> Most hams do not ...: Any evidence to back this assumption? Also, since
Linux
> is free, cost isn't a problem (yes, most hams I know are cheap).
>
> Not of interest to you: That's not debatable.
>
> > But in any case I am not looking for solutions. Those I can create.
> >
> > I am looking for ideas about WHAT problems might be solved,
> > and how the applications that implement those solutions might
> > be structured so they would be of interest to hams.
>
> THe one big problem is the "anarchy" problem. Everyone does their own
thing or
> wants to be the "big fish of the pond," etc. Good luck with this one.
Suggestions?
> > Your points about installation are well taken, and "simple"
> > installation is a part of what I am working on now.
>
>.
------------------------------
Date: Wed, 13 Oct 1999 08:16:07 -0700
From: "Hank Oredson" <horedson@att.net>
Subject: The BBS network and tcp/ip.
Charles Brabham <n5pvl@texoma.net> wrote in message
news:7u1mav$1dg4@enews2.newsguy.com...
>
> Hank Oredson <horedson@att.net> wrote in message
> news:7tqrt1$agn$1@bgtnsc02.worldnet.att.net...
> >
> > >
> > > Then what do you want?
> >
> > Ideas.
>
> I hate to encourage the "applications mantra", but I do have an idea for
> one...
>
> I was thinking a "tune-up" or 'performance meter" application might be
> handy. Have it offer a number of functions for direct connectees and even
> for those who access it from a distance and want info about their link.
>
> There is already a "deviation meter" function available for X1J nodes..
I'd
> start off with something like that. FlexNet has a TXD sniffer of some
sort.
> Toss that in too. I used to run a BBS program that would tell you the
> "effective baud rate" of the link you are currently running. The number
> fluctuated according to conditions... I remember a 300 baud HF packet qso
> averaging 56 baud throughput... A round-trip-time indicator would be
great,
> and so on...
>
> Serious tests would be handy, as well as "rule of thumb" and even "fun"
> tests! Many of these are things that CAN already be done, but seldom are.
> Putting them all within a specialized application so Hams could play
around
> with them would encourage their use. - This would be just the thing for
new
> Hams to learn from, and experienced hams to tinker around with, and for
> bored Hams to play with.
>
> Such a program could serve as a benchmark or standard measuring system for
> comparing the performance of different packet networks, protocols,
software,
> and what have you, or even for comparing the performance the same system
> under different conditions... That could be a lot of fun, and maybe even
> educational.
>
> Have the servers interact with others in the same network, using that info
> to give users "the big picture" about the net's strong and weak points.
> Sometimes getting things fixed is just a matter of making people generally
> aware of problem areas. Making such info available can generate support
from
> unexpected quarters.
>
> This is all info that most packet ops are generally unaware of, or are
> uncertain about how to get. This is a shame, as the Packet community would
> greatly benefit if the general level of awareness concerning these matters
> could be raised. Putting all of these into a tcpip server would be very
> effective, if it's practical and possible to do so. - Would some of this
> stuff need to be in the "driver" instead of in an application, for
example?
>
> Anyway, there's an idea at any rate... I never guaranteed a good one!
Interesting ideas.
I have some of this in SNOS (rtt per circuit e.g.) and am in the process
of adding more such statistics. Investigating different re-route mechanisms.
The tradititional tcp measures do not work well over radio networks.
NetWalker was designed for exactly this purpose: measuring network
parameters across the "whole" network.
--
... Hank
http://horedson.home.att.net
>.
------------------------------
Date: Wed, 13 Oct 1999 08:45:39 -0700
From: "Cathryn Mataga" <cathryn@junglevision.com>
Subject: The BBS network and tcp/ip.
Hank Oredson wrote in message <7u274r$6ct$1@bgtnsc03.worldnet.att.net>...
>
>D. Stussy <kd6lvw@bde-arc.ampr.org> wrote in message
>news:Pine.LNX.4.10.9910130807320.551-100000@dns.bde-arc.ampr.org...
>> On Tue, 12 Oct 1999, Hank Oredson wrote:
>> Rob Janssen <nomail@pe1chl.demon.nl> wrote in message
>> > news:slrn805t5t.835.nomail@linux.pe1chl.ampr.org...
>> > > Hank Oredson <horedson@att.net> wrote:
>> > >
>> > > >> Then what do you want?
>> > >
>> > > >Ideas.
>> > >
>> > > Ok here is an idea:
>> > >
>> > > What you want already exists. Under Linux. So, the problem is not
>how to
>> > > write the software itself.
>> >
>> > I have Linux.
>> > Did not find any such software.
>> > Most hams do not (and will not) have Linux.
>> > So Linux is not of interest to me.
>>
>> Didn't find: Well, you need the package called "ax25-utils".
>> The file [/usr/src/]linux/Documentation/networking/ax25.txt tells you
>> where to get this, and the "how-to" file.
>
>I have ax25-utils.
Hmm, have you visitited http://radio.linux.org.au ? That site seems to
be the place where the latest stuff shows up. If you're on 2.0.xx kernels
ax25-utils is okay, but if you have a recent Redhat, you may want the libax25,
ax25-tools, ax25-apps, etc. ax25-utils, I believe works okay from the
binaries
though -- just the source doesn't work on 2.2 kernels..
>Where is NET/ROM?
Netrom is there. Create the nrports and nrbroadcast like it says in
ax25-howto. Do a man nrattach and run netromd, like it says in
ax25-howto. Check for /proc/nr_* for nr_neigh and nr_nodes or
something like that. They should start filing up with node names.
try 'call netrom k0localstation' and see if your TNC lights up.
>Where is a HAL P38 / PCI400 driver?
At this time, there's no support for HALP38 or much of any HF hardware.
To be continued in digest: hd_99_260D
Read previous mail | Read next mail
| |
