| |
PA2AGA > HDDIG 20.09.00 23:26l 220 Lines 7710 Bytes #999 (0) @ EU
BID : HD_2000_256F
Read: DC1TMA GUEST
Subj: HamDigitalDigest 2000/256F
Path: DB0AAB<DB0FSG<DB0SL<DB0RGB<DB0MRW<DB0ERF<DB0BRI<DB0HAG<DB0ACH<PI8JOP<
PI8ZAA<PI8HGL
Sent: 000920/1851Z @:PI8HGL.#ZH1.NLD.EU #:16247 [Den Haag] FBB $:HD_2000_256F
From: PA2AGA@PI8HGL.#ZH1.NLD.EU
To : HDDIG@EU
Date: Tue, 19 Sep 00 20:17:33 MET
Message-Id: <hd_2000_256F>
From: pa2aga@pe1mvx.ampr.org
To: hd_broadcast@pa2aga.ampr.org
X-BBS-Msg-Type: B
existing packet nertwork or I wouldn't be using it.
> >
> > >
> > > > I've had a quick look at AGW, but only being able to use
> > > > the tcpip side of it for 45 minute (without registering it) has put
me
> > > > off doing tests with it. Maybe one day.
> > >
> > > I never had any luck with it. Should try it again sometime.
I might have a look on my next lot of days off if it's not good fishing
weather.
I've got it installed on this computer with one TNC cofigured. I just
haven't
looked at the tcpip side of it.
--
Shane Deering VK3BVP
Packet VK3BVP@VK3BVP.#SEV.VIC.AUS.OC
http://www.qsl.net/vk3bvp/index.htm
------------------------------
Date: Mon, 18 Sep 2000 23:54:02 GMT
From: "Hank Oredson" <horedson@att.net>
Subject: TCP/IP Address
"Shane Deering" <vk3bvp@crosswinds.net> wrote in message
news:8q649v$ebh$1@perki.connect.com.au...
>
> "Hank Oredson" <horedson@att.net> wrote in message
> news:p8qx5.20247$6f1.986318@bgtnsc05-news.ops.worldnet.att.net...
> > > > . What I really want is JNOS with an interface to the
> > > > > windows tcpip stack. Then it would be sort of like Wingate and
> Mailtraq
> > > > > rolled into one, but with all the packet interface options.
> > > >
> > > > I'm not sure what you are suggesting. Could you explain in a bit more
> > > > detail what that interface would be / do?
>
> I'm suggesting that SNOS should be able to talk directly to the Windows
> TCPIP stack rather than having to go out one NIC and back in via another
> one.
> Just like all the internet software I know of does.
The cost of writing software to do this is quite large, since essentially
none of the bits exist. Perhaps someone will take on this project.
SNOS, as I said, is an experiment in what such software might do.
> > > > As far as I'm aware, SNOS
> > > > and etherax25 have nothing at all in common, they do different things.
>
> That's right, more or less.
Well ... exactly, actually :-)
> > > > You could, perhaps, use etherax25 to connect your Winsock over
> > > > ham radio to another machine running SNOS ... and use a serial port
> > > > and TNC instead of that second ethernet controller :-)
>
> Yes. For a user (client) all that's needed is ethrax25 and a serial port
> and
> they are surfing the packet radio net in a matter of minutes and a few
> reboots.
> It doesn't have to be SNOS, it could be *NOS for private mail and bulletins
> that have been through rewrite and alias (so that bulls end up like mailing
> list mail is on the internet) or even to a server like I'm running here.
SNOS is not a client.
It is middleware.
It has a client side and a server side, but it is not itself a client.
You could, of course, use it just for it's servers: smtp, nntp, ftp, http,
pop3.
It also has a client side, so it can talk to servers.
You might also call it "agentware" ;-)
You don't look at "the SNOS window", or type at it.
It links those things you are talking about together, so they work with
the existing ham radio network (BBS and tcp/ip). It could link most
anything: for example I use the pop3 client and server as a mail collector
and router. It can snarf up mail from my various pop3 accounts and from
the ham radio BBS network, I can then access it all from one place. It
knows how to route the outgoing smtp mail to the correct smtp server,
and the outgoing BBS mail to the correct BBS system.
Middleware. Both client and server.
> > > I have to go out in a minute so it won't be detailed.
> > > I thought that SNOS used BPQEITHER to talk to the packet network via
> > > another computer that has normal packet interfaces. Why not add a normal
> > > packet
> > > interface to SNOS.
> >
> > I think you should look at the web pages before you "think" too many
> > wrong things. SNOS has ax.25, NET/ROM, tcp/ip, can talk to TNCs
> > on serial ports, supports HAL P38 and PCI4000 controllers
>
> I have actually downloaded SNOS a couple of times. It seems to offer more
> now than when I last looked at it.
> I'm sure in the past it wouldn't run without bpqether and there seems to be
> more features now. If I had a couple of spare card slots and NICs I would
> be temped to give it another look. If it talked directly to the Windows
> tcpip
> stack and to BPQ via a loopback port I'd be running it now.
That would be a very different program.
> But for now I get more features with less hardware with what I'm running.
Which features?
> > > Of course they have nothing in common. The idea of using ethrax25 is as
> > > interface
> > > option like bpqeither. To be used as well as or instead of it with SNOS.
> > > If you have eithrax25 you don't need to connect to another SNOS
> computer,you
> > > can connect to any *NOS computer over packet.
> > > I just thought it would be a good interface to have as well as
> bpqeither.
> >
> > SNOS does all that.
> >
> > > >
> > > > > >
> > > > > > Are there any other solutions available?
> > > > >
> > > > > Guess you knew I was going to say ethrax25.
> > > > > To my way of thinking it offers the easiest way of getting windows
> > > > > end user client tcpip software onto the packet tcpip network.
> > > >
> > > > Not what SNOS is about ...
>
> OK, then how do end users get their mail and bulls from your SNOS server.
SNOS is not a BBS.
> Or does everyone have to use SNOS to be able to use, say, outlook express
> to get their mail.
SNOS is not a BBS.
> I tend to split packet (or internet for that matter) into two types- server
> and
> client. SNOS would be a good server if you had their hardware to run it.
> But I don't see it as a client solution.
SNOS is not a client. Sorry, I thought that was obvious. It's middleware.
Use any clients you like, for the appropriate protocols.
> > > > > All you have to do is install the driver, hook up your KISS mode TNC
> > > > > and config your software (that you're already using on the
> internet).
> > > >
> > > > As far as I was aware, etherax25 allows you to stuff tcp/ip
> > > > out over a TNC. No services, nntp <-> bulletin translation, etc.
> > >
> > > Good isn't it. Why tie yourself down to one bit of packet software.
> > > I use Mailtraq which does that and a lot more.
> > >
> > > > So it doesn't solve the most important issue: maintaining
> compatibility
> > > > with the existing packet network applications. SNOS my experiment
> > > > to do this: provide the bridge between the existing BBS network
> > > > protocols (e.g. forwarding) and the tcp/ip protocols (e.g. nntp
> > > > distribution).
> > > JNOS<>Mailtraq does that too, but you aren't tied to using them.
>
> And mailing lists and you can get your mail with a browser if you were
> silly enough. The remote logging is handy. It's all compatable with the
> existing packet nertwork or I wouldn't be using it.
> > >
> > > >
> > > > > I've had a quick look at AGW, but only being able to use
> > > > > the tcpip side of it for 45 minute (without registering it) has put
> me
> > > > > off doing tests with it. Maybe one day.
> > > >
> > > > I never had any luck with it. Should try it again sometime.
>
> I might have a look on my next lot of days off if it's not good fishing
> weather.
> I've got it installed on this computer with one TNC cofigured. I just
> haven't
> looked at the tcpip side of it.
--
... Hank
http://horedson.home.att.net
------------------------------
Date: Tue, 19 Sep 2000 07:02:27 GMT
From: nomail@rob.knoware.nl (Rob Janssen)
Subject: TCP/IP Address
Hank Oredson <horedson@att.net> wrote:
To be continued in digest: hd_2000_256G
Read previous mail | Read next mail
| |
