From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, pigi@frumar.it
Subject: Re: [Bugme-new] [Bug 11470] New: pppoe not working when acting as gateway.
Date: Sun, 31 Aug 2008 11:17:18 -0700 [thread overview]
Message-ID: <20080831111718.d47fa76f.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-11470-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Sun, 31 Aug 2008 09:59:12 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=11470
>
> Summary: pppoe not working when acting as gateway.
> Product: Networking
> Version: 2.5
> KernelVersion: 2.6.26.3
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Netfilter/Iptables
> AssignedTo: networking_netfilter-iptables@kernel-bugs.osdl.org
> ReportedBy: pigi@frumar.it
> CC: networking_netfilter-iptables@kernel-bugs.osdl.org
>
>
> Latest working kernel version: 2.6.21.7
> Earliest failing kernel version: 2.6.22
> Distribution: Slackware
> Hardware Environment: Ibm Thinkpad T23 Intel(R) Pentium(R) III Mobile CPU
> 1133MHz
> Software Environment:
> Problem Description:
> Packet are not handled back to clients, neither are see on ppp0
>
> Steps to reproduce:
> Just put a MASQUERADE rule in iptables, to NAT packects from client to
> internet, with a FORWARD rule that allow the packects to be forwarded. Try to
> ping or dig or telnet or whatever from the client and nothing happens.
>
> My configuration is :
>
> CLIENT ----> T23 -----> DSL-MODEM -----> INTERNET
>
>
> Client = linux machine
> T23 = linux machine with everything configure to act as a dsl router
> On T23 I'm using vanilla kernel recompiled by myself, using the same config
> that is working on 2.6.21.7
> pppoe binaries is :
> root /usr/src >/usr/sbin/pppoe -V
> Roaring Penguin PPPoE Version 3.8
>
>
> I have another linux machine on internet, that I have used to verify the
> problem.
>
> When I run the ping from the client, on the router I can see the packet come in
> from the eth0 and leaving natted from the ppp0. On the internet machine I see
> the icmp packet ( or whatever packet I send ) coming in, and the reply going
> out to the router machine.
> This packet seems to be lost ( i can't see it on the router either on ppp
> interface than on eth0 interface ), by using tcpdump (3.9.5).
> If the communication is started from the router ( icmp, ssh, whatever )
> everything works well.
>
> Running the 2.6.21.7 but keeping the same configuration for kernel, iptables
> and all, is seen on router and handled back to client.
> Not working behavior is seen on 2.6.22+ to 2.6.26.3
> Working behavior is seen on 2.6.21.7- ( at last to 2.6.19.2 which was my
> starting kernel )
>
> At beginning I thought the problem was with iptables
> root /usr/src >iptables -V
> iptables v1.3.8
> but the strange thing is that I can't even see the reply packets on ppp0
> interface, while if the trouble was on iptables rules, then I should have seen
> the packet and then I should have seen it dropped somewhere.
> Anyway I have put netfilters guys in CC just in case I'm wrong.
>
> Googling around I have seen others that have similar behavior and I have seen
> that in 2.6.22 there is been a lot of change in pppoe area.
>
> Let me know if you need more informations.
>
> The 2.6.22 .config is:
> ...
next parent reply other threads:[~2008-08-31 18:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11470-10286@http.bugzilla.kernel.org/>
2008-08-31 18:17 ` Andrew Morton [this message]
2008-09-01 12:04 ` [Bugme-new] [Bug 11470] New: pppoe not working when acting as gateway 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=20080831111718.d47fa76f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pigi@frumar.it \
/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).