| |
PA2AGA > TCPDIG 31.08.96 03:46l 179 Lines 6719 Bytes #-10902 (0) @ EU
BID : TCP_96_175A
Read: GUEST
Subj: TCP-Group Digest 96/175A
Path: DB0AAB<DB0PV<DB0MAK<DB0SON<DB0SIF<DB0NHM<DB0SHG<DB0HSK<DB0SGL<DB0HAG<
DB0END<DB0ACC<PI8DRS<PI8DAZ<PI8GCB<PI8WFL<PI8VNW
Sent: 960830/2232Z @:PI8VNW.#ZH2.NLD.EU #:58550 [Hoek v Holland] FBB5.15c
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : TCPDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA16535 ; Fri, 30 Aug 96 21:48:04 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.61/7.1) with SMTP
id AA00003719 ; Fri, 30 Aug 96 22:49:05 MET
Received: from pa2aga-1 by pa2aga with SMTP
id AA00003687 ; Fri, 30 Aug 96 22:44:21 MET
Received: from pa2aga-1 by pa2aga-1 (NET/Mac 2.3.61/7.5.4) with SMTP
id AA00008003 ; Fri, 30 Aug 96 22:44:19 MET
Date: Fri, 30 Aug 96 22:38:36 MET
Message-Id: <tcp_96_175A>
From: pa2aga
To: tcp_broadcast@pa2aga-1
Subject: TCP-Group Digest 96/175A
X-BBS-Msg-Type: B
TCP-Group Digest Thu, 29 Aug 96 Volume 96 : Issue 175
Today's Topics:
(2) Looking for an RFC
(fwd) Re: AX.25 - that darn PID (fwd)
advanced networking
AX.25 - that darn PID (5 msgs)
AX.25 - that darn PID (Fwd)
PPP/SLIP in connected AX25? (8 msgs)
Standalone router PTP - Wireless lan cards FHSS
Send Replies or notes for publication to: <TCP-Group@UCSD.Edu>.
Subscription requests to <TCP-Group-REQUEST@UCSD.Edu>.
Problems you can't solve otherwise to brian@ucsd.edu.
Archives of past issues of the TCP-Group Digest are available
(by FTP only) from ftp.UCSD.Edu in directory "mailarchives".
We trust that readers are intelligent enough to realize that all text
herein consists of personal comments and does not represent the official
policies or positions of any party. Your mileage may vary. So there.
----------------------------------------------------------------------
Date: Wed, 28 Aug 96 06:22:16 EDT
From: "Tom Moulton" <tmoulton@ram.net>
Subject: (2) Looking for an RFC
>No, that's an internal feature of AX.25. I think it's in the AX.25 spec.
>As I recall, it came from Eric Scace.
>
>Phil
Ok... It isn't in the AX25 spec... but that's another story...
***********************
Thomas A. Moulton, W2VY
w2vy@ram.net
------------------------------
Date: Thu, 29 Aug 1996 00:00:54 -0500 (CDT)
From: Robert E Brose II <bob@kunk.n0qbj.ampr.org>
Subject: (fwd) Re: AX.25 - that darn PID (fwd)
> From: alan@cymru.net (Alan Cox)
> > Any thoughts? Anyone else interested in STREAMS? They're cool, you
> > know.
>
> Mutter..performance..mutter..latency..mutter... No Im not convinced,
Not to offend the hoards of Linux and BSD users, but:
Weak argument IMHO. If we were that concerned about performance, we'd all be
running nos.asm in native mode on pentiums or ppc 604's
>From what I've seen, the difference in performance is small, 20% MAYBE (based
on informal testing of SVR4.2 vs FreeBSD on similar speed class machines).
Wait a month and get a 20% faster machine for the same price :)
I can run right up to the theoretical Max on a 10Mb ethernet board with
ftp's on a 586 120mhz box with a $50 ne2000 pci clone using standard SVR4
streams without any Sun enhancements. (can't tell if it'll go faster, don't
have a 100mb network yet :-)
Even the Free-BSD fanatics I work with recognize the value of Streams.
For those that don't know how it works (and I am not an expert, just learing
myself), you can simply dynamically push a module, say an ax25 module, on
an ASY driver, SCC driver, whatever and connect it into the TCP (or whatever
upper level protocol). In a system that dynamically loads drivers, UW 4.2mp,
SCO UW, Solaris, you don't even need to rebuild the kernel.
73, Bob
--
Robert E. Brose II / N0QBJ / Amateur Radio IP Address Coordinator for
Minnesota
Amprnet: bob@n0qbj-uhf.ampr.org (44.94.9.9)
WWW (Amprnet only): http://kunk.n0qbj.ampr.org/
Packet: N0QBJ@WB0GDB.#STP.MN.USA.NOAM
------------------------------
Date: Wed, 28 Aug 1996 00:46:10 -0700
From: "Ron Curry" <recurry@insighttec.com>
Subject: advanced networking
Seems like there is little reason to build a ROM version of Linux. A
386/486/Pentium mother board (one of the P54C with power management) with a
PCMCIA flash card will work just fine. The flash cards are available for
less than $200 for 15 mb and about $50 for 5mb. That is more than enough to
build a basic system for a router. No moving parts and it looks to the bios
and software just like an ATA device.
Ron
----------
> From: Terry Dawson <terry@perf.no.itg.telstra.com.au>
> To: Graham Broadbridge <grahamb@peachy.apana.org.au>
> Cc: mikebw@bilow.bilow.uu.ids.net; tcp-group@ucsd.edu
> Subject: Re: advanced networking
> Date: Monday, August 26, 1996 3:26 PM
>
> > > I've successfully built a single 1.44Mb floppy disk that was bootable
> > > that contained enough to boot linux and act as a router with
ethernet,
> > > ax25, netrom and ppp support, and supported firewalling, masquerade
> > > etc as well. It requires 4Mb of ram in the machine, but the rest is
> > > easy.
> >
> > Surely the normal reason for a reboot in a remote environment is power
> > failure. Given that, a power failure would normally be a result of
some
> > unusual weather conditions.
> >
> > In that instance, the dramatic temperature changes would not suggest
> > that a bootable floppy would fare well in the long term.
>
> Graham,
> my point was not that this would be a suitable arrangement for a
> mountain
> top router/repeater, but that it takes quite minimal resource to get a
> working linux configuration running. I see little reason why one of
> those
> 'rom' drives couldn't be burnt to contain a like configuration and this
> would prove much more reliable than a floppy disk based unit.
>
> The Linux ELKS project holds some promise, and might produce a rommable
> version of linux for low end intel hardware which would surely verge on
> the most flexible configuration around.
>
> Terry
------------------------------
Date: Wed, 28 Aug 1996 09:42:11 +0100 (BST)
From: Alan Cox <alan@cymru.net>
Subject: AX.25 - that darn PID
> Ether type in the PID octet. The problem with this is that the PID
> octet is only present in I frames; when a connection is established, there's
> no way to know what SAP the connection is going to end up using.
Yes. We have this problem with the Linux AX.25, at the moment an incoming
netrom connect will cause an AX.25 connect which will wait in the user
process not receiving the netrom frames then time out. Its a pig because
you can't send the user an initial greeting if you don't know what
protocol they are.
> The reason I care about all this is I'd like to complete the project
> I envisioned - a STREAMS implementation of the AX.25 protocols (LAPB,
> net/rom, etc.) using standard interfaces (DLPI).
Don't use a standard LAPB streams module for the AX.25 layer - the
To be continued in digest: tcp_96_175B
Read previous mail | Read next mail
| |
