public inbox for linux-hams@vger.kernel.org
 help / color / mirror / Atom feed
From: f6bvp <f6bvp@free.fr>
To: C Schuman <k4gbb1@embarqmail.com>
Cc: Ray Wells <vk2tv@exemail.com.au>, Bob Tenty <bobtenty@gmail.com>,
	Jerry DeLong <KD4YAL@tampabay.rr.com>,
	List for LINUX ROSE/FPAC network switch <fpac@f6fbb.org>,
	linux-hams <linux-hams@vger.kernel.org>
Subject: Re: Patch improving ROSE routing
Date: Sat, 04 Dec 2010 18:49:53 +0100	[thread overview]
Message-ID: <4CFA7F41.7070505@free.fr> (raw)
In-Reply-To: <4CF6B200.1060509@embarqmail.com>

Hi,

I am presently hunting a bug in fpacwpd that makes this server crash 
regularly.
I think I am not far from the goal as I found a SIGPIPE signal that is 
occuring when
fpacwpd cannot reach a destination node. This signal was not handled by 
the server
and this could explain why WP data base is not available from time to 
time inside
fpacnode showing -1 instead of the number of nodes and fpacnode not 
being able to
connect a remote node.
Continuous testing are being performed locally.
If the results are positive, I will soon release fpac327.14-pre30 that 
could become
fpac327.14 after validation by you all.

On my list are a few other bugs in Linux rose module, ax25ipd, FPAC and 
BBS softwares.
This number is decreasing regularly, with some valuable help from Cathryn.

I recently corrected a bug in "nestat", a usefull tool from net-tools. 
When I patched it
to include ROSE handling, I made a small error that made it crash from 
time to time.
You can download netstat from CVS and apply the new patch as explained 
here :

http://rose.fpac.free.fr/MINI-HOWTO/#s103

73 de Bernard, f6bvp


Le 01/12/2010 21:37, C Schuman a écrit :
> Bernard
> Either the AxUDP ports are working better or the ROSE patch has made a 
> *HUGE* improvement.
> I installed the patch on approx half of our Servers.
> In Every case connectivity has improved and connections go thru at 
> warp speed.
>
> <<Charley>>
>      k4gbb
>

--
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2010-12-04 17:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-25 22:08 Patch improving ROSE routing f6bvp
2010-12-01 20:37 ` C Schuman
2010-12-02 10:38   ` f6bvp
2010-12-04 17:49   ` f6bvp [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CFA7F41.7070505@free.fr \
    --to=f6bvp@free.fr \
    --cc=KD4YAL@tampabay.rr.com \
    --cc=bobtenty@gmail.com \
    --cc=fpac@f6fbb.org \
    --cc=k4gbb1@embarqmail.com \
    --cc=linux-hams@vger.kernel.org \
    --cc=vk2tv@exemail.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox