From: Andy Polyakov <appro@fy.chalmers.se>
To: Harald Welte <laforge@netfilter.org>,
coreteam@netfilter.org,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: [netfilter-core] linux-2.6.0-testX ipchains oops in NAT
Date: Thu, 23 Oct 2003 13:16:04 +0200 [thread overview]
Message-ID: <3F97B874.CB12C184@fy.chalmers.se> (raw)
In-Reply-To: 3F97A4C5.982725B0@fy.chalmers.se
[-- Attachment #1: Type: text/plain, Size: 815 bytes --]
> > > Question. Should I pursue the issue further?
> >
> > yes, please. Especially a means of reproduction without running
> > proprietary software (and thus being repruducable for me) would be very
> > helpful.
>
> Would eth0:1 be sufficient?
It's perfectly reproducible with eth0:1. In other words I
- take up eth0:1 with private ip address, e.g. 192.168.60.1 on computer
running 2.6 with 'ipchains -A forward -s 192.168.0.0/255.255.0.0 -d
0.0.0.0/0.0.0.0 -j MASQ';
- on another computer take up eth0:1 with e.g. 192.168.60.2 and 'route
add host some.host 192.168.60.1';
- on that other computer run attached script as './conn.pl some.host 80
2345';
- wait till port translation expires at first computer;
- run attached script as './conn.pl some.host 80 2345' once again;
- collect attached console.dump;
A.
[-- Attachment #2: conn.pl --]
[-- Type: application/x-perl, Size: 598 bytes --]
[-- Attachment #3: console.dump --]
[-- Type: text/plain, Size: 1824 bytes --]
Unable to handle kernel paging request at virtual address 00100108
printing eip:
e08787e1
*pde = 00000000
Oops: 0000 [#1]
CPU: 0
EIP: 0060:[<e08787e1>] Tainted: PF
EFLAGS: 00013203
EIP is at find_appropriate_src+0x3d/0xa0 [ipchains]
eax: e084dcf0 ebx: 00100100 ecx: dd3cdd44 edx: 0000059e
esi: 00000000 edi: dd3cdcd8 ebp: dd3cdc50 esp: dd3cdc40
ds: 007b es: 007b ss: 0068
Process X (pid: 1257, threadinfo=dd3cc000 task=dd3b5940)
Stack: dd3cdce8 dd3cdd08 dd3cdcd8 0000059e dd3cdc90 e0878a83 dd3cdcd8 dd3cdd44
dd3cdce8 c80e4ea4 dd3cdd08 e08817e0 dd3cdcd8 c80e4e2c c80e4e2c dd3cdc9c
e0876099 dd3cdcd8 c80e4e2c e0881580 dd3cdd18 e0878c2d dd3cdd08 dd3cdcd8
Call Trace:
[<e0878a83>] get_unique_tuple+0x33/0x190 [ipchains]
[<e0876099>] invert_tuplepr+0x1d/0x28 [ipchains]
[<e0878c2d>] ip_nat_setup_info+0x4d/0x2a0 [ipchains]
[<e0875ff3>] ip_conntrack_in+0x18f/0x218 [ipchains]
[<c02300c3>] __ip_route_output_key+0x23/0xe4
[<e08780b8>] gcc2_compiled.+0x168/0x1f0 [ipchains]
[<e0877735>] fw_in+0x1f9/0x228 [ipchains]
[<c0229f70>] nf_iterate+0x44/0xa4
[<c0232c44>] ip_forward_finish+0x0/0x4c
[<c022a30a>] nf_hook_slow+0x8e/0x124
[<c0232c44>] ip_forward_finish+0x0/0x4c
[<c0232bfc>] ip_forward+0x1ec/0x234
[<c0232c44>] ip_forward_finish+0x0/0x4c
[<c0231c89>] ip_rcv_finish+0x1bd/0x204
[<c022a348>] nf_hook_slow+0xcc/0x124
[<c02318da>] ip_rcv+0x3ae/0x3f0
[<c0231acc>] ip_rcv_finish+0x0/0x204
[<c0220fe0>] netif_receive_skb+0x13c/0x18c
[<c022109f>] process_backlog+0x6f/0x100
[<c02211a2>] net_rx_action+0x72/0x11c
[<c01202be>] do_softirq+0x4e/0xa0
[<c010d251>] do_IRQ+0x115/0x130
[<c010ba08>] common_interrupt+0x18/0x20
Code: 8b 53 08 0f b7 47 0e 31 f6 66 39 42 1e 75 2e 8b 07 39 42 10
<0>Kernel panic: Fatal exception in interrupt
In interrupt handler - not syncing
next prev parent reply other threads:[~2003-10-23 11:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F964F9D.D5C69498@fy.chalmers.se>
2003-10-23 9:02 ` [netfilter-core] linux-2.6.0-testX ipchains oops in NAT Harald Welte
2003-10-23 9:52 ` Andy Polyakov
2003-10-23 10:57 ` Harald Welte
2003-10-23 14:29 ` Andy Polyakov
2003-10-23 11:16 ` Andy Polyakov [this message]
2003-10-23 11:26 ` Andy Polyakov
2003-10-26 6:19 ` Rusty Russell
2003-10-26 13:31 ` Andy Polyakov
2003-10-27 7:58 ` David S. Miller
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=3F97B874.CB12C184@fy.chalmers.se \
--to=appro@fy.chalmers.se \
--cc=coreteam@netfilter.org \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@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.