All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cian Masterson <cianm@klasonline.com>
To: netfilter@lists.netfilter.org
Subject: Kernel panic when routing large pings on an XScale (IXP425).
Date: Mon, 30 May 2005 15:26:02 +0100	[thread overview]
Message-ID: <429B227A.1000306@klasonline.com> (raw)

Hi,

I am using iptables on an Intel ixp425 (XScale/ARM processor) and am 
finding that I get a kernel panic when I try to send large (65k) pings 
to the board, or route them across the board.  Iptables is not 
configured with any rules (see below) so all traffic is passed through 
the board.  I don't see any problems with regular pings/FTP 
transfers/etc and I have left a chain of boards passing traffic over the 
weekend with no problems, however the board will always experience a 
kernel panic within 30 seconds of me initiating large pings.  I have 
applied the ixp425_eth_1_1_update_nf_bridge.patch patch that I got from 
Intel 
(http://developer.intel.com/design/network/products/npfamily/ixp400_osc.htm) 
to no avail.  I am running version 1.4 of Intel's software but before 
anyone suggests it upgrading to 1.5 is simply not an option at this 
point, unfortunately.

If I don't insert the iptables modules the board passes large pings 
without any problems so it is definitely a ixp425_eth.o/netfilter 
interaction problem.  I've downloaded and searched through the archives 
for this board and have found a posting from Rob Ranslam of Intel 
stating that if I also have ebtables then I'll need an extra patch from 
sourceforge, however I *don't* have ebtables so I can't see how that 
patch would be needed in my case.  The documentation for the Intel patch 
seems to relate to bridging, and I've seen posts from others who say 
routing works but bridging doesn't but my problem definitely relates to 
routing.  Has anyone seen a problem like this and/or can anyone offer 
any ideas as to where I should be looking for the problem as I'm a 
netfilter newbie?  Thanks.

Slan,
Cian

PS:  Below is the output of iptables --list for reference;
  root@(none):~# iptables 
--list                                                 
  Chain INPUT (policy 
ACCEPT)                                                    
  target     prot opt source               
destination                           
   
                                                                              

  Chain FORWARD (policy 
ACCEPT)                                                  
  target     prot opt source               
destination                           
   
                                                                              

  Chain OUTPUT (policy 
ACCEPT)                                                   
  target     prot opt source               
destination                           
  root@(none):~#




             reply	other threads:[~2005-05-30 14:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-30 14:26 Cian Masterson [this message]
2005-05-30 17:46 ` Kernel panic when routing large pings on an XScale (IXP425) Gary W. Smith
2005-05-31 13:08   ` Eduardo Spremolla
  -- strict thread matches above, loose matches on Subject: below --
2005-05-31 14:51 Gary W. Smith

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=429B227A.1000306@klasonline.com \
    --to=cianm@klasonline.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 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.