| |
F1OYP > BPQ 09.07.00 08:42l 415 Lines 13068 Bytes #-9585 (0) @ EU
BID : 306-F1OYP
Read: DG4MFN GUEST
Subj: BPQ cfg fbb+tnc2 (4/5)
Path: DB0AAB<DB0FSG<I4UKI<IK2HDG<IK1MAP<I1YLM<IK1ZNW<KB7FRV<VE2RNT<F5JOE<
F1OYP
Sent: 000707/0533Z @:F1OYP.FAQI.FRA.EU #:44314 [Perigueux] FBB7.00g25 $:306-F1O
From: F1OYP@F1OYP.FAQI.FRA.EU
To : BPQ@EU
[¯¯¯ TSTH V 143aF , UTC diff:5, Heure Locale:Ven Jul 07 06:19:52 2000®®®]
msg 4/5 :
re-send 07/07/2000 to bpq@eu
___________________________________________________________________________
Ma configuration
config bpq / tnc2 en kiss + FBB
___________________________________________________________________________
--- 2tnc2.bat :
rem Chargement de 2 x TNC2 en Kiss
SETKISS 1 9 H
SETKISS 2 9 H
bpqcfg
bpqcode
cd c:\fbb\bin
appel.bat
--- Port.sys
#
# FBB7.00g (j'occulte les textes)
# avec BPQ
#
#Ports TNCs
2 2
#
#Com Interface Address (device) Baud
#
1 2 3F8 9600
2 2 2F8 9600
#
#TNC NbCh Com MulCh Pacl Maxfr NbFwd MxBloc M/P-Fwd Mode Freq
#0 0 0 0 0 0 0 0 00/01 ---- File-fwd.
1 6 1 1 230 2 4 5 20/15 UQLYW 145.275
2 5 2 1 230 2 4 5 30/30 UQYW 433.675
#
# End of file.
#
--- bpqcfg.txt :
;********************************
;bpqcfg.txt__2tnc2_kiss_s/s_dos >
;********************************
;
; For Version 4.08
;
;
; CONFIGURATION FILE FOR G8BPQ SWITCH SOFTWARE
;
; The program which converts this text file to binary
; form is currently very crude - be VERY careful when
; editing this file!
;
;
; The order of parameters in not important, but they
; all must be specified - there are no defaults
;
;
;
HOSTINTERRUPT=127 ; Sets the Interrupt used to access BPQ Host Mode. Will
; normally be 127, but may be changed if this clashes with
; other software. BTRIEVE seems to use 127, so if you are
; using it, try INTERRUPT=126
; Memory Usage. If EMS=1, the system will attempt to put its
; data area into EMS Memory. At the moment it makes no attempt
; to manage sharing of the EMS window, so you must not run any other
; software using EMS.
;
; Setting EMS=1 seems to cause problems with Desqview. I suggest it
; is only used with non-DV installations.
;
;
EMS=0 ; dont use EMS RAM
;
; I seem to have problems with systems not using DESQVIEW - especially
; NNA BBS's. The DV calls SHOULD be ignored if DV is not loaded, but
; just in case, if you set DESQVIEW=0, the 'Release Timeslice' call
; wont be used. MAKE SURE that you set DESQVIEW=1 if using DV, or
; performance will be seriously affected.
;
DESQVIEW=0
;
;
; Station Identification.
;
; If a user connects to the NODE Callsign or Alias, he is linked
; to the switch code, and can use normal NetRom/TheNet commands
;
; If he connects to the BBS Callsign or Alias he will be connected
; directly to a BBS port. If none are available, the connect will
; be rejected.
;
; Note that of you are running only a NODE (ie BBS=0), or
; or just a BBS (NODE=0), then you must still put in two pairs of calls,
; but they MUST be the SAME.
;
; If you are running both, the calls MUST be different
NODECALL=F1OYP-12 ; NODE CALLSIGN
NODEALIAS=NODPGX
BBSCALL=F1OYP ; BBS CALLSIGN
BBSALIAS=BBS ; BBS ALIAS
;
; 'ID' MESSAGE - SENT EVERY IDINTERVAL MINS
;
; WILL BE ADDRESSED FROM THE PORT CALLSIGN (IF DEFINED)
; ELSE FROM THE NODE CALL
;
; The following format allows KA nodes to include your system in
; their 'Nodes' lists.
;
IDMSG:
ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»
º -*- Node BPQ -*- Test º
ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ
****
;
UNPROTO=MAIL ; DEFAULT UNPROTO ADDR
; 'I' COMMAND TEXT
;
; Note that the bit about needing a port param in connects is only
; necessary if you are running more that one (radio) port.
;
INFOMSG:
F1OYP-12 -*- BPQnode Packet Switch.
Test bpq
***
;
; CTEXT - Normally will only be sent when someone connects to
; the NODE ALIAS at level 2. If FULL_CTEXT is set to 1, it
; will be sent to all connectees. Note that this could confuse BBS
; forwarding connect scripts.
;
CTEXT:
Welcome sur le Node_BPQ
BPQnode!
Tapez ? pour les cmds.
***
FULL_CTEXT=0 ; SEND CTEXT ONLY TO L2 CONNECTEES TO ALIAS
; Network System Parameters
;
OBSINIT=5 ; INITIAL OBSOLESCENCE VALUE
OBSMIN=4 ; MINIMUM TO BROADCAST
NODESINTERVAL=15 ; 'NODES' INTERVAL IN MINS
IDINTERVAL=15 ; 'ID' BROADCAST INTERVAL (UK Regs require
; an AX25 ID every 15 mins)
;
BTINTERVAL=0 ; NO BEACONS
L3TIMETOLIVE=25 ; MAX L3 HOPS
L4RETRIES=3 ; LEVEL 4 RETRY COUNT
;
; I have seen suggestions that L4TIMEOUT should be increased to very
; high values (even as long as seven mins). Although 60 may be a bit
; short in some cases, I STRONGLY advise that you dont go much above
; 120 secs unless you understand ALL the implications.
;
; I've set TTL and TIMEOUT to the values agreed by the latest SYSOPS
; meeting - this does not imply that I agree with them!
;
L24TIMEOUT=120 ; LEVEL 4 TIMEOUT
L4DELAY=10 ; LEVEL 4 DELAYED ACK TIMER
L4WINDOW=4 ; DEFAULT LEVEL 4 WINDOW
;
MAXLINKS=30 ; MAX LEVEL 2 LINKS (UP,DOWN AND INTERNODE)
MAXNODES=120 ; MAX NODES IN SYSTEM
MAXROUTES=35 ; MAX ADJACENT NODES
MAXCIRCUITS=64 ; NUMBER OF L4 CIRCUITS
MINQUAL=10 ; MINIMUM QUALITY TO ADD TO NODES TABLE
BBSQUAL=255 ; BBS Quality relative to NODE - used to
; limit 'spread' of BBS through the network
; to your required service area. I've been
; asked to set a low default to encourage you
; to think about a suitable value. Max is 255
BUFFERS=255 ; PACKET BUFFERS - 255 MEANS ALLOCATE AS MANY
; AS POSSIBLE - NORMALLY ABOUT 130, DEPENDING
; ON OTHER TABLE SIZES
;
; TNC DEFAULT PARAMS
;
PACLEN=230 ; MAX PACKET SIZE
;
; PACLEN is a problem! The ideal size depends on the link(s) over
; which a packet will be sent. For a session involving another node,
; we have no idea what is at the far end. Ideally each node should have
; the capability to combine and then refragment messages to suit each
; link segment - maybe when there are more of my nodes about than 'real'
; ones, i'll do it. When the node is accessed directly, things are a
; bit easier, as we know at least something about the link. So, from
; Version 3.11 onwards, there are two PACLEN params, one here and
; one in the PORTS section. This one is used to set the initial value
; for sessions via other nodes, and for sessions initiated from here.
; The other is used for incoming direct (Level 2) sessions. In all cases
; the TNC PACLEN command can be used to override the defaults.
;
; The main reason for changing this now was a request from someone
; wanting to run an HF port.
;
;
;
TRANSDELAY=0 ; TRANSPARENT MODE SEND DELAY - 1 SEC
;
; Level 2 Parameters
;
; T1, T2 and N2 are now int the PORTS section
;
T3=180 ; LINK VALIDATION TIMER (3 MINS)
IDLETIME=900 ; IDLE LINK SHUTDOWN TIMER (15 MINS)
;
;
; Configuration Options
;
BBS=1 ; INCLUDE BBS SUPPORT
NODE=1 ; INCLUDE SWITCH SUPPORT
;
HIDENODES=0 ; IF SET TO 1, NODES STARTING WITH # WILL
; ONLY BE DISPLAYED BY A NODES * COMMAND
;
; THE *** LINKED COMMAND IS INTENDED FOR USE BY GATEWAY SOFTWARE, AND
; CONCERN HAS BEEN EXPRESSED THAT IT COULD BE MISUSED. I RECOMMEND THAT
; IT IS DISABLED IF NOT NEEDED.
;
ENABLE_LINKED=Y ; CONTROLS PROCESSING OF *** LINKED COMMAND
; Y ALLOWS UNRESTRICTED USE
; A ALLOWS USE BY APPLICATION PROGRAM
; N (OR ANY OTHER VALUE) DISABLE
;
;
;
;
; 'COMBIOS' Port definitions.
;
; This section defines the virtual TNC's that the code supports.
;
; The basic format is:
;
; TNCPORT
; COM=n ; COMBIOS port number
; APPLMASK=nn ; Defaults to 1 (BBS)
; APPLFLAGS=nn ; Defaults to 6
; ENDPORT
;
; See APPLS.DOC for details on use of APPLFLAGS and APPLMASK
;
; Only TNC2 applications are supported through this interface.
; For information on using KISS or DEDHOST applications, see file
; DRIVERS.DOC
;
; Dont try to define more than 16 ports.
;
TNCPORT
COM=1
ENDPORT
;
;
TNCPORT
COM=2
ENDPORT
;
;
;
; AX25 PORT DEFINITIONS
;
; These define the external links - normally to radios, but possibly
; to other computers, modems, etc.
;
; The hardware type and protocol are now defined separately, but
; at the moment only a limited number of combinations are possible
;
; Interrupt levels may be shared by any cards with suitable
; hardware. Examples are all but the earliest DRSI cards, and
; a MS400 modified as described by AA4RE in his MBBIOS documentation.
;
; There is a significant overhead in using the shared interrupt
; feature - try to use it on relatively low speed links, and
; wath out for TX underruns/RX overuns.
;
;
; See file PORTS.DOC for full details of available paramters.
;
; Note that all timer values are in ms intervals. Most TNC's
; use different units for the various timers, so be careful!
;
; The timings are all derived from the PC's timer interrupt,
; who's frequency is about 18.2 HZ, so the resolution is only to
; approx 50ms.
;
; ParamŠtres du port 1
PORT
ID=tnc2
TYPE=EXTERNAL
PROTOCOL=KISS
IOADDR=3F8H
INTLEVEL=4
SPEED=9600
CHANNEL=A
QUALITY=10
MAXFRAME=2
TXDELAY=500
SLOTTIME=150
PERSIST=128
FULLDUP=0
FRACK=7000
RESPTIME=2000
RETRIES=10
PACLEN=230
UNPROTO=F1OYP-1
DIGIFLAG=1
DIGIPORT=0
MHEARD=1
ENDPORT
;
; ParamŠtres du port 2
PORT
ID=tnc2
TYPE=EXTERNAL
PROTOCOL=KISS
IOADDR=2F8H
INTLEVEL=3
SPEED=9600
CHANNEL=A
QUALITY=10
MAXFRAME=2
TXDELAY=500
SLOTTIME=150
PERSIST=128
FULLDUP=0
FRACK=7000
RESPTIME=2000
RETRYS=20
PACLEN=230
DIGIFLAG=1
DIGIPORT=0
MHEARD=1
ENDPORT
;
ROUTES:
;
; ROUTES TO LOCK IN
;
; specify Callsign, Quality and Port. You can now also specify
; MAXFRAME, FRACK, PACLEN (in that order) to override the port
; defaults.
;
;
***
;
; APPLICATIONS SUPPORTED
;
; UP TO 8 ENTRIES OF UP TO 12 BYTES EACH
;
; THE FIRST 3 ARE RESERVED FOR BBS, HOST, AND REMOTE SYSOP - YOU
; CAN DEFINE THE OTHERS AS YOU LIKE.
;
; FOR COMPATIBILITY WITH EARLIER VERSIONS, JUST ENTER APPLICATIONS=BBS
;
; NAMES STARTING WITH * ARE NOT INCLUDED IN 'VALID COMMANDS' DISPLA
;
APPLICATIONS=BBS
;
; NOTE THAT THE LAST ITEM CREATES A 'COMMAND ALIAS'. IF THE USER
; ENTERS 'CHAT' THIS IS CONVERTED BY THE SWITCH TO 'C NMCHAT'. THE
; TOTAL LENGTH OF THE PAIR CANNOT EXCEED 15 BYTES
;
Le chargement des 2 tnc2 sous FBB peut ˆtre envisag‚ de deux fa‡ons :
- soit comme le montre l'exemple ci-dessus , on charge chaque TNC sur
chaque COM en "direct" , adresse + irq dans FBB & dans BPQ , ce qui
ne pose pas de pbs sur chaque pc ‚quip‚ d'un com1 et d'un com2.
- soit on dispose de coms suppl‚mentaires com3 , com4 , ou + et dans ce
cas l… la notion de com virtuel "com8" et MULCH dans FBB sera bien utile
pour que les deux softs soient sur la bonne longueur d'onde ...
Cette solution est FB , car aussi bien TFPCX que SETKISS ont leurs
limites et posent des pbs … ceux qui veulent charger plus de coms au-del…
des coms 1 & 2 traditionnels.
Pour config sp‚cifique , me consulter . C'est parfois la prise de tˆte
pour param‚trer quelques lignes sous fbb et bpq ...
Chez moi ‡a tourne en fbb7 sur un 486/33 avec 4 coms et le tout sous BPQ.
Bonne bidouille
jean pierre / f1oyp
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
Û FBB 7.00g - jn05if - P‚rigueux Û
ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ
APRS=4511.50N/00044.54E
Read previous mail | Read next mail
| |
