From: Michal Ostrowski <mostrows@earthlink.net>
To: linux-ppp@vger.kernel.org
Subject: Re: Kernel-mode PPPoE server.
Date: Mon, 18 Oct 2004 17:21:07 +0000 [thread overview]
Message-ID: <1098120068.25095.163.camel@brick.watson.ibm.com> (raw)
In-Reply-To: <200410181453.16399.cpwp@w3z.co.uk>
[-- Attachment #1: Type: text/plain, Size: 3091 bytes --]
From rom what I can tell the problem is on the other end of the connection.
It looks like the other end has terminated your connection.
PPP/PPPoE on this end appears to be behaving correctly.
--
Michal Ostrowski <mostrows@earthlink.net>
On Mon, 2004-10-18 at 16:09 +0100, Charles Price wrote:
> Thanks, for the quick response, Michal...
>
> > Try running an "strace" on the pppoe-server to see what system call
> > fails.
> >
> I have posted the output of 'strace -f pppoe-server' to
> http://hognaston.com/strace.txt - I thought it might have been bad netiquette
> to post something of that length to a mailing list ;-)
>
> There seem to be a number of entries in there that look like error messages in
> the output, but since I've not used strace before a second opinion would be
> appreciated.
>
> > Also, a tcpdump log of the packets going back and forth would be useful.
> >
> pppoe2 root # tcpdump -i eth1 -n
> tcpdump: WARNING: eth1: no IPv4 address assigned
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
> listening on eth1, link-type EN10MB (Ethernet), capture size 68 bytes
> 16:03:45.626913 PPPoE PADI [Service-Name] [Host-Uniq 0x1D180000] [EOL]
> 16:03:45.627118 PPPoE PADO [AC-Name "W3Z-2"] [Service-Name "W3Z"] [AC-Cookie
> 0x7880E92E058E66DFBCE211A52AACD52592280000] [Host-Uniq 0x1D180000]
> 16:03:45.627242 PPPoE PADR [Service-Name] [Host-Uniq 0x1D180000] [AC-Cookie
> 0x7880E92E058E66DFBCE211A52AACD52592280000]
> 16:03:45.627766 PPPoE PADS [ses 0x2] [Service-Name "W3Z"] [Host-Uniq
> 0x1D180000]
> 16:03:46.627238 PPPoE [ses 0x2] LCP, Conf-Request (0x01), id 1, MRU 1492,
> Magic-Num 0xf9397f65, length 14
> 16:03:49.627791 PPPoE [ses 0x2] LCP, Conf-Request (0x01), id 1, MRU 1492,
> Magic-Num 0xf9397f65, length 14
> 16:03:52.628551 PPPoE [ses 0x2] LCP, Conf-Request (0x01), id 1, MRU 1492,
> Magic-Num 0xf9397f65, length 14
> 16:03:55.629318 PPPoE [ses 0x2] LCP, Conf-Request (0x01), id 1, MRU 1492,
> Magic-Num 0xf9397f65, length 14
> 16:03:58.630084 PPPoE [ses 0x2] LCP, Conf-Request (0x01), id 1, MRU 1492,
> Magic-Num 0xf9397f65, length 14
> 16:04:01.630851 PPPoE [ses 0x2] LCP, Conf-Request (0x01), id 1, MRU 1492,
> Magic-Num 0xf9397f65, length 14
> 16:04:04.631645 PPPoE [ses 0x2] LCP, Conf-Request (0x01), id 1, MRU 1492,
> Magic-Num 0xf9397f65, length 14
> 16:04:07.632412 PPPoE [ses 0x2] LCP, Conf-Request (0x01), id 1, MRU 1492,
> Magic-Num 0xf9397f65, length 14
> 16:04:10.633178 PPPoE [ses 0x2] LCP, Conf-Request (0x01), id 1, MRU 1492,
> Magic-Num 0xf9397f65, length 14
> 16:04:13.633944 PPPoE [ses 0x2] LCP, Conf-Request (0x01), id 1, MRU 1492,
> Magic-Num 0xf9397f65, length 14
> 16:04:16.641160 PPPoE PADT [ses 0x2] [Host-Uniq 0x1D180000] [Generic-Error
> "RP-PPPoE: System call error: Input/o..........."]
> 16:04:16.641313 PPPoE PADT [ses 0x2] [Generic-Error "Received PADT"]
>
> 16 packets captured
> 16 packets received by filter
> 0 packets dropped by kernel
>
> Regards,
>
> Charlie Price
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-10-18 17:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-18 13:53 Kernel-mode PPPoE server Charles Price
2004-10-18 14:46 ` Michal Ostrowski
2004-10-18 15:09 ` Charles Price
2004-10-18 17:21 ` Michal Ostrowski [this message]
2004-10-18 20:45 ` Charles Price
2004-10-18 21:04 ` Michal Ostrowski
2004-10-18 21:29 ` Charles Price
2004-10-19 9:09 ` Charles Price
2004-10-19 10:30 ` Michal Ostrowski
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=1098120068.25095.163.camel@brick.watson.ibm.com \
--to=mostrows@earthlink.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox