From: jabennett (terhi.victor@logonet.com)
Date: Fri Jul 06 2001 - 19:37:43 EEST
I concur with Roger. In fact, those perms have been enabled. Binary
forwarding over the ax25 radio ports works fine. The problem occurs when
you telnet over an Ethernet link. Could it be that the code only applies
perms to the ax25 radio ports only?
73, John
----- Original Message -----
From: "Roger Harris" <bivns@dasdial.com>
To: "Ian Russon" <wfutqci@hkr.se>; "g3orh" <hpfvtth.ondtjz@sirus.com>
Cc: <rhm@911-sales.com>
Sent: Thursday, July 05, 2001 1:34 PM
Subject: Re: compressed through 'node'
> Thanks for the comments, Ian and Colin.
>
> > > the answer is to add 287 to the node.perms files to any person
> > > who will be forwarding though it or even add it as default ???
>
> It's very true that this will disable the escape mechanism (it can also be
> done using "esc off" command).
>
> However, all this appears to do is to prevent the escape character (e.g.
> ctrl-T) from disconnecting the forwarding session. Whilst this is
necessary
> for compressed forwarding, it is not a complete solution.
>
> As far as I know, telnet does have a "BINARY" mode which can be invoked
> manually. Does this allow telnet to be completely transparent? If so,
> perhaps the answer is to make the node invoke telnet in this way, if a
> specific command is sent to the node. Alternatively, make it always behave
> like this if the escape character has been disabled. I can't think of a
> reason why you would want to disable the escape character and NOT want the
> connection to be transparent.
>
> Anyway... over to the experts ;-)
>
> Regards
>
> Roger
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-hams" in
> the body of a message to terhi.victor@logonet.com
>
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to otryoctu.qubkwgkiye@tu-bs.de
This archive was generated by hypermail 2b30 : Fri Jul 06 2001 - 19:44:12 EEST