PPPoE connections problem

[Dmitriy Sirant]

Hello

Have Debian Sarge, pppd-2.4.3, pppoe-server-3.5.

/etc/ppp/pppoe-server-options
require-chap
mru 1480
mtu 1480
debug
logfile /var/log/pppd.log
nobsdcomp
noccp
noendpoint
noipdefault
noipx
nodeflate
novj
novjccomp
nopredictor1
nopcomp
noaccomp
ms-dns xxx.xxx.xxx.xxx
receive-all

In /etc/ppp/chap-secrets all informations is added.

Start pppoe server by command
/usr/sbin/pppoe-server -I eth4 -L xxx.xxx.xxx.xxx

Have in logs:
Using interface ppp0
Connect: ppp0 <--> /dev/pts/1
sent [LCP ConfReq id=0x1 <mru 1480> <auth chap MD5> <magic 0x81900d15>]
rcvd [LCP ConfReq id=0x1 <mru 1480> <magic 0x650d348f>]
sent [LCP ConfAck id=0x1 <mru 1480> <magic 0x650d348f>]
sent [LCP ConfReq id=0x1 <mru 1480> <auth chap MD5> <magic 0x81900d15>]
rcvd [LCP ConfReq id=0x2 <mru 1480> <magic 0x650d348f>]
sent [LCP ConfAck id=0x2 <mru 1480> <magic 0x650d348f>]
sent [LCP ConfReq id=0x1 <mru 1480> <auth chap MD5> <magic 0x81900d15>]
rcvd [LCP ConfReq id=0x3 <mru 1480> <magic 0x650d348f>]
sent [LCP ConfAck id=0x3 <mru 1480> <magic 0x650d348f>]
sent [LCP ConfReq id=0x1 <mru 1480> <auth chap MD5> <magic 0x81900d15>]
rcvd [LCP ConfReq id=0x4 <mru 1480> <magic 0x650d348f>]
sent [LCP ConfAck id=0x4 <mru 1480> <magic 0x650d348f>]
sent [LCP ConfReq id=0x1 <mru 1480> <auth chap MD5> <magic 0x81900d15>]
sent [LCP ConfReq id=0x1 <mru 1480> <auth chap MD5> <magic 0x81900d15>]
rcvd [LCP ConfReq id=0x5 <mru 1480> <magic 0x650d348f>]
sent [LCP ConfAck id=0x5 <mru 1480> <magic 0x650d348f>]
sent [LCP ConfReq id=0x1 <mru 1480> <auth chap MD5> <magic 0x81900d15>]
rcvd [LCP ConfReq id=0x6 <mru 1480> <magic 0x650d348f>]
sent [LCP ConfAck id=0x6 <mru 1480> <magic 0x650d348f>]
sent [LCP ConfReq id=0x1 <mru 1480> <auth chap MD5> <magic 0x81900d15>]
rcvd [LCP ConfReq id=0x7 <mru 1480> <magic 0x650d348f>]
sent [LCP ConfAck id=0x7 <mru 1480> <magic 0x650d348f>]
sent [LCP ConfReq id=0x1 <mru 1480> <auth chap MD5> <magic 0x81900d15>]
sent [LCP ConfReq id=0x1 <mru 1480> <auth chap MD5> <magic 0x81900d15>]
rcvd [LCP ConfReq id=0x8 <mru 1480> <magic 0x650d348f>]
sent [LCP ConfAck id=0x8 <mru 1480> <magic 0x650d348f>]
LCP: timeout sending Config-Requests
Connection terminated.
using channel 14
Using interface ppp0
Connect: ppp0 <--> /dev/pts/2
Waiting for 2 child processes...
script /usr/sbin/pppoe -n -I eth4 -e 1:00:11:11:23:d0:d6Init -S '',
pid 9691
script /usr/sbin/pppoe -n -I eth4 -e 1:00:11:11:23:d0:d6Init -S '',
pid 9688
sending SIGTERM to process 9691
sending SIGTERM to process 9688
tcflush failed: Bad file descriptor

First question - why "LCP: timeout sending Config-Requests" ?
Second question - why "tcflush failed: Bad file descriptor" ?
Third question - why i have two "/usr/sbin/pppoe" with different pid
(9691 and 9688) and both of them not killed when finished (with error)
connection ?

Thank you for answer.

[Lew Pitcher]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Because your side never receives a ConfAck or ConfNak for it's ConfReq
messages. It finally gave up waiting for the partner to Ack or Nak the
outstanding ConfReq

> Second question - why "tcflush failed: Bad file descriptor" ?

Likely a remnant of the script. The PPPoE service establishes a
pseudo-terminal for PPP to talk to. PPP thinks it is talking to a real
serial terminal, and makes sure that the terminal is in a known good
state when PPP shuts down. But, since the terminal is a PTY run by PPPoE
and PPPoE has already shut down, the PTY file descripter is invalid when
PPP finally gets to cleaning it up.

> Third question - why i have two "/usr/sbin/pppoe" with different pid
> (9691 and 9688) and both of them not killed when finished (with error)
> connection?

Don't know. P'haps the PPPoe service forks off two children to handle in
and out traffic?

> Thank you for answer.

FWIW, your config is such that the other party of the PPPoE connection
must authenticate with you. Most ISPs won't work with this config, and
expect your PPPoE to authenticate with them instead. I hope that you are
acting as an ISP here, rather than a customer of an ISP, because your
PPPoE isn't configured to act as the customer end of a typical ISP
connection.

- --

Lew Pitcher, IT Specialist, Enterprise Data Systems
Enterprise Technology Solutions, TD Bank Financial Group

(Opinions expressed here are my own, not my employer's)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)

iD8DBQFCgLLjagVFX4UWr64RAh7MAJ90VZ9tNnHz8XCXUaDAkgqXVj9gVQCfZZCB
JMaYmKmSQHJLFCariZpy/ik=
=cxyB
-----END PGP SIGNATURE-----

[Dmitriy Sirant]

Ok, more information gave about it. I try use at server side two
different versions of pppd. When i use ppp-2.4.3 have that situation,
but when i use ppp-2.4.1 from debian woody all work fine. As i
understand, mine client is configured right and physical link is ok,
is'n it ?

> > Second question - why "tcflush failed: Bad file descriptor" ?
>
> Likely a remnant of the script. The PPPoE service establishes a
> pseudo-terminal for PPP to talk to. PPP thinks it is talking to a
real
> serial terminal, and makes sure that the terminal is in a known good
> state when PPP shuts down. But, since the terminal is a PTY run by
PPPoE
> and PPPoE has already shut down, the PTY file descripter is invalid
when
> PPP finally gets to cleaning it up.
>

That problem also only if using ppp-2.4.3 and haven't it in ppp-2.4.1

> > Third question - why i have two "/usr/sbin/pppoe" with different
pid
> > (9691 and 9688) and both of them not killed when finished (with
error)
> > connection?
>
> Don't know. P'haps the PPPoe service forks off two children to handle
in
> and out traffic?

And that problem only in ppp-2.4.3, not in ppp-2.4.1

>
> > Thank you for answer.
>
> FWIW, your config is such that the other party of the PPPoE
connection
> must authenticate with you. Most ISPs won't work with this config,
and
> expect your PPPoE to authenticate with them instead. I hope that you
are
> acting as an ISP here, rather than a customer of an ISP, because your
> PPPoE isn't configured to act as the customer end of a typical ISP
> connection.

Yes, i try to make pppoe-server for use it with clients windows and
linux. As i wrote above with ppp-2.4.1 all work fine, but i need radius
support. As i know in ppp-2.4.1 plugins is not present.

I think that problem can be only in debian package, but now can't try
make package from sources.
In Debian bugtraq that bug commited:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=308383
If you can help - please do it

Thank you for answer.

[Unruh]

"Dmitriy Sirant" <sir...@gmail.com> writes:

>Hello

>Have Debian Sarge, pppd-2.4.3, pppoe-server-3.5.

>/etc/ppp/pppoe-server-options
>require-chap

Why do you want them to authenticate themselves to you? Are you the isp?
Almost no ISP will do so. If you are not the isp, remove this line.

>mru 1480
>mtu 1480
>debug
>logfile /var/log/pppd.log
>nobsdcomp
>noccp
>noendpoint
>noipdefault
>noipx
>nodeflate
>novj
>novjccomp

Why all of these no... entries. What is wrong with defaults?

>nopredictor1
>nopcomp
>noaccomp
>ms-dns xxx.xxx.xxx.xxx
>receive-all

>In /etc/ppp/chap-secrets all informations is added.

>Start pppoe server by command
>/usr/sbin/pppoe-server -I eth4 -L xxx.xxx.xxx.xxx

>Have in logs:
>Using interface ppp0
>Connect: ppp0 <--> /dev/pts/1
>sent [LCP ConfReq id=0x1 <mru 1480> <auth chap MD5> <magic 0x81900d15>]
>rcvd [LCP ConfReq id=0x1 <mru 1480> <magic 0x650d348f>]

They do not hear you. Probably modem problems.

Who cares. The relevant thing is that they cannot hear you. Fix that first.

[Dmitriy Sirant]

Who cares. The relevant thing is that they cannot hear you. Fix that
first.

As i wrote above, i ISP, and when i use ppp-2.4.1 instead of 2.4.3 all
work fine. From that i think that phisycal link is good and problem in
server side of ppp.