P2P SSID

[mike...@well-dunn.com]

  Hi,

Is it possible to change the SSID that Pat registers when you enable listening for peer 2 peer connections?  I had someone tell me the other day that they couldn't connect to my AX.25 BBS, and I realized that Pat was answering the -1 SSID instead of the BBS.  I would like to have Pat listening to AX.25, but on a different SSID.

  Thanks

  Mike

[Kyle K]

What do you get if you do:

 netstat --protocol=ax25 -l

On my computer it appears to be listening on the -0 SSID

[mike...@well-dunn.com]

  Hi Kyle,

My apologies, you are absolutely correct, it does bind to -0 .  I still have the same question though.  I'm getting folks connecting to P2P expecting either a BBS or a CONVERS chat.  I'd like to bind it to -2 since there isn't really a conventional use for that SSID (as near as I can tell).

  Thanks

  Mike

[Kyle K]

So was Pat answering on both -0 and -1?

I'm wondering if having it Pat listen on -2 might confuse the winlink protocol, I'm going to set my callsign in pat to VA7KYL-2 and see what RMS express does if I try to send it a P2P message. 

[mike...@well-dunn.com]

  Oh, so apparently you can just put a SSID in call sign configuration?  I made that change and it is listening on -2 now.  I don't have windows, so I can't test out a P2P winlink session just yet :) .

  Previously it was listening on -0 only; the -1 confusion came from a user who reported that he could not connect to my -1 BBS.  I incorrectly stated that it was listening to -1 and speculated that it was causing issues with my BBS.

  Thanks

  Mike

[LA5NTA]

I think this is a reasonable request. It is correct that Pat will bind to -0 by default, but it would be great if users could set mycall: N0CALL and still be able to specify an arbitrary SSID for the AX.25 listener.

I believe it's a relatively easy to extent the ax25 config section with an optional SSID int value, and then pass that to wl2k-go/transport/ax25's listener.

If someone can create a new issue on github for this, I would very much appreciate it :)

-- 

73 de LA5NTA

[mike...@well-dunn.com]

  Thanks, Martin.  I just submitted it on github.

  Cheers

  Mike

[mike...@well-dunn.com]

  As an update, I just discovered today that I'm unable to retrieve Winlink email after making this change.  Apparently adding the SSID to mycall causes the Winlink server to be unable to deliver my messages.  This took me a while to discover because I don't get a lot of Winlink email :) .

  The interesting thing is that the CMS servers never complained.  With mycall set to KG7WFV-2, I could login and check for messages (none were found).  Setting mycall back to KG7WFV, I immediately downloaded 4 messages that had been queued.  It would appear to be able to retrieve Winlink email and listen for P2P on anything but -0 we would need the modification that Martin mentioned.

  Thanks

  Mike