Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: "Günther Montag " <dl4mge@darc.de>
To: John Coppens <john@jcoppens.com>
Cc: -HFTERMHACKERS- <hfterm-hackers@lists.sourceforge.net>,
	linux hams <linux-hams@vger.kernel.org>
Subject: Re: usage of f6fbb via telnet port
Date: Mon, 26 Apr 2004 13:20:48 +0200	[thread overview]
Message-ID: <200404261320.48683.dl4mge@darc.de> (raw)
In-Reply-To: <20040422123757.3d4249a9.john@jcoppens.com>

Am Donnerstag 22 April 2004 17:37 schrieben Sie:
> On Thu, 22 Apr 2004 15:49:53 +0200
>
> Günther Montag  <dl4mge@darc.de> wrote:
> > 3286
>
> Hi Gunter
>
> This is what I found out:
>
> That port (3286) is open normally, but it is formatted to be used with the
> xfbbC terminal program. The username and password are made into a key to
> be sent to that port, to get actual access.
>
> According to 18.23 of the FBB manual:
>
> The address to use may be 189C (189C hex = 6300 decimal).
>
> But, it´s also possible to define another port address,
> for example if you want Telnet access to LinFBB on port 23,
> (port 23 is standard for Telnet, but 23 is also used by inetd in Linux!)
> then change the ´address´ of COM2 to 17 (hex 17 = 23 decimalt)
>
> Tip:
> You may put the R letter (Read only default access) which gives a
> read-only if the user is unknown or not authorized for Modem/Telnet (M
> Flag in EU command).
>
>
> <Image>Example of PORT.SYS for LinFBB
>
> Standard PORT.SYS with 1 TNC (COM1) with WA8DED-hostmode,
> 4 channels, 1 channel for outgoing forward,
> and one Telnet interface listening on port 6300,
> 8 channels, 1 channel for outgoing forward.
>
> #
> #Ports TNCs
> 2      2
> #
> #Com Interface Address (device)   Baud
> 1    9         /dev/cua0          9600
> 2    9         189C               0		<=== the telnet port at 6300
> #
>
> 73,
> John
> ON6JC/LW3HAZ

tnx!
How it i do want that access is read/write?

-- 
73 de
Günther
dl4mge@darc.de
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2004-04-26 11:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-22 13:49 usage of f6fbb via telnet port Günther Montag 
2004-04-23  6:23 ` Rodolfo Brasnarof
     [not found]   ` <200404231632.20056.dr.g.montag@gmx.net>
2004-04-26  5:05     ` Rodolfo Brasnarof
     [not found]   ` <200404231502.30654.dl4mge@darc.de>
2004-04-26  5:05     ` Rodolfo Brasnarof
2004-04-26 11:18       ` Günther Montag 
     [not found] ` <408968CA.4030304@free.fr>
     [not found]   ` <4089A467.3000507@eunet.yu>
2004-04-26 11:15     ` Günther Montag 
     [not found] ` <20040422123757.3d4249a9.john@jcoppens.com>
2004-04-26 11:20   ` Günther Montag  [this message]
     [not found]     ` <20040426163020.0c79a7af.john@jcoppens.com>
2004-04-27 14:26       ` Günther Montag 
     [not found]       ` <4091B615.25333.76512@localhost>
2004-04-30 12:27         ` Günther Montag 
2004-05-03 11:58         ` f6fbb via telnet port, f6fbb mailing list? Günther Montag 
2004-05-06  4:13           ` Rodolfo Brasnarof
2004-05-07 20:35             ` Rodolfo Brasnarof

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200404261320.48683.dl4mge@darc.de \
    --to=dl4mge@darc.de \
    --cc=hfterm-hackers@lists.sourceforge.net \
    --cc=john@jcoppens.com \
    --cc=linux-hams@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox