netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: iptables bug (was: Re: 2.6.12-mm1)
Date: Mon, 20 Jun 2005 15:34:45 -0700	[thread overview]
Message-ID: <20050620153445.5daaed4e.akpm@osdl.org> (raw)
In-Reply-To: <1119305756l.1344l.0l@werewolf.able.es>

"J.A. Magallon" <jamagallon@able.es> wrote:
>
> 
> On 06.20, Andrew Morton wrote:
> > 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.12/2.6.12-mm1/
> > 
> > 
> > - Someone broke /proc/device-tree on ppc64.  It's being looked into.
> > 
> > - Nothing particularly special here - various fixes and updates.
> > 
> 
> Are there any known problems with iptables ?

Let's cc the appropriate list and find out ;)

> I see strange things.
> When I use bittorrent (azureus or bittorrent-gui), at the same time as
> iptables (for nat and internet access for my ibook), when I stop a download
> or exit from one of this apps my external network goes down. 
> I have tried the same without iptables loaded and it works fine.
> 
> If someone has any idea about this, I could give more details.
> 
> Kernel: every -mm since time ago.
> External net: 1Mb cable through 3c59x, dhcp
> Internal net: e1000
> Iptables setup:
> # Generated by iptables-save v1.2.9 on Thu Mar  3 23:41:02 2005
> *nat
> :PREROUTING ACCEPT [2:156]
> :POSTROUTING ACCEPT [0:0]
> :OUTPUT ACCEPT [0:0]
> [0:0] -A POSTROUTING -o eth0 -j MASQUERADE 
> COMMIT
> # Completed on Thu Mar  3 23:41:02 2005
> # Generated by iptables-save v1.2.9 on Thu Mar  3 23:41:02 2005
> *filter
> :INPUT ACCEPT [6:468]
> :FORWARD DROP [0:0]
> :OUTPUT ACCEPT [0:0]
> [0:0] -A FORWARD -i eth0 -o eth1 -m state --state RELATED,ESTABLISHED -j ACCEPT 
> [0:0] -A FORWARD -i eth1 -o eth0 -j ACCEPT 
> [0:0] -A FORWARD -i eth0 -o eth2 -m state --state RELATED,ESTABLISHED -j ACCEPT 
> [0:0] -A FORWARD -i eth2 -o eth0 -j ACCEPT 
> [0:0] -A FORWARD -i eth0 -o eth3 -m state --state RELATED,ESTABLISHED -j ACCEPT 
> [0:0] -A FORWARD -i eth3 -o eth0 -j ACCEPT 
> COMMIT
> # Completed on Thu Mar  3 23:41:02 2005
> 
> eth's:
> alias eth0 3c59x
> alias eth1 e1000
> alias eth2 ne2k-pci
> alias eth3 eth1394
> 
> eth2 and eth3 are currently down, not even the module is loaded.
> 
> Any idea ?
> 
> --
> J.A. Magallon <jamagallon()able!es>     \               Software is like sex:
> werewolf!able!es                         \         It's better when it's free
> Mandriva Linux release 2006.0 (Cooker) for i586
> Linux 2.6.12-jam1 (gcc 4.0.1 (4.0.1-0.2mdk for Mandriva Linux release 2006.0))
> 

       reply	other threads:[~2005-06-20 22:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050619233029.45dd66b8.akpm@osdl.org>
     [not found] ` <1119305756l.1344l.0l@werewolf.able.es>
2005-06-20 22:34   ` Andrew Morton [this message]
2005-06-20 23:39     ` iptables bug Patrick McHardy
2005-06-21 19:21       ` Stephen Jones
2005-06-22  1:52         ` Patrick McHardy

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=20050620153445.5daaed4e.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=jamagallon@able.es \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).