mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Øyvind Vågen Jægtnes" <lorrides@gmail.com>
To: "Jan Engelhardt" <jengelh@linux01.gwdg.de>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: Routing 600+ vlan's via linux problems (looks like arp problems)
Date: Thu, 3 May 2007 23:12:09 +0200	[thread overview]
Message-ID: <d20c3b7d0705031412y11f18288t321c097aaad4b38b@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0705032255080.18504@yvahk01.tjqt.qr>

On 5/3/07, Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
>
> On May 3 2007 22:53, Willy Tarreau wrote:
> >> For the rest all we see in the arp cache is (incomplete)
> >
> >I suspect that your arp cache is full (128 entries by default).
> >Check /proc/sys/net/ipv4/neigh/gc_thresh1 (128 for me). You can
> >set it as high as gc_thresh2 (512 for me), and I don't know what
> >happens above.
>
> Above, you will perhaps need the not-so-elegant userspace arpd :-/

Yes, i was suspecting that the arp cache got full, but i will try
increasing it :)
Would there be any huge bugs if i change these lines in arp.c:

        .gc_thresh1 =   128,
        .gc_thresh2 =   512,

to

        .gc_thresh1 =   700,
        .gc_thresh2 =   700,

under the definition for struct arp_tbl?
This setup will only run for about 1-2 hours while we fix the hardware
router (it is running now, but only on a backup flash card solution.
the harddrive in it died ;)

I have been looking at arpd, but i quickly discarded it as an option
since its marked both experimental and obsolete ;)

regards
Øyvind Vågen Jægtnes
+47 96 22 03 08
lorrides@gmail.com

  reply	other threads:[~2007-05-03 21:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-03 20:25 Øyvind Vågen Jægtnes
2007-05-03 20:34 ` Jan Engelhardt
2007-05-03 20:53 ` Willy Tarreau
2007-05-03 20:55   ` Willy Tarreau
2007-05-03 20:55   ` Jan Engelhardt
2007-05-03 21:12     ` Øyvind Vågen Jægtnes [this message]
2007-05-03 22:23       ` Willy Tarreau
2007-05-03 22:50         ` Jan Engelhardt
2007-05-04  0:11           ` Willy Tarreau
2007-05-04  7:53             ` Jan Engelhardt
2007-05-04 20:27               ` Willy Tarreau
2007-05-04  3:48         ` Øyvind Vågen Jægtnes
2007-05-04  5:30           ` Willy Tarreau
2007-05-04  7:08           ` Miquel van Smoorenburg
2007-05-04  8:28             ` Andi Kleen
2007-05-04  8:05           ` Jan Engelhardt
2007-05-03 20:53 ` Sam Ravnborg
2007-05-03 21:38   ` Stephen Hemminger
2007-05-04 14:02 Paul Slootman

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=d20c3b7d0705031412y11f18288t321c097aaad4b38b@mail.gmail.com \
    --to=lorrides@gmail.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®