Jean VE2PKT helpt me to get things going. Thank you Jean. I really appreciate it.
I first have to compile a new Jnos version with the NNTP(s) enabled, edit your config.h and define NNTPS.
(#define NNTPS /* Netnews client and server */)
I had problems if I wanted to connect the NNTP server. Jnos crached right away. After a distro update of my linux version from “Stretch” to “Buster” all went fine.
# NNTP server/client
nntp profile fullname"Niels PD9Q"
nntp profile host jnos.packet-radio.nl
nntp profile organ"Amateur Radio"
nntp profile reply firstname.lastname@example.org
nntp profile user pd9q
nntp access off
nntp lzw on
Fist create newsgroups on the Jnos prompt
jnos>nntp create ng.bpqy
nntp create <news.group.name> [y|n]
Updates the /spool/news/active file, which must have an entry for each news group you wish to receive. Choose y to permit posting to this group, or n to deny posting. y is assumed if nothing is specified. The /spool/news/pointer file is also updated with the path to the directory which will contain the articles. Articles will be stored as separate files, named by an integer corresponding to their arrival order.
The NNTPS software includes a mail-to-news feature, such that email with a To: address that begins with “!” is passed to the NNTPS module. The remainder of the To: address is interpreted as a newsgroup name, with the name truncated at the first occurrence of one of “%@.,/”, and with “!” translated to “.” and “+” to “,”. An alias is usually used to provide this special name. For example, to route all NLD bulletins to both the NLD area, and the NG.NLD newsgroup, use the alias:
My alias file looks like this
The NNTPS software includes a news-to-mail feature, such that news articles can be emailed to local or remote destinations after they are processed by nntp. This would allow, for example, emailing to a public area, so that BBS users too could read news articles. JNOS must be compiled with NNTPS and NEWS_TO_MAIL #define’d and a file /spool/news/gateway must exist to define the mapping from a newsgroup to an SMTP To: address. Each non-comment line in the gateway file must begin with a newsgroup name (starnames OK), followed by spaces or tabs, followed by the email To: address.
Expire time of bulletins or newsgroup messages.
# bulletins received from AX25 network
I’m using Thunderbird to read and post messages as bulletin and newsgroup mail.
For the Raspberry Pi users among us, Maiko has found a solution for the Colors in Jnos and the NNTP server and probably even more stability issues.
For a long time we had to miss the colors, but I immediately imagine myself back in the 90s.
JNOS is doing strange things on PI platforms. Because gcc in the ARM processors are forcing CHAR variables to be UNSIGNED, not SIGNED!
UntilIfindabetter solution(longterm),you must add:
Maiko has been busy again to make some adjustments in Jnos. A friend of mine had asked if it was possible to save a Most Heard list. A few days later it was already done. Fantastic. It is also possible to leave the file ftpusers and use hashed passwords.
In the previous post about Direwolf and jnos i use Direwolf-1.3 and does not know about the SERIALKISS port.
John WQ6N point it out to me… Tnx John WQ6N. Nice one. Read the previous post.
So maybe I wrote that script for nothing. This is working pretty simple 🙂
In Direwolf 1.5-beta is it possible to use SERIALKISS to connect com to com.
I have try to use a PTY pair created with socat.
I use conspy to look at the output of Direwolf. apt-get install conspy
Use it just like this “conspy 3” The number 3 stands for the tty were Direwolf is running on /dev/tty3.
Hit the escape button a couple of times to exit.
040:6e6b65642077697468206f7468657273nked with others
Ok that is working quit well.
I start Direwolf with the option “-d kn” So you can look at the kiss communication between Direwolf and Jnos.
Some text out of the User-Guide.pdf.
“Up to 3 concurrent TCP KISS client applications are allowed at the same time.
You can raise this limit by increasing the value of MAX_NET_CLIENTS, in source file kissnet.c and recompiling.”
Whoooo thats nice up to 3 (and more) applications can connect to Direwolf on the KISSPORT.
And there is also the AGW and the SERIALKISS port. Men where do I start.
John WQ6N has found something that is useful. He use a Legacy BSD pseudo pair.
There are no Legacy BSD pseudo pairs in Linux any more. But it is possible to create some.
Change line from:
(Where10isthe number of pty legacy devices you require.)
Thiscreated10ptypX/ttypX terminal pairs.
After editing the grub file run the command “update-grub” and reboot.
So now it`s time to set Direwolf and Jnos to use the pty Legacy devices.
The issue here isyou don't know what slave device you will get, it could
change each time you run kissattach, there may be no consistent device name
for you to depend on when running 'attach asy' in the JNOS autoexec.nos.
Now in JNOS (autoexec.nos), suppose we have this entry below :
attach asy ptmx_radio - ax25 ax0 4096 256 9600
I have added a feature where if the 3rd argument starts with 'ptmx_',then
JNOS will look foracorresponding *.cfg file,andextract the slave device
name from it,andthenattach using that instead of the original argument.
This is some monitor output of Direwolf.
Dire Wolf version 1.3
Reading config file /direwolf/direwolf.conf
Audio device for both receive and transmit: plughw:0,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, E+, 44100 sample rate.
Ready to accept AGW client application 0 on port 8000 …
Use -p command line option to enable KISS pseudo terminal.
Ready to accept KISS client application on port 8001 …