Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@riverviewtech.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] neighbor table overflow
Date: Tue, 23 Oct 2007 21:04:43 +0000	[thread overview]
Message-ID: <471E61EB.4080602@riverviewtech.net> (raw)
In-Reply-To: <200710230146.27081.peet@altlinux.org>

On 10/23/07 16:10, Marco C. Coelho wrote:
> This box is doing a lot.  It terminates 1000 PPPoE connections, provides 
> traffic shaping using TC/HTB, authenticates all users via Radius.  It 
> also runs OSPF routing for the internal network.  Looking at a simple 
> route output I see all the PPP connections coming through the box, and 
> due to the OSPF I also see the rest of my network announcements.  The 
> only strange things are:

That's just a few things to do on one box.  How well is it handling it 
if I can ask (aside from the problem that you are working on)?

> 1.  The last man working on this box had mistakenly edited the hosts 
> file and added the machine name and complete domain name to the local 
> host 127.0.0.1 name.  It should only be pointed to the eth0 interface.   
> I have changed this.

Dough!

> 2.  The route output is making an announcement
> 
>    64.0.0.0        argontech.net   255.0.0.0       UG    20     0        
> 0 eth0
> 
> My public IP space is a /20 within that space, not the whole Class A.  I 
> have not found which box is announcing this within my network yet.

I would think that you could extract that information from OSPF, or at 
least the system that is advertising and work backwards until you find 
the ultimate culprit.



Grant. . . .
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2007-10-23 21:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-22 21:46 [LARTC] neighbor table overflow Peter V. Saveliev
2007-10-22 21:46 ` Marco C. Coelho
2007-10-22 22:35 ` Grant Taylor
2007-10-23 11:56 ` Alexandru Dragoi
2007-10-23 20:32 ` Grant Taylor
2007-10-23 20:43 ` Jeff Welling
2007-10-23 21:04 ` Grant Taylor [this message]
2007-10-23 21:10 ` Marco C. Coelho
2007-10-23 21:23 ` Grant Taylor
2007-10-23 21:27 ` Marco C. Coelho
2007-10-24 10:19 ` Alexandru Dragoi
2007-10-24 15:19 ` Marco C. Coelho
2007-10-24 16:06 ` Alexandru Dragoi
2007-10-25 15:08 ` Marco C. Coelho
2007-10-25 16:30 ` Alexandru Dragoi
2007-11-19 22:36 ` Marco C. Coelho
2007-11-19 23:15 ` darko
2007-12-07 17:17 ` Marco C. Coelho

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=471E61EB.4080602@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=lartc@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