conversd-saupp

conversd-saupp

[Ben Stienstra]

Dear all,
 
I'm setting up a saupp conversd server and got it running, almost... When i connect with the 'convers' client from the localhost, it works. But, when i connect via AX.25 i only get the "channel 0 has been removed" message, and nothing else. It just waits and disconnect after a long wait. Maybe someone can help me with it.

Please see the output below. 

c vhf pd0b-13
Trying...  The escape character is: CTRL-T
*** connected to PD0B-13
*
* Access to channel 0 has been removed from this server.
*

*** reconnected to PD0B-2 


I have tried everything from axconv (ax25d) to the ax25 listener and rawconvers, all give the same output on AX.25. I have no errors in the log. The line below is the only evidence from the connect:

Sep 19 23:28:00 voyage conversd[2118]: Incoming connection from PD0B-15 to ax25:pd0b-13,pd0b-1


Best regards,
Ben

Re: conversd-saupp

[Ladislav Vaiz]

Hi Ben,
try to force channel number with convers argument -c. As far as
I remember, channel 0 is disabled for security reason. Don't ask me why, 
I'm not convers guru :-)

73 Lada, OK1ZIA


On Mon, 19 Sep 2011, Ben Stienstra wrote:

> Dear all,
>
> I'm setting up a saupp conversd server and got it running, almost... When i connect with the 'convers' client from the localhost, it works. But, when i connect via AX.25 i only get the "channel 0 has been removed" message, and nothing else. It just waits and disconnect after a long wait. Maybe someone can help me with it.
>
> Please see the output below.
>
> c vhf pd0b-13
> Trying...  The escape character is: CTRL-T
> *** connected to PD0B-13
> *
> * Access to channel 0 has been removed from this server.
> *
>
> *** reconnected to PD0B-2
>
>
> I have tried everything from axconv (ax25d) to the ax25 listener and rawconvers, all give the same output on AX.25. I have no errors in the log. The line below is the only evidence from the connect:
>
> Sep 19 23:28:00 voyage conversd[2118]: Incoming connection from PD0B-15 to ax25:pd0b-13,pd0b-1
>
>
> Best regards,
> Ben
>
>
> --
> 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
>

Re: conversd-saupp

[Ben Stienstra]

> try to force channel number with convers argument -c. As far as
> I remember, channel 0 is disabled for security reason. Don't ask me why, I'm 
> not convers guru :-)

I'm not using axconv right now. I've configured conversd to listen to the 
AX.25 device.

I have now:
DefaultChan     137
BanZero 0

On the command line (localhost with convers command) it directly logs me 
into channel 137. But on the AX.25 side i still only receive the lines 
below.

*
* Access to channel 0 has been removed from this server.
*

It must be something else i'm overlooking. Just using a Alix3d3 board 
(i386) with Voyage Linux (Debian).

Re: conversd-saupp

[Ben Stienstra]

One thing i learned is that the message:

      * Access to channel 0 has been removed from this server.

Is from the conversd.issue file... So it is not a real error or config 
problem. I can just change the text in the file.

But i still do not see anything else than that after a connect to the 
AX.25 port. It does not react on any given commands, except for /bye! It 
then disconnects.

Re: conversd-saupp

[Willie Hein WJ3G]

What's your line in ax25d.conf to launch the client? It may not be 
logging in on connection.

Good luck!

Willie, WJ3G

On 09/20/2011 06:08 AM, Ben Stienstra wrote:
>
> One thing i learned is that the message:
>
>      * Access to channel 0 has been removed from this server.
>
> Is from the conversd.issue file... So it is not a real error or config 
> problem. I can just change the text in the file.
>
> But i still do not see anything else than that after a connect to the 
> AX.25 port. It does not react on any given commands, except for /bye! 
> It then disconnects.
>
>
> -- 
> 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
>

Re: conversd-saupp

[Ben Stienstra]

> What's your line in ax25d.conf to launch the client? It may not be logging in 
> on connection.

I'm not using ax25d (hope thats not part of the problem). I have 
configured conversd to listen to the AX.25 port itself:

/usr/local/etc/conversd/conversd.conf
Listeners       ax25:pd0b-13,pd0b-1


Device ax0 is configured with name pd0b-1. It is a working AX.25 port. I 
can connect to it etc.

Netstat shows:
Active AX.25 sockets
Dest       Source     Device  State        Vr/Vs    Send-Q  Recv-Q
*          PD0B-13    ax0     LISTENING    000/000  0       0

Re: conversd-saupp

[Thomas Osterried]

Hello,

- channel 0:
  conversd.issue is a file which contense is written after connect.
  You may use it to give hints. In the example, it's a notice about
  channel 0.
  Channel 0 usage is not a security issue, but has social reasons.
  We had problems with only a hand full "hams" without any ham spirit.
  Everytime a new OM connected (and for many conversd implementations,
  the default login channel was 0), they began to flame on the newcomer.
  conversd-saupp has many configuration options to handle that social
  disaster:
    - you could configure that channel 0 is not joinable at all
      (conversd.conf: BanZero 1).
    - DefaultChan 1234 (-> user is logged on on channel 1234 - i.E. your
      channel where most local users / sysop team / etc.. are on, being
      able to give hints)
    - DefaultChan 0 configures conversd-saupp to use dice a random channel.

- What to do after a connect?

dl9sau-g> c db0tud-9 db0tud-10
Conn pend
Connected
* convers at db0tud.
* Access to channel 0 has been removed from this server.
*
* Please join with
* /name yourcall channelnumber
*

conversd-saupp does not login the user automaticaly to a channel.
Simply because the user might first try to look if the contact he likes
to chat with is online. Or the sysop likes to check if the links are ok.
I.e., commands like "cstat", "exit", "login", "rtt", and so on are
valid. These are commands to the convers-server which do not introduce
any traffic to other servers.
For a complete list, see 
  $ grep CM_UNKNOWN conversd.c

Another important feature (at least for me) is, that I've the choice
to either
  - use normal text mode, by issuing /name dl9sau 1234
or to enter irc-client mode if I connect with my favourite IRC-client.
conversd-saupp is able to recognize (by the NICK command - which is part
of the IRC-protocol).
    Btw, as a linux user it was very easy for me to script a little daemon
    that listens to localhost:someport and issuing an ax25 connect to a
    convers-server after my local irc-client connects to localhost:someport.

Note that the non-automatical login is not a "new feature", it's a behaviour
conversd had ever since.

It's not conversd-saupp's fault that there are other
convers-implementations around which do an automatical login. With all
the problems it may cause, i.E. that if a neighbor conversd connects
via ax25 for establishing a link, but the configuration of the local
conversd is not correct, the conversd joins to a channel as a normal
user - which is not really a great idea.

vy 73,
	- Thomas  dl9sau

On 2011-09-20 12:08:09 +0200, Ben Stienstra <b.stienstra@xs4all.nl>
wrote in <alpine.LNX.2.02.1109201202440.2190@archlinux.home>:
> 
> One thing i learned is that the message:
> 
>      * Access to channel 0 has been removed from this server.
> 
> Is from the conversd.issue file... So it is not a real error or
> config problem. I can just change the text in the file.
> 
> But i still do not see anything else than that after a connect to
> the AX.25 port. It does not react on any given commands, except for
> /bye! It then disconnects.
> 
> 
> --
> 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

Re: conversd-saupp

[Ben Stienstra]

Thomas,

> conversd-saupp does not login the user automaticaly to a channel.

Amazing... this was indeed a user (my) error. It does work, as it always 
did. I just didn't know how.

Thank you very much for you time and explanation.


Regards,
Ben

Re: conversd-saupp

[Thomas Osterried]

On 2011-09-20 13:38:44 +0200, Ben Stienstra <b.stienstra@xs4all.nl>
wrote in <alpine.LNX.2.02.1109201336240.2190@archlinux.home>:
> Thomas,
> 
> >conversd-saupp does not login the user automaticaly to a channel.
> 
> Amazing... this was indeed a user (my) error. It does work, as it
> always did. I just didn't know how.
> 
> Thank you very much for you time and explanation.

congrats.

I'd suggest to add a notice in conversd.issue in order to give a user
the hint that he'd should issue the command
/name callsign channelnumber

Have fun with your new conversd.

vy 73,
	- Thomas  dl9sau