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: w4bgh@verizon.net, Ray Wells <vk2tv@exemail.com.au>,
	Jerry DeLong <KD4YAL@tampabay.rr.com>,
	Bob Tenty <bobtenty@gmail.com>, Chuck Hast <wchast@gmail.com>,
	Klaus VE3KR <ve3kr@yahoo.ca>,
	"Lisandro M. Arends" <p43l@arubanet.com>,
	linux-hams <linux-hams@vger.kernel.org>
Subject: Re: Patch improving ROSE routing
Date: Thu, 02 Dec 2010 11:38:40 +0100	[thread overview]
Message-ID: <4CF77730.3090101@free.fr> (raw)
In-Reply-To: <4CF6B200.1060509@embarqmail.com>

Hi Charley,

I made a few connect request through the ROSE FPAC network you modified 
and agree
that it works faster and much more efficiently.

The good and completely unexpected surprise is that F6BVP node is now 
connected
directly to KP4DJT ! Although I have no explanation, I am very glad.

I encourage you to add, as I did in KP4DJT routing table, default 
generic routes with
four digits DNICs in all your nodes routing tables.
These DNIC routes should be populated with three best nodes toward the 
final goal.

Considering the results I am encouraged to commit the patch right now 
for it to be
included as soon as possible in next kernel release and appear in due 
time in Linux distros.

Thanks for your help.

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

  reply	other threads:[~2010-12-02 10:38 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 [this message]
2010-12-04 17:49   ` f6bvp

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=4CF77730.3090101@free.fr \
    --to=f6bvp@free.fr \
    --cc=KD4YAL@tampabay.rr.com \
    --cc=bobtenty@gmail.com \
    --cc=k4gbb1@embarqmail.com \
    --cc=linux-hams@vger.kernel.org \
    --cc=p43l@arubanet.com \
    --cc=ve3kr@yahoo.ca \
    --cc=vk2tv@exemail.com.au \
    --cc=w4bgh@verizon.net \
    --cc=wchast@gmail.com \
    /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