linux-kernel - Re: Routing 600+ vlan's via linux problems (looks like arp problems)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 3 May 2007 23:12:09 +0200
From:	"Øyvind Vågen Jægtnes" <lorrides@...il.com>
To:	"Jan Engelhardt" <jengelh@...ux01.gwdg.de>
Cc:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: Routing 600+ vlan's via linux problems (looks like arp problems)

On 5/3/07, Jan Engelhardt <jengelh@...ux01.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@...il.com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/