[nos-bbs] Hidden Digipeater Path Setting?

[N0MR]

Brett,

I do not see your station from WISS. Try connecting to WISS. Then connect on 
to DULBBS. If that all works, then you can try the digipeater command c port 
dulbbs v wiss. I believe you need the v or via in the command. At DULBBS, 
you can send me mail with the address n0mr at n0mr.

Jerry, N0MR

----- Original Message ----- 
From: "Brett Friermood" <brett.friermood at gmail.com>
To: "TAPR xNOS Mailing List" <nos-bbs at tapr.org>
Sent: Tuesday, April 10, 2012 2:26 PM
Subject: [nos-bbs] Hidden Digipeater Path Setting?


> Thanks again to everyone for the help you've given me this far. I'm
> making progress and am understanding JNOS more.
>
> I was able to do some valuable testing last night while monitoring
> with another station. I confirmed everything works and gained a lot
> more knowledge of the protocol and network by seeing the connections
> decoded in realtime, however I stumbled across something else.
>
> At one time I was trying to connect to the BBS, DULBBS, by digipeating
> through another node, WISS, using the command "c radio dulbbs wiss".
> My packets were decoding as: "KC9MWG>DULBBS,WISS <<C>>". I was unable
> to connect so I killed the session and got back to the command line.
>
> Then I tried to connect again to DULBBS but my transmitted packets
> were still "KC9MWG>DULBBS,WISS <<C>>". Did I unknowingly set a
> variable or something? I was using the plain old "c radio dulbbs" as
> before, which before was transmitting "KC9MWG>DULBBS <<C>>".
>
> Thanks,
> Brett
> KC9MWG
>
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> https://www.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>