开云体育

Hello Max,

I think we need to start with what you mean by "BBS".? Many hardware TNCs offer a "Personal" BBS or PBBS for leaving simple packet messages as well as node functionality to see details like remote stations heard, create new connections to other remote nodes, send NETROM advertisements, etc.? Is this the "simple PBBS" functionality you're looking to emulate on your Raspberry Pi?

Then there are full blown Packet BBS solutions coming from software like BPQ32, JNOS, FBB, etc.? These programs are fully featured, can relay packet messages back and forth from other compatible packet BBSes, etc.? Is this "Full BBS" functionality what you seek?? There are some significant differences between some of the BBS programs so you'll need to research this and narrow the choices down to your needed functionality but I can say:

?? BPQ32 BBS:
????? - Under active development
????? - Runs on multiple OSes including Linux
????? - has a smaller core feature set but can be dramatically enhanced with add-ons
????? - Flexible packet I/O: Can uses it's own AX.25 stack with serial KISS, supports AGW I/O instead of KISS, supports the native Linux AX.25 stack

?? JNOS BSS:
????? - Under active development
????? - Runs on Linux
????? - has a complete BBS feature set
????? - Flexible packet I/O: Can uses it's own AX.25 stack with serial KISS, supports AGW I/O instead of KISS, supports the native Linux AX.25 stack

?? LinFBB BBS:
????? - Under maintenance support
????? - Runs on Linux
????? - has a complete BBS feature set
????? - Only supports the native Linux AX.25 stack

There are other legacy BBS programs but pretty much of them are no longer developed: TNOS, TnT, N0ARY, OpenBCM, etc.

All other programs like Linpac, QtTCPTerm, EasyTerm, etc. are not real BBSes.? They might offer some nifty features and maybe sometimes emulate


Regardless of your desired functionality, any of those hardware TNCs will work as they will need to be put into KISS mode.? Once in KISS mode, software running on the connected PC will take over all responsibilities on the AX.25 stack and all higher level functions. ? Running any TNC in KISS mode is a bit of a compromise but it works well enough.? One of the better solutions now is to use software-TNCs with AGW API connectivity.? This type of setup allows the Software-TNC+Radio to service all AX.25 I/O and just send application payloads to the BBS program.

Finally, Outpost is a Window packet client program and NOT a BBS/Nodes/etc.? If you are interested in more details of how a EmComm usecase can use Outpost + Packet BBS, there are several groups doing this today.? One example of a group doing this is:

?? #Linux x86 servers running JNOS with three radios per computer
?? #? 2m enduser RF, 1.25m enduser RF, 70cm BBS-to-BBS fwding, Wifi BBS-to-BBS fwding, Internet BBS-to-BBS fwding
?? #? enduser Windows clients running Outpost PMM
?? #
??

--David
KI6ZHD