All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Øyvind Vågen Jægtnes" <lorrides@gmail.com>
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 22:55:23 +0200	[thread overview]
Message-ID: <20070503205523.GC943@1wt.eu> (raw)
In-Reply-To: <20070503205341.GB943@1wt.eu>

On Thu, May 03, 2007 at 10:53:41PM +0200, Willy Tarreau wrote:
> On Thu, May 03, 2007 at 10:25:48PM +0200, Øyvind Vågen Jægtnes wrote:
> > Hi,
> > 
> > We have a one gigabit internet connection that is normally
> > routed by a hardware juniper router. The drive in this is down
> > and we need to use a linux machine (Pentium D 3 ghz) as a
> > temporary router.
> > Now setting up all the 600 vlans and assigning ip addresses
> > is no problem. We have testet all by using a laptop, setting up
> > 600 vlan interfaces on this and running dhcpclient on all.
> > This worked just fine, all the interfaces got address.
> > 
> > Now for the real setup.
> > We closed the mac of the juniper to the network card that
> > would be connected to the internal LAN, set up the interfaces,
> > and swapped cables. This worked fine for approximately 100
> > of the computers that are connected, but the rest would not
> > get IP. The connected 100 computers were routed just fine.
> > 
> > What we think the problem is, is that the arp cache on the
> > linux router seems strange. It can resolve the MAC for the
> > 100 clients that actually got through.
> > 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
                                ^ insert /default/ here.

> set it as high as gc_thresh2 (512 for me), and I don't know what
> happens above.

Willy


  reply	other threads:[~2007-05-03 20:55 UTC|newest]

Thread overview: 20+ 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 [this message]
2007-05-03 20:55   ` Jan Engelhardt
2007-05-03 21:12     ` Øyvind Vågen Jægtnes
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  0:01     ` jamal
  -- 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=20070503205523.GC943@1wt.eu \
    --to=w@1wt.eu \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.