[nos-bbs] Mbox jumpstart

[Michael Fox - N6MEF]

Brian,

JNOS seems to be a bit weird in this regard.  The manual says to set "ax25 mycall" and "ax25 bbscall" to different values and that "ax25 bbscall" will "jump-start" the mailbox.

What we do is:

autoexec.nos:
  ax25 mycall w1xsc
  ax25 bbscall w1xsc-1

Then we have users connect over the radio to w1xsc-1.  They are immediately connected to the mailbox (they get the SID, etc.).

But over AXIP/AXUDP, it's different.  In my forward.bbs entries for each JNOS system that I connect to via AXIP/AXUDP, I have to include an extra line with a "." (return).  Otherwise, the remote JNOS system does not respond with the SID after connect and the connection just sits there and does nothing.  Example:

forward.bbs:
  w1xsc
  ax25 pW1XSC w1xsc-1
  .
  <mailbox-list>
  ----

It's annoying.  But I never reported it because I had the workaround of the ".".  I tried connecting to the mycall value, but that does nothing (I don't really know what it's purpose is).  Maybe it's time to get it fixed?

Michael
N6MEF


> -----Original Message-----
> From: nos-bbs [mailto:nos-bbs-bounces at tapr.org] On Behalf Of Brian
> Sent: Tuesday, September 20, 2016 8:45 AM
> To: nos-bbs at tapr.org
> Subject: [nos-bbs] Mbox jumpstart
> 
> I'm trying to look for a flag so that via vanilla ax25 the
> mailbox does NOT require jumpstarting. Right now after an initial
> connect the user has to press enter:
> c ax3 n1uro-7
> link setup (ax3)...
> *** connected to N1URO-7
> 
> 
> and it will stay there until <return>  is pressed. By not jumpstarting
> the mbox, jnos will be more FlexNet friendly.
> 
> 
> --
> I was going to go see a Guns 'n' Roses concert...
> until the liberals took away ALL the guns. Now I'm
> only going to see Roses *sigh*
> -----
> 73 de Brian - N1URO
> email: (see above)
> Web: http://www.n1uro.net/
> Ampr1: http://n1uro.ampr.org/
> Ampr2: http://nos.n1uro.ampr.org
> Linux Amateur Radio Services
> axMail-Fax & URONode
> http://uronode.sourceforge.net
> http://axmail.sourceforge.net
> AmprNet coordinator for:
> Connecticut, Delaware, Maine,
> Maryland, Massachusetts,
> New Hampshire, New Jersey, Pennsylvania,
> Rhode Island, and Vermont.