[fbb] kantronics HOST mode FBB7g
ve7ken@amsat.org
ve7ken@amsat.org
Sun, 14 Jan 2001 02:59:59 -0800
This is a multi-part message in MIME format.
------=_NextPart_000_0049_01C07DD6.151EFE80
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_004A_01C07DD6.151EFE80"
------=_NextPart_001_004A_01C07DD6.151EFE80
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I do hope you are wrong Emery but have noted it. I would much rather =
not use BPQ if I can avoid it. Computer seems to not like it. I will =
rephrase the request:
,
I am having a small problem with FBB I am running a system with a VHF
port, a telnet port and a modem port. The problem comes up when someone
comes in with proper verified Password etc... and wants to use the =
gateway
to connect out on the VHF port. It seem that FBB does not want to pass =
the
Users callsign onto the TNC (which is a KAM 9612 in HOST Mode) All the
gateway settings are set in the port.sys file and in the options. =
Should
something be set in the Inittnc#.sys file A copy of my Port.sys file is
attached.
Thanks for any assistance given
----- Original Message -----=20
From: Emery J. Heintz=20
To: ve7ken@amsat.org=20
Sent: Saturday, January 13, 2001 7:17 PM
Subject: Re: [fbb] Fw: help needed to solve fbbwindows 7g - 2nd =
request
Hello Ken
=20
I read your query about the Gateway Call sign with WinFbb. I think =
your stuck with the problem as long as your using host mode. BPQ 4.08A =
and kiss mode works correctly by changing the call sings to the users =
call sign.
=20
If you find some other cure, while still using host mode please post =
it on the reflector
73
=20
Emery =20
------=_NextPart_001_004A_01C07DD6.151EFE80
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I do hope you are wrong Emery but have =
noted=20
it. I would much rather not use BPQ if I can avoid =
it. Computer seems=20
to not like it. I will rephrase the </FONT><FONT face=3DArial=20
size=3D2>request:</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>,<BR><BR> I am having a =
small problem=20
with FBB I am running a system with a VHF<BR>port, a telnet port and a =
modem=20
port. The problem comes up when someone<BR>comes in with proper =
verified=20
Password etc... and wants to use the gateway<BR>to connect out on the =
VHF=20
port. It seem that FBB does not want to pass the<BR>Users callsign =
onto=20
the TNC (which is a KAM 9612 in HOST Mode) All the<BR>gateway settings =
are set=20
in the port.sys file and in the options. Should<BR>something be =
set in the=20
Inittnc#.sys file A copy of my Port.sys file =
is<BR>attached.<BR><BR>Thanks for=20
any assistance given<BR><BR></FONT></DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A href=3D"mailto:emery@oregontrail.net" =
title=3Demery@oregontrail.net>Emery J.=20
Heintz</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
href=3D"mailto:ve7ken@amsat.org"=20
title=3Dve7ken@amsat.org>ve7ken@amsat.org</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Saturday, January 13, =
2001 7:17=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: [fbb] Fw: help =
needed to=20
solve fbbwindows 7g - 2nd request</DIV>
<DIV><BR></DIV>
<DIV><FONT face=3DArial>Hello Ken</FONT></DIV>
<DIV><FONT face=3DArial></FONT> </DIV>
<DIV><FONT face=3DArial>I read your query about the Gateway Call sign =
with=20
WinFbb. I think your stuck with the problem as long as your =
using=20
host mode. BPQ 4.08A and kiss mode works correctly by =
changing=20
the call sings to the users call sign.</FONT></DIV>
<DIV><FONT face=3DArial></FONT> </DIV>
<DIV><FONT face=3DArial>If you find some other cure, while still using =
host mode=20
please post it on the reflector</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial>73</FONT></DIV>
<DIV><FONT face=3DArial></FONT> </DIV>
<DIV><FONT face=3DArial>Emery =
</FONT></DIV></BLOCKQUOTE></BODY></HTML>
------=_NextPart_001_004A_01C07DD6.151EFE80--
------=_NextPart_000_0049_01C07DD6.151EFE80
Content-Type: application/octet-stream;
name="Port.sys"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="Port.sys"
# FBB7.00
# File for programming of channels and TNCs.
#
# Ports : How many ports (COM1, COM2, Etc...)
# TNCs : How many TNCs and modems in use. With multiplexer
# there can be up to 4 TNCs per port.
#
#Ports TNCs
3 3
#
#In WinFBB ONLY THESE interfaces are available:
# Interface : 2 =3D BPQ-node (BPQ in AA4RE-mode)
# 4 =3D DRSI
# 5 =3D TFPCR/TFPCX interface. Interrupt MUST be 0xFD or =
the same
# as stated in INIT.SRV, if any..
# 6 =3D Windows-driver, replaces both ESS, ESSKAM and =
FBBIOS.
# 7 =3D TCP/IP. Needs WINSOCK.DLL. Put port-address as 17.
# TNC-emulation is T (see below)=20
# 8 =3D TFWin.dll (Only WinFBB32)
# BEWARE: The old interface 1 and 3 will NOT be used in WinFBB. =
Interface 6
# replaces both. (FBBCOMM.DRV). Neither ESS nor FBBIOS can be
# used with WinFBB !
#
#In LinFBB ONLY this interface is available:
# Interface 9 =3D Linux. Can work via serial port (D),via AX25 domain
# socket (X) or via Telnet port (T).
#
#In DosFBB ONLY THESE interfaces are available:
# Interface : 1 =3D Use external COMBIOS-driver (MBBIOS, ESS etc)
# 2 =3D BPQ-node v 4.05 and up (BPQ in AA4RE-mode)
# 3 =3D Telephone-modem with FBBIOS
# 4 =3D DRSI card with driver
# 5 =3D TFPCR/TFPCX interface. Interrupt MUST be 0xFD
#
# Address : Address of port in hexadecimal (Needed for multiplexer).
# In LinFBB:
# Address is the device name (/dev/cua0).
# Be sure you have the rights to access to the device =
(rw-rw-rw-).
# When using kernel AF_AX25 socket, address is not used.
# When using Telnet, address is the Telnet port in Hex (Hex =
17 =3D Telnet port 23)
# Baud : Ports baud rate. Ignored by BPQ, kernel AF_AX25 socket and =
Telnet.
#
# Use same number of lines as number of ports.
#
#Com Interface Address (device) Baud
11 7 17 19200
1 6 3f8 19200
2 6 2f8 19200
#
# TNC : Number on TNC in use. Use 0 for file-forward !
# NbCh : Number of channels I want to use in the TNC.
# Maximum available channels depend on firmware.
# Com : Number of the COM-port. Com1, Com2 etc.
# MultCh : Number of channel if port-multiplexer is used, otherwise 1.
# In DRSI use values from 0 to 7, by KAM use 1/VHF and 2/HF.
# With BPQ first TNC must have MultCh 0, the next 1, etc.
# When using kernel AF_AX25 socket in Linux, MultCh is the
# interface name (eg: ax0)
# Paclen : PACLEN on this TNC.
# Maxframe: The maximum nb of frames the TNC will send at a time.
# NbFwd : Number of channels for OUTGOING forward at same time.
# MxBloc : Size of forward-block in kb.
# M/P-Fwd : Minute of the hour for start of forward, and period
# (how many minutes between each forward-start).
# Port mode, one of these:
# B : BBS-mode.
# G : "Guest"-mode.
# U : Normal-mode.
# Type host-mode, one of these:
# H : SCS/PTC-II (extended/WA8DED emulation) pactor TNC.
# D : WA8DED
# K : KAM hostmode. Must use ESSKAM driver.
# P : PK-232
# Q : BPQ v 4.x
# T : Ethernet/TCP-IP
# X : AX25 domain socket (for Linux)
# Addition: One or more of these letters can be used too:
# L : Send unproto beacon after each arriving mail.
# M : Telephone-modem.
# Y : Yapp allowed on this QRG.
# W : Gateway allowed TO this QRG.
# R : Modem port allowed in Read-only mode.
# Freq. : Text to describe this port (max 9 characters, no space)
#
# Same number of lines as TNCs:
#
#TNC NbCh Com MultCh Pacln Maxfr NbFwd MxBloc M/P-Fwd Mode Freq
0 0 0 0 0 0 0 0 00/01 ---- File-fwd.
1 10 11 0 250 2 1 10 00/60 TUWR TELNET
2 4 2 1 120 4 1 10 00/60 KULWY 144.930
3 1 1 0 250 4 1 10 00/60 MU MODEM
#
# Special callsigns and modes for some channels.
#
#TNC Nbs Callsign-SSID Mode
#1 1 LA1B-1 B
#
# End of file.
#
------=_NextPart_000_0049_01C07DD6.151EFE80--