Direwolf and Jnos (review)

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.

Here is the output of Direwolf

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

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.

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.

Direwolf and Jnos

The scipt…. Small but work quit well

This is what i found in the change.log of Jnos

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 …

Connected to KISS client application …

[0L] PD2LT-2>NODES:<0xfe>
[0L] PD2LT-9>NODES:<0xff>LAPNOS
[0L] PD2LT-9>NODES:<0xfe>LAPNOS

PD2LT-2 audio level = 14(3/3) [NONE] |||||||__
[0.3] PD2LT-2>NODES:<0xfe>

PD2LT-9 audio level = 14(3/3) [NONE] ||||||||_
[0.3] PD2LT-9>NODES:<0xff>LAPNOS

Jnos link local

Setup a local link in jnos to uronode.

 

Jnos rewrite

Setup Jnos rewrite

 

Jnos axip link

Setup Jnos axip link

 

Jnos ampr gateway

Setup Jnos ampr gateway

 

Jnos network interface

Setup a Jnos network Interface

 

Tcp Access Control Jnos

Jnos werkt met een access control list. Hier onder een klein voorbeeld wat je zo er allemaal in kan zetten. Er staan dingen dubbel in, het gaat hier om een voorbeeld wat allemaal mogelijk is.

 

Xnet axudp link Jnos

De axudp link van xnet naar jnos heeft voor heel wat problemen gezorgd.
Maar hij is up and running… Hier onder de uitleg.

In de regel “attach axudp xnet 256 192.168.1.112” (jnos) zit het geheim.
Deze moet dus “niet” verwijzen naar het ip-adres van xnet zoals je
hebt aangegeven in ip.net bij myip, maar naar het ip-adres van Linux zelf.
Dus het ip-adres van (b.v) eth0

Autoexec.nos (Jnos)

Eth0 (Linux)

Ip.net (xnet)

Autoboot.net (xnet)

 

Voorbeeld forward JNOS/BPQ/LinFBB

Hier onder een aantal voorbeelden hoe de configuratie van de forward in verschillende systemen in zijn werk gaat.

Thanks in particular to Bob (VE3TOK) and Gus (I0OJJ) for example configs !

Copyright ©  http://www.langelaar.net/jnos2/