<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.10.3">
</HEAD>
<BODY>
QSL Andre - the "initial packet delivered to the BBS" is well exampled in my neighborhood by various sites with jnos.<BR>
In addition, I seem to recall several occurrences of this detail on this reflector...<BR>
<BR>
Clearly - I have disadvantaged the AX.25 BBS user by my choice of a single SSID for my configuration.<BR>
On my site the *blank* needs to be sent after the "CONNECTED" message per your note.<BR>
At this moment I have not fully defined the problem thus I will not adopt multiple SSID as a solution *yet*...<BR>
Perhaps multiple SSID is a solution, or perhaps it is a work-around waiting for a more elegant solution?<BR>
<BR>
On Wed, 2006-12-13 at 19:10 +0100, Andre van Schaijk wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">(Skip) K8RRA schreef:</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> As an addendum - NET-ROM connects from remote sites to "GHWEST" and </FONT>
<FONT COLOR="#000000">> "k8rra-1" quite normally via AX-25 I believe.</FONT>
<FONT COLOR="#000000">> No special SSID for NET-ROM service only at k8rra-1.</FONT>
<FONT COLOR="#000000">> The SSID at wa8rsa is set to -7 where -4 is the BBS & hamgate..</FONT>
<FONT COLOR="#000000">> Thus I conclude that both options work and it becomes owner choice...</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">> 73</FONT>
<FONT COLOR="#000000">> de [George (Skip) VerDuin] K8RRA k</FONT>
<FONT COLOR="#000000">></FONT>
<FONT COLOR="#000000">There is a very good reason to add a netrom and bbscall different from </FONT>
<FONT COLOR="#000000">the base call.</FONT>
<FONT COLOR="#000000">If you don´t set these jnos will use the basecall for netrom and bbs </FONT>
<FONT COLOR="#000000">trafic as wel as for tcp/ip trafic.</FONT>
<FONT COLOR="#000000">The result of this is that at the start of a connection jnos doesn´t </FONT>
<FONT COLOR="#000000">know what protocoll to use and waits for a frame from the remote site. </FONT>
<FONT COLOR="#000000">tcp/ip and netrom users won´t notice anything but your bbs users will </FONT>
<FONT COLOR="#000000">have to hit enter before they get a welcome from your jnos.</FONT>
</PRE>
</BLOCKQUOTE>
I find it interesting that jnos can differentiate NET-ROM and TCP/IP but not "vanilla" at connect time.<BR>
This is perhaps one of those classic examples of comparing apples and oranges for differences.<BR>
The BBS is a server function whereas NET-ROM and TCP/IP act more as communication "paths" between nodes.<BR>
<BR>
Before I leave this subject behind I feel the need to dig into the detail - and document the consequences of the choice (or oversight).<BR>
<BR>
<BLOCKQUOTE TYPE=CITE>
<PRE>
<FONT COLOR="#000000">Andre PE1RDW</FONT>
<FONT COLOR="#000000">_______________________________________________</FONT>
<FONT COLOR="#000000">nos-bbs mailing list</FONT>
<FONT COLOR="#000000"><A HREF="mailto:nos-bbs@lists.tapr.org">nos-bbs@lists.tapr.org</A></FONT>
<FONT COLOR="#000000"><A HREF="https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs">https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs</A></FONT>
</PRE>
</BLOCKQUOTE>
<TABLE CELLSPACING="0" CELLPADDING="0" WIDTH="100%">
<TR>
<TD>
<BR>
73<BR>
de [George (Skip) VerDuin] K8RRA k
</TD>
</TR>
</TABLE>
</BODY>
</HTML>