From christopher.maness at gmail.com Thu Feb 1 13:32:13 2024 From: christopher.maness at gmail.com (Chris Maness) Date: Thu, 1 Feb 2024 10:32:13 -0800 Subject: [nos-bbs] Slow/Clunky NETROM on JNOS Message-ID: (* Cross posted from the JNOS BBS flood area *). I am not sure where most of you guys are lurking. I am wondering what the best NETROM parameters for an efficient netrom link over a 1k2bps link. My current setup is a but clunky in comparison to a UROnode->BPQ32 link that I have on the same port. I the link efficiency is decent ~80%, but a straight AX.25 -> AX.25 link is much better. When I use NETROM->NETROM with the native linux stack and say BPQ32, cannot tell the difference between that and a plain vanilla AX.25 link, but with JNOS this process is slow. ENTER = continue, A = Abort, N = Next, C = remove paging --> Here is the pertinent settings for my autoexec.nos file: NETROM/AX.25 Settings attach asy ttyq5 - ax25 vhf 4096 255 9600 # # Attach to the kernel multiplex AX.25 port # #attach baycom vhf 255 ax0 # ifconfig vhf description "vhf - 1200 baud port" # param vhf 2 63 param vhf 3 1 param vhf 5 1 # param vhf TxDelay 25 ENTER = continue, A = Abort, N = Next, C = remove paging -->c ################## start netrom attach netrom # Place your CALLSIGN and ALIAS (NetROM Nodename) here: # netrom alias NTSNOS # *MUST* be set the SAME as the 'ax25 alias' netrom call K6HTN-3 # # # Only enable these if using BPQ AXUDP Internet links if they have # been uncommented, above. This sets the initial routing 'weight' value. ##netrom interface EATON 192 ##netrom interface SAGINW 192 ##netrom interface GRNVLE 192 # # netrom interface axi0 203 netrom bcnodes axi0 netrom bcpoll axi0 # netrom interface lb0 203 netrom bcnodes lb0 netrom bcpoll lb0 # netrom interface vhf 192 netrom bcnodes vhf netrom bcpoll vhf # pause 5 # mode netrom vc # defauilt datagram netrom minquality 161 # default 10 #netrom acktime 3000 # default 3000 #netrom choketime 180000 # default 180000 # #netrom derate on # default on netrom hidden off # default on #netrom promiscuous off # default off # #netrom retries 10 # default 10 #netrom ttl 10 # default 10 #netrom window 4 # default 4 #netrom tdisc 0 # default 0 # netrom timertype linear # default exponential netrom irtt 15000 # default 45000 #netrom nodetimer 1800 # default 1800 #netrom obsotimer 2100 # default 2100 #netrom qlimit 2048 # default 2048 # netrom g8bpq on # default off # netrom route sort alias # remark "***** NetROM configured *****" 73 de Chris KQ6UP -- Thanks, Chris Maness From christopher.maness at gmail.com Thu Feb 1 19:04:19 2024 From: christopher.maness at gmail.com (Chris Maness) Date: Thu, 1 Feb 2024 16:04:19 -0800 Subject: [nos-bbs] JNOS and ax0? Message-ID: Strange, I did not receive your response but the archive did. I am wondering if google is bouncing replies to xNOS. Anyhow, yes I can attach the ax0 port with said command, and it works great for AX.25, but NETROM does not seem to play well with it. net2kiss seems to work better with NETROM as it provides JNOS a KISS port to work with. The reason this is useful is that I am also doing LinFBB and UROnode on the same system, and those applications need access to the Linux AX.25 stack as well. -Chris KQ6UP ############## It does look like it, it specifically mentions Linux AX.25 network devices, it is just confusing that it uses the baycom hardware type and only talks about soundmodem, offcourse all the other devices like serial and usb kiss tncs are directly supported by JNOS and people preferred to keep the ports seperated and link the 2 sides with a tunnel so it is not a common usecase but still valid. 73 Andre PE1RDW Op 19-01-2024 om 16:17 schreef Chris Maness: > Does the following passage from: > > https://www.langelaar.net/jnos2/documents/kb8ojh-packet/jnos.html > > Mean that I can also attach to ax0, or does this only account for sm0? > > I would like to share my KISS port with the linux AX.25 stack. > > -TNX Chris KQ6UP > > ######################################################### > > Kernel AX.25 devices > > As of JNOS version 2.0g, JNOS supports Linux AX.25 network devices > directly, by way of the baycom hardware type. In order to use it, > change the #undef BAYCOM_SER_FDX line in config.h to read: > > #define BAYCOM_SER_FDX > > Then recompile JNOS, and attach the soundmodem device in your autoexec.nos with: > > attach baycom vhf 256 sm0 > > If your soundmodem network device is named something other than sm0, > change the last parameter accordingly. > > The JNOS documentation on this can be found on langelaar.net. > > Many thanks to Maiko Langelaar himself for pointing this out. > > _______________________________________________ > nos-bbs mailing list > nos-bbs at lists.tapr.org > http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org -- Thanks, Chris Maness