| |
PA2AGA > TCPDIG 24.08.96 21:36l 174 Lines 6651 Bytes #-10909 (0) @ EU
BID : TCP_96_168B
Read: GUEST
Subj: TCP-Group Digest 96/168B
Path: DB0AAB<DB0PV<DB0MAK<DB0SON<DB0FP<DB0GV<DB0SIF<DB0NHM<DB0SHG<DB0OBK<
DB0ACC<PI8DRS<PI8DAZ<PI8APD<PI8GCB<PI8MBQ<PI8VNW
Sent: 960824/1529Z @:PI8VNW.#ZH2.NLD.EU #:54800 [Hoek v Holland] FBB5.15c
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : TCPDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA16034 ; Sat, 24 Aug 96 14:12:59 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.61/7.1) with SMTP
id AA00003294 ; Fri, 23 Aug 96 20:24:44 MET
Received: from pa2aga-1 by pa2aga with SMTP
id AA00003252 ; Fri, 23 Aug 96 20:14:35 MET
Received: from pa2aga-1 by pa2aga-1 (NET/Mac 2.3.61/7.5.4) with SMTP
id AA00007891 ; Fri, 23 Aug 96 20:14:33 MET
Date: Fri, 23 Aug 96 20:04:07 MET
Message-Id: <tcp_96_168B>
From: pa2aga
To: tcp_broadcast@pa2aga-1
Subject: TCP-Group Digest 96/168B
X-BBS-Msg-Type: B
Diliman, Quezon City, PHILIPPINES 1101
voice: 632 9205301 to 99 loc.5106
fax: 632 9224714
Internet: jojo@asti.dost.gov.ph
ochave@itu.ch
v.ochave@ieee.org
X.400: G=victorio; S=ochave; P=itu; A=arcom; C=ch
---------------------------------------------------------------
------------------------------
Date: Wed, 21 Aug 1996 10:03:35 +0100 (BST)
From: Alan Cox <alan@cymru.net>
Subject: PPP/SLIP in connected AX25?
> The over-the-air interface would then be PPP or SLIP in connected-mode
> AX25 with PID F0. To distinguish this mode from conventional "dumb
> terminal" (e.g., BBS) mode, the NOS router could either set aside a
> separate AX25 SSID. Or it could get clever and look for the
> distinguishing characteristics of a SLIP or PPP frame in the incoming
> data, e.g., the leading C0 or 7E flag character. I understand that
> some dialup IP routers/terminal servers already do this.
It produces abominable results unless the TNC is very very smart and
sends packets broken on the SLIP/PPP framing boundary only. If you do
it connected mode you get horrible congestion problems as well. Routing
the stuff when users keep reconnecting to the nearest site that looks
the fastest becomes horrible as well.
If you can get a windoze box talking SLIP to a serial port then the code
in the TNC to do SLIP->AX.25 UI is not exactly difficult and that would
seem a better path.
Alan
------------------------------
Date: Wed, 21 Aug 1996 06:12:11 -0500 (CDT)
From: ssampson@othello.UCSD.EDU (Steve Sampson)
Subject: PPP/SLIP in connected AX25?
> What about plugging a standard Winsock stack that supports PPP or SLIP
> (like the one that built into Windows 95) into a conventional (not
> KISS) AX25 TNC and connecting it to a suitably configured NOS gateway?
>
Win95 did not carry-over the null modem from 3.11. The Dialup Networking
means Dialup. That was quite a disappointment. I then checked the
serial connect of two machines application, and it requires one to be
the server, the other client (like most parrallel/serial port stuff).
One of the things that bugged me about NOS was the need to implement the
AX.25 into it. The TNC had a perfectly good AX.25 implementation. I
decided to just program an interface to use the TNC. I noticed I could
catch all the packets and get the IP packets very well. I mentioned this
to K5JB (Joe) at lunch one day, and he kind of laughed (as he usually
does when you haven't thought a thing through). He asked, "Hmm, I don't
think a TNC will send anything but an dumb terminal PID." Well crap, I
was having so much fun with the receive side, I forgot about the
transmit side. That has always been a need in the TNC, to allow the
PID to be changed. I suppose you could fanagle it in host mode, but I
kinda lost interest.
The reason I bring this up, is I had a perfectly good set of radios and
tnc's that I thought I could put in the transparent mode and hook up
between my station and an across town Ham. We both were running W95,
and that's when I found the crippled dialup stuff. By the way, the
dialup networking doesn't work very well with any of the ISP's I've had.
It takes a long time to negotiate the login. Linux and Trumpet seem
to operate on the first try.
Steve
------------------------------
Date: Wed, 21 Aug 96 18:24:00 -0000
From: mikebw@bilow.bilow.uu.ids.net (Mike Bilow)
Subject: PPP/SLIP in connected AX25?
Steve Sampson wrote in a message to Mike Bilow:
SS> Win95 did not carry-over the null modem from 3.11. The
SS> Dialup Networking means Dialup. That was quite a
SS> disappointment. I then checked the serial connect of two
SS> machines application, and it requires one to be the server,
SS> the other client (like most parrallel/serial port stuff).
The null modem stuff is supposed to be available from FTP.MICROSOFT.COM.
-- Mike
------------------------------
Date: Wed, 21 Aug 96 14:45:00 -0000
From: mikebw@bilow.bilow.uu.ids.net (Mike Bilow)
Subject: PPP/SLIP in connected AX25?
Phil Karn wrote in a message to Mike Bilow:
PK> The over-the-air interface would then be PPP or SLIP in
PK> connected-mode AX25 with PID F0. To distinguish this mode from
PK> conventional "dumb terminal" (e.g., BBS) mode, the NOS router
PK> could either set aside a separate AX25 SSID. Or it could get
PK> clever and look for the distinguishing characteristics of a
PK> SLIP or PPP frame in the incoming data, e.g., the leading C0 or
PK> 7E flag character. I understand that some dialup IP
PK> routers/terminal servers already do this.
SLIrP works something like this, running on a Unix machine under a shell
account and passing SLIP across the terminal link. I believe it is fairly
widely available with source code. From the point of view of the Unix machine
which gets turned into a SLIrP server, SLIrP is just an application program
which talks to the socket interface.
-- Mike
------------------------------
Date: Wed, 21 Aug 1996 12:33:42 -0700 (PDT)
From: Phil Karn <karn@qualcomm.com>
Subject: PPP/SLIP in connected AX25?
>SLIrP works something like this, running on a Unix machine under a shell
>account and passing SLIP across the terminal link. I believe it is fairly
>widely available with source code. From the point of view of the Unix
machine
>which gets turned into a SLIrP server, SLIrP is just an application program
>which talks to the socket interface.
This is certainly one way to implement the hub that the users connect
to, but it would be nice to multiplex everyone through a single piece
of AX.25 hardware and/or software if at all possible. That's why NOS
would make a good platform for this sort of thing.
Phil
------------------------------
End of TCP-Group Digest V96 #168
******************************
You can send your message for this bulletin
to: tcp-group@pa2aga on .AMPR.ORG-net
or: tcpaga@pi8vnw.#zh2.nld.eu on BBS-net
------
NOT TO: pa2aga@pa2aga or pa2aga@pi8vnw.#zh2.nld.eu PLEASE!!
It will get posted automatically within a few days
Read previous mail | Read next mail
| |
