Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Derick Anderson" <danderson@vikus.com>
To: "Harrison, James" <james.harrison@americancolor.com>
Cc: netfilter@lists.netfilter.org
Subject: RE: Troubleshooting Netfilter Firewall (performance issues)
Date: Fri, 4 Nov 2005 09:42:29 -0500	[thread overview]
Message-ID: <FAC4E024BF776842876169173CE2F0132950@mailbox.vikus.com> (raw)

 

> -----Original Message-----
> From: Harrison, James [mailto:james.harrison@americancolor.com] 
> Sent: Thursday, November 03, 2005 1:24 PM
> To: Derick Anderson
> Cc: netfilter@lists.netfilter.org
> Subject: RE: Troubleshooting Netfilter Firewall (performance issues)
> 
> On Thu, 2005-11-03 at 12:55 -0500, Derick Anderson wrote:
> [snip]
> 
> > 
> > If I were you I would monitor top during a large transfer 
> and maybe do 
> > an ethereal dump as well. If your two endpoint machines are both on 
> > Gbit LAN and your firewall is 100Mbit (on a 100/1000 switch) then 
> > perhaps your firewall NICs are getting overloaded. Every 
> night at my 
> > company all the servers (Gbit) back up to a local machine 
> (100Mbit). 
> > They each have their time window for backing up but it's common for 
> > Nagios to report an "UNKNOWN" status for the backup server in the 
> > early morning hours. Of course that could simply be the poor little 
> > backup server not having the time to reply...
> > 
> > Derick Anderson
> 
> According to netstat -i I shouldn't be having issues with 
> overloading the interfaces. (TX-ERR on eth0 and eth1 are 
> static and have not
> incremented) I have 2/100MB and 2/1000MB interfaces.
> 
> Iface   MTU Met   RX-OK RX-ERR RX-DRP RX-OVR   TX-OK TX-ERR 
> TX-DRP TX-OVR Flg
> eth0   1500 0  50757220      0      0      050703586    523   
>    0      0 BMRU
> eth0:  1500 0       - no statistics available -               
>          BMRU
> eth1   1500 0  339989009      0      0      0397086634   3381 
>      0      0 BMRU
> eth1:  1500 0       - no statistics available -               
>          BMRU
> eth2   1500 0  409181861      0      0      0344550753      0 
>      0      0 BMRU
> eth3   1500 0  11352902      0      0      015003672      0   
>    0      0 BMRU
> eth3:  1500 0       - no statistics available -               
>          BMRU
> 
> It is running on the Devil Linux distro.
> 
> --
> James Harrison RHCE
> Manager, Information Security
> AIM: harrijh1

Unless Devil Linux has messed with your TCP/IP options in the kernel,
then I think it's time to look at the firewall. If you have an
abnormally high number of rules, this could be an issue, or if you're
rate-limiting anything...

Derick Anderson


             reply	other threads:[~2005-11-04 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-04 14:42 Derick Anderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-11-03 17:55 Troubleshooting Netfilter Firewall (performance issues) Derick Anderson
2005-11-03 18:24 ` Harrison, James
2005-11-03 17:28 Harrison, James

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=FAC4E024BF776842876169173CE2F0132950@mailbox.vikus.com \
    --to=danderson@vikus.com \
    --cc=james.harrison@americancolor.com \
    --cc=netfilter@lists.netfilter.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