From: Willy Tarreau <w@1wt.eu>
To: "Øyvind Vågen Jægtnes" <lorrides@gmail.com>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Routing 600+ vlan's via linux problems (looks like arp problems)
Date: Fri, 4 May 2007 00:23:34 +0200 [thread overview]
Message-ID: <20070503222334.GD943@1wt.eu> (raw)
In-Reply-To: <d20c3b7d0705031412y11f18288t321c097aaad4b38b@mail.gmail.com>
On Thu, May 03, 2007 at 11:12:09PM +0200, Øyvind Vågen Jægtnes wrote:
> 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?
I don't think it could cause a problem, but network people will surely
correct me if I'm wrong.
> 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 ;)
Huhhh! Please tell us exactly what make and model of ROUTER you are using
which embeds a HARD DRIVE, so that we recall never to buy that ! Having
seen uptimes of 5 years on moderately big access routers, I would have
find it awful to see them die multiple times in that timeframe because
of a crappy IDE drive inside !
> I have been looking at arpd, but i quickly discarded it as an option
> since its marked both experimental and obsolete ;)
I never dared to try it either, and since 512 has always been enough
for me, anything above is unknown area to me :-)
Regards,
Willy
next prev parent reply other threads:[~2007-05-03 22:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-03 20:25 Routing 600+ vlan's via linux problems (looks like arp problems) Ø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
2007-05-03 22:23 ` Willy Tarreau [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=20070503222334.GD943@1wt.eu \
--to=w@1wt.eu \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lorrides@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