[nos-bbs] Re: nos-bbs Digest, Vol 36, Issue 1

[JJ]

nos-bbs-request at lists.tapr.org wrote:

>Send nos-bbs mailing list submissions to
>	nos-bbs at lists.tapr.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>or, via email, send a message with subject or body 'help' to
>	nos-bbs-request at lists.tapr.org
>
>You can reach the person managing the list at
>	nos-bbs-owner at lists.tapr.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of nos-bbs digest..."
>
>
>Today's Topics:
>
>   1. Re: JNOS *live* page (Maiko Langelaar (ve4klm))
>
>
>----------------------------------------------------------------------
>
>Message: 1
>Date: Tue, 10 Jul 2007 13:39:54 -0500 (CDT)
>From: "Maiko Langelaar (ve4klm)" <maiko at pcs.mb.ca>
>Subject: [nos-bbs] Re: JNOS *live* page
>To: nos-bbs at lists.tapr.org
>Message-ID:
>	<Pine.LNX.4.61.0707101330240.12740 at jedi.physics.umanitoba.ca>
>Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
>
>Greetings all,
>
>I figure I got about 30+ logins through the java telnet client which was
>made available on the JNOS live page. Thank you to everyone who tried it
>out. It's nice to see there are still some JNOS users out there. Most of
>the logins no doubt came from people on this mailing list, so I think it
>is safe to say there are even a few more users then that out there ...
>
>  
>
>>http://www.langelaar.net/projects/jnos2/live
>>    
>>
>
>Maiko Langelaar / VE4KLM
>
>
>
>------------------------------
>
>_______________________________________________
>nos-bbs mailing list
>nos-bbs at lists.tapr.org
>https://lists.tapr.org/cgi-bin/mailman/listinfo/nos-bbs
>
>
>End of nos-bbs Digest, Vol 36, Issue 1
>**************************************
>
>  
>
Yep, still love xNOS...off-topic, I'm having an ax25 fragmentation 
problem, and it looks like I'm
not the only one...ka0mos and ve1ama both are fragmenting too at the 
ax25 and netrom level...I can
only give the params I need for mine...I run 2 ports (for now) with a 
Kam...my HF port needs to have
paclen 64 or so, while my VHF port needs 128...now, things seem to be ok 
until I attach netrom
to the hf port...it then forces my VHF port netrom to use the HF paclen 
(64), and my resulting
attempts to solve that have only met with fragmentation...I sure hope I 
don't have to set a system-wide
MTU of 64, hi hi! The problem is also apparent using vc on vhf...the 
first I-frame goes fine, then I
see the dreaded "Remain" word in the header of the second packet, and 
the local node just silently
drops it, and that's where it sits until it times out....(ax25)...the 
result seen by the end-user is that
only one packet gets thru...then connection sits udle till 
timeout....anybody have any ideas about
how to solve?(besides DE-taching netrom from HF port, hi)
Cheers all...and good to see activity..
73 de John

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.tapr.org/pipermail/nos-bbs_lists.tapr.org/attachments/20070711/8ffe59b7/attachment.html>