| |
PA2AGA > HDDIG 26.03.00 09:13l 176 Lines 6800 Bytes #-9534 (0) @ EU
BID : HD_2000_85D
Read: GUEST
Subj: HamDigitalDigest 2000/85D
Path: DB0AAB<DB0SL<DB0RGB<DB0MRW<DB0ERF<DB0FBB<DB0GOS<DB0PKE<DB0SM<PI8DAZ<
PI8GCB<PI8HGL<PE1NMB<EA7URC<PE0MAR<PI8VNW
Sent: 000326/0331Z @:PI8VNW.#ZH2.NLD.EU #:59517 [HvHolland] FBB7.00g24
From: PA2AGA@PI8VNW.#ZH2.NLD.EU
To : HDDIG@EU
Received: from pa2aga by pi1hvh with SMTP
id AA31914 ; Sun, 26 Mar 00 03:07:55 UTC
Received: from pa2aga by pa2aga (NET/Mac 2.3.70/7.5.3) with SMTP
id AA00018531 ; Sat, 25 Mar 2000 14:33:35 MET
Date: Sat, 25 Mar 00 14:24:32 MET
Message-Id: <hd_2000_85D>
From: pa2aga
To: hd_broadcast@pa2aga
Subject: HamDigitalDigest 2000/85D
X-BBS-Msg-Type: B
> >> configurability... unfortunately the structure of the NET/NOS config
> >> does not lend itself well to removing, because the items in the config
> >> file often perform some "action" during startup. That is more difficult
> >> to hardwire than just fixing a set of values.
>
> >I split the configuration into two parts: defaults and user specified.
> >Many parameters cannot be changed by the user.
>
> What I meant to say is that there cannot be a default value for something
> like "start smtp". It is not a value, it performs the action of starting
> a server.
>
> When you want to hardwire such things you will either need a table of
> config commands built into the executable and run as an autoexec.net, or
> the code will have to be restructured quite a bit.
"the code" in this case is SNOS, it is structured a bit differently than
the common *NOS flavors.
> >> I was not aware that G8BPQ code had such an extension.
> >> There are other extensions, by G8BPQ and others, but I cannot oversee
> >> quickly if you could add such an extension and have compatible behaviour.
>
> >A quick test, against BPQ, K-net and NET/ROM worked ok: the extra
> >octet was ignored and caused no problem.
>
> I mean: how do you connect to another node and detect if it can handle
> your new protocol, will just ignore your extension (and in this case:
> malfunction because the PID will be dropped) or will refuse your connects?
If the other node can handle the extension, it will report this fact in the
connect acknowledge, as BPQ does. If it cannot, the existing protocol
(AX.25 at layer 2, NET/ROM at layer 3) would be used. Much larger
issue of capability negotiation might be an interesting future discussion.
BPQ has the extra byte in the connect acknowedge. If you get an ack
with the extra byte, you know your connect target is BPQ. I'll ignore the
fact that not all implementations of the BPQ extensions to NET/ROM
work the same: that is a different discussion about standards setting
processes (or lack of same ...) within ham radio.
The test bed for some of these ideas was DIGI. Tossed that code after
doing the experiments. It could route AX.25 connections automatically.
i.e. if an AX.25 connect was attempted to a station known to any DIGI
node in the network, the connect would be answered by whatever DIGI
node heard it and the frames routed transparently to the target of the
connect request, whereever it was in the network. The experiment was
mainly about inter-node exchange of routing information ... the technique
would work equally well for any address type (IP, NET/ROM, AX.25).
Think of a distributed database and how synchronization should occur
between multiple instances of that same database. Model is WP.
Small incremental updates sent fairly frequently. Less update overhead
than NET/ROM because of greater intelligence in each node, thus
less information needs to be exchanged, and is only exchanged when
some bit of routing information changes. Yes, this did require a "triggered
database load" when a naive node first came on air.
> This extension will be like the extended sequencing, in that it will most
> likely need a separate table with callsigns that can handle this new
protocol.
SNOS marks which nodes are "BPQ capable" when it discovers them.
My first guess is that a similar approach could be used for other extensions.
Experimentation will be needed to verify this. Will be a while before I
get to this part of the project.
> Well, routing IP over NET/ROM already requires far too much user
> configuration, so this extra bit can probably be added.
Yes indeed! Thus SNOS, which requires much less user configuration.
One of the goals is minimal user configuration required. Nowhere near
done with that part of the code. Experience to date is that a user (node
owner with 8 radios) unfamiliar with tcp/ip was able to bring up SNOS
to replace BPQ in less than one hour.
> It would, however, be more constructive to work towards an auto-configuring
> autorouting IP protocol that has functionality like Flexnet but uses IP
> addresses instead of AX.25 callsigns.
Not quite sure what you mean: create a new protocol to replace AX.25
or create extensions to NET/ROM to handle things it cannot presently
handle such as RIP and other broadcast IP or just start from scratch?
> As IP supports the notion of subnets, it would be better scalable than
> Flexnet, and it would also better suit todays network applications.
> Building this on top of NET/ROM is just as bad as trying to route IP over a
> Flexnet network...
Two issues here. First, NET/ROM support is needed because NET/ROM
networks exist. Second would be new layer 2 and/or layer 3 protocols that
are not compatible with AX.25 and/or NET/ROM. For me, not an option
yet because there is nobody to test with. Perhaps sometime in the future.
> Rob
Again: thank you for your continued comments on these issues.
They have been very helpful!
--
... Hank
http://horedson.home.att.net
>.
------------------------------
Date: Fri, 24 Mar 2000 23:31:05 -0500
From: "Brian Pawloski" <kc8fuw@usxchange.net>
Subject: Rtty and PSK 31 interface Help needed
Hello,
I am a rookie who needs help. I have a IBM thinkpad 600 pentium 2 laptop and
a IC-706 and I would like to try RTTY and PSK 31. My question is do I have
to have the CT-17 level converter? or can I buy a MFJ prewired transciever
to computer cable? I'm not really sure what I need. Also what software would
be the best, I have rtty and psk on my logging program (Logger) and I'm not
sure if it would be adequate. any help would be greatly appreciated. e-mail
me direct or post to group.
Thanks,
Brian KC8FUW
>.
------------------------------
Date: Sat, 18 Mar 2000 15:10:58 GMT
From: Tony Schonfeld <tony@f5git.ampr.org>
Subject: Web address for T7F and interlink.
hello Everybody ,
i need to have the dutch web address for T7F and Interlink products
Please let me know if you know that ,
many thanks per advance
Tony
--
------------
Email: tony@f5git.ampr.org WWW: http://www.f5git.ampr.org
Voice/Data/Fax: (0)33 0476932598 Phone(GSM): 06 17 85 69 07
>.
------------------------------
End of Ham-Digital Digest V2000 #85
******************************
You can send in your contribution to this digest by
sending an e-mail to: hd-group@pa2aga.ampr.org
or (via BBS-net) to: hdaga@pi8vnw.#zh2.nld.eu
Read previous mail | Read next mail
| |
