All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair Tonner <Alistair@nerdnet.ca>
To: Peter Choynowski <pkc@scs.carleton.ca>, netfilter@lists.netfilter.org
Subject: Re: Problem with PAT - HARD lock-up
Date: Wed, 5 Nov 2003 15:08:36 -0500	[thread overview]
Message-ID: <200311051508.36925.Alistair@nerdnet.ca> (raw)
In-Reply-To: <3FA92644.91C0E53D@scs.carleton.ca>

On November 5, 2003 11:33 am, Peter Choynowski wrote:
> I need some ideas how to debug a hard lock-up problem with PAT.
>
> The setup - my test setup consists of 2 hosts, one running PAT, the
> other running Apache.  Both hosts are RH 8.0 with 2.4.22, iptables
> v1.2.8, P4 with 1GB of ram. I am using a default route pointing to the
> PAT for the return traffic from the web server.  The PAT rules are:
>
>         iptables -t nat -F
>         iptables -F
>
>         iptables -P FORWARD DROP
>         iptables -A FORWARD -m state --state RELATED,ESTABLISHED -j
> ACCEPT
>
>         iptables -A FORWARD -i eth0 -o eth1 -p $proto --dport $port_numb
> -j ACCEPT
>         iptables -t nat -A PREROUTING -i eth0 -p $proto --dport
> $port_numb \
>           -j DNAT --to ${host_ip}:$port_numb
>
>
> Problem description - I am using wget from 2 or 3 outside hosts doing
> continuous gets of a 1Mb file from the web server - things work for
> about 5 to 40 min. after that that the PAT host locks up, the web server
> stays up.  Average transfer rate is about 60 Mbits/s.
>
> Actions taken - I have enabled SysRq, and other kernel debugging
> options, as well  added KDB code to the kernel, but when the lock-up
> happens neither can be invoked, there are no oops on the screen or logs
> of any kind - only reset button can bring it back.   I tried both 2.4.20
> and 2.4.22 with the same results.
>
> Any ideas ?

	I doubt (if Magic SysRq doesn't work) this will help much, but console over 
	serial port? 
	
	There are several kernel debuggng flags in 2.4.22 ... which do you have 
turned on other than SysRq? 

	You can turn on debugging in the iptables stuff in 
	/path/to/kernel/source/net/ipv4/netfilter/ip_tables.c
	there are three options in there that can be #defined and will 
	spew tons of info.
	

>
> Thx,
> Peter

-- 

	Alistair Tonner
	nerdnet.ca
	Senior Systems Analyst - RSS
	
     Any sufficiently advanced technology will have the appearance of magic.
	Lets get magical!


      reply	other threads:[~2003-11-05 20:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-05 16:33 Problem with PAT - HARD lock-up Peter Choynowski
2003-11-05 20:08 ` Alistair Tonner [this message]

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=200311051508.36925.Alistair@nerdnet.ca \
    --to=alistair@nerdnet.ca \
    --cc=netfilter@lists.netfilter.org \
    --cc=pkc@scs.carleton.ca \
    /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.