From: Stephen Hemminger <shemminger@osdl.org>
To: linux-ppp@vger.kernel.org
Subject: Fw: [Bug 6402] New: KERNEL 2.6.16-rX (Gentoo) && PPPD && SNAT
Date: Mon, 17 Apr 2006 22:08:28 +0000 [thread overview]
Message-ID: <20060417150828.3dbf6bb5@localhost.localdomain> (raw)
Begin forwarded message:
Date: Mon, 17 Apr 2006 14:56:59 -0700
From: bugme-daemon@bugzilla.kernel.org
To: shemminger@osdl.org
Subject: [Bug 6402] New: KERNEL 2.6.16-rX (Gentoo) && PPPD && SNAT
http://bugzilla.kernel.org/show_bug.cgi?idd02
Summary: KERNEL 2.6.16-rX (Gentoo) && PPPD && SNAT
Kernel Version: 2.6.16.ALL
Status: NEW
Severity: high
Owner: shemminger@osdl.org
Submitter: slavon@bigtelecom.ru
After start download file its stop after 4-10 mb and network is down.
Interface ppp0 is UP.
No new dmeseg or debug of syslog
try to ping ppp client:
slavon ~ # ping 192.168.0.2
PING 192.168.0.2 (192.168.0.2) 56(84) bytes of data.
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
#ifconfig ppp0
ppp0 Link encap:Point-to-Point Protocol
inet addr:192.168.0.1 P-t-P:192.168.0.2 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1396 Metric:1
RX packets:1648 errors:0 dropped:0 overruns:0 frame:0
TX packets:2407 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:75765 (73.9 Kb) TX bytes:3242633 (3.0 Mb)
#iptables-save
*nat
:PREROUTING ACCEPT [6826:411515]
:POSTROUTING ACCEPT [11117:531811]
:OUTPUT ACCEPT [11118:531895]
-A POSTROUTING -s 192.168.0.0/255.255.255.0 -j SNAT --to-source XXX.XXX.XXX.XXX
COMMIT
slavon ~ # pppd --version
pppd version 2.4.3
slavon ~ # pptpd --version
pptpd v1.3.1
I try it in 3 Computers 2 - x86 and 1 - x86-64 - All have this trouble
its gentoo patches for kernel
* Applying 1000_linux-2.6.16.1.patch (-p0+)
* Applying 1001_linux-2.6.16.2.patch (-p0+)
* Applying 1002_linux-2.6.16.3.patch (-p0+)
* Applying 1003_linux-2.6.16.4.patch (-p0+)
* Applying 1700_sparc-obp64-naming.patch (-p0+)
* Applying 1705_sparc-U1-hme-lockup.patch (-p0+)
* Applying 1710_sparc-sparsemem.patch (-p0+)
* Applying 1715_ppc32-crosscc-ssp.patch (-p0+)
* Applying 2400_sky2-1.1.patch (-p0+)
* Applying 2405_skge-1.5.patch (-p0+)
* Applying 2600_input-mod-devicetable.patch (-p0+)
* Applying 4000_deprecate-sk98lin.patch (-p0+)
* Applying 4100_libata-enable-atapi.patch (-p0+)
* Applying 4105_dm-bbr.patch (-p0+)
* Applying 4110_promise-pdc2037x.patch (-p0+)
* Applying 4200_fbsplash-0.9.2-r5.patch (-p0+)
* Applying 4205_vesafb-tng-1.0-rc1-r3.patch (-p0+)
* Applying 4300_squashfs-3.0.patch (-p0+)
* Applying 4400_speakup-20060103.patch (-p0+)
* Applying 4401_speakup-highlight-tracking-amd64.patch (-p0+)
* Applying 4405_alpha-sysctl-uac.patch (-p0+)
!! In 2.6.15 kernel ALL WORK.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
reply other threads:[~2006-04-17 22:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060417150828.3dbf6bb5@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=linux-ppp@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 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.