| |
SM3LKS > BPQ 19.08.99 04:54l 145 Lines 5687 Bytes #-9919 (0) @ EU
BID : 43499_SM3LKS
Read: GUEST
Subj: Re: SM7UZI - please give it a rest
Path: DB0AAB<DB0ZKA<DB0KFB<DB0CZ<DB0GE<DB0ZDF<DB0SRS<DB0ABH<DB0BOX<DB0MAK<
DB0ERF<DB0ABZ<DB0OCA<DB0SAW<DB0MAR<DB0IL<OZ5BBS<OZ4PAC<OZ4BBS<OZ4BOX<
OZ7PAC<OZ3PAC<OZ6BBS<SK7CY<SK6FV<SK6YW<SK6BA<SK6LK<SM7FEJ<SK7HR<SK7GC<
SK5AS<SK5BN<SK5UM<SK5AE<SK5BB<SK4HC<SK4EA<SK4BW<SM3ESS<SK3BG<SK3UB<
SK3JR<SM3LKS
Sent: 990818/1315Z @:SM3LKS.Z.SWE.EU #:43499 [Ostersund] LinFBB7.00g $:43499_SM
From: SM3LKS@SM3LKS.Z.SWE.EU
To : BPQ@EU
SM7UZI@SK7IQ.MALMOE.M.SWE.EU wrote:
...snip...
>The net/rom network in Sweden is only crap!
If you think so, write an article in QTC about it, because if it is true
it is time to wake up some of the sysops that are responsible of the
network. Then you might have a better chance to improve it.
Make sure you make it clear what is crap, and why you think so.
Make sure to say that is is the complete network in Sweden that is crap,
not just the part in your area.
Say what improvements you want. Detailed if possible.
You will surely get a debate.
If we agree whith you, we will surely get to an agreement what to
do to fix the network.
I will be waiting for your article.
...snip...
>>I think the larger part of NET/ROM-nodes is TNC-2 (or compatible) with
>>NET/ROM-firmware. I don't think a computer, that may crash, has replaced
>>over 50% of the nodes yet, making BPQ the most used NET/ROM-node.
>Bpq is very much used on bbs systems as combined packet driver and node.
Yes, it is used as a frontend to BBS'es.
But there are still a lot more standalone nodes out there.
>>TNC-2-nodes are still in majority.
>Yes maybe, but also they should be replaced!
I wish you good luck in your mission.
...snip...
>>NET/ROM-nodes were originally, and still are, intended as unattended
>>24h/day-link-stations, often in remote areas, connecting several local networks
>>They were not intended as a frontend to your personal packet-computer that
>>only are up for a few hours a day.
>Bpq is used like that!
>And that is aproblem that makes the routing work bad, nodes popup and
>disapears.
If you read my statement again, you see that if you use it as it was
intended, you don't have nodes that keeps popping up and down.
If you have such nodes, it is because of a poor radio-link.
It is the use of "your own node", as a frontend to your packetstation
that most of the time causes the trouble, as they are not 24h/day-stations.
Used as a frontend to a BBS causes no problem, as long as it is up 24h/day.
If you have problems with stations that pops up and down, don't blame BPQ
ore any other software for that.
Make the user that causes the problem to change their behaviour, or change
the software in use.
Don't start a crusade against the software, in this case BPQ.
It is the WRONG use of the software that should be stopped, not the
software itself.
>>If you use NET/ROM-nodes as they were intended to be used, you have no
>>problems with routing-tables etc...
>That is not very realistic, since net/rom node ise used by many users.
>And I would still have since the routing information is updated to seldom for
>the routingto work good, the traffic load etc change more often than one each
>half hour or what ever time it is between the routing information beacon is
>sent out.
That is very easy to solve. You are not stuck with 30 minute intervals in
the routing broadcast. You can have them every minute if you like.
The reason why 30 minutes is widely used is because the nodes is used in
stable links, no popping up or down.
For the majority of the nodes it is no need for shorter intervals.
The problem is still the "personal nodes".
>>If you are looking for a personal-"node" that you can use only a few hours
>>a day, and not corrupting the routing-tables, you could use FlexNet, or
>>TCP/IP that is a far better choice.
>Why should I use anode like that?
>To make the life harder for my fellow hams?
TCP/IP-software is very easy to get, and use.
So we are not making it any harder then if we force them to use flexnet.
The only thing they must do is to contact their local IP-coordinator to
get their own IP-number and .ampr.org-address.
But, lets do it your way.
"NET/ROM-network is crap, it should be replaced."
TCP/IP-networking, in my opinion, is for the moment the best alternative.
(It has adaptive parameters built in, etc..)
We surly should go directly to the best alternative, or we might be forced
to replace the system anyway i a few years.
>With flexnet can't that even be done!
Then flexnet is crap, if it can't support TCP/IP. ;-)
Throw away flexnet, and use another software.
(Note that this is not my real opinion. Only to show how I easy can
reverse the discussion)
...snip...
>>OK, please explain to us all what you mean with "packetdriver", in words
>>that everyone understands.
>The software with an interface to the modem driver, and a interface to your
>terminal, bbs, node etc which handels the ax25 communication.
You mean like this ?: (For BPQ as an example)
Application <-> packetdriver <-> protocoldriver <-> modemdriver <-> modem
(BBS) (Part of BPQ) (Part of BPQ) (Part of BPQ)
(configurable) (fixed) (any from a list)
The packetdriver gets the information from the application.
The packetdriver sends it to the protocoldriver, etc...
A re-sending, acks, responsetime etc.. of any packet is handeled by the
packetdriver.
The protocoldrivers job is to code/decode to/from ax25/netrom.
The modemdriver interfaces the protocoldriver to the modem in use.
(KISS-modem, NET/ROM-node, network-card, scc-card, etc...)
...snip...
>>And just because it it easy to setup does not make it the most suitable
>>node to use. It has to have more features that just an easy setup.
>The adaptive parameters makes is easy to set up and also very good!
>So it is both the best packet driver avalaible and easy to setup!
Does it have any more features than adaptive parameters ?
A correct setup can eliminate most of the problems.
Best packetdriver available ?, only because of adaptive parameters ?
...snip... huge signaturetext removed
73 de SM3LKS
Read previous mail | Read next mail
| |
