Linux PPP protocol development
 help / color / mirror / Atom feed
From: Michal Ostrowski <mostrows@earthlink.net>
To: linux-ppp@vger.kernel.org
Subject: Re: Kernel-mode PPPoE server.
Date: Tue, 19 Oct 2004 10:30:29 +0000	[thread overview]
Message-ID: <1098181830.25095.199.camel@brick.watson.ibm.com> (raw)
In-Reply-To: <200410181453.16399.cpwp@w3z.co.uk>

[-- Attachment #1: Type: text/plain, Size: 2761 bytes --]

Try using the binary from the system that works on the new system.  I'm
not seeing there being any sort of pppoe specific problem.  It appears
to be an issue of pppd not sending the first LCP packet.

Perhaps somebody else can comment on this...


On Tue, 2004-10-19 at 10:09 +0100, Charles Price wrote:
> On Monday 18 October 2004 23:39, Michal Ostrowski wrote:
> > I think one can attribute this to a pppd behavior change.  There are
> > some options to pppd that control this behavior (silent?).  I'd check to
> > see if one of those options is sneaking in somewhere.  (Try using the
> > dryrun option to check?)
> >
> The configuration options that pppd printed to syslog are listed below.  Note 
> that I am using PAP this time, because I will be using RADIUS but the 
> concentrator does not send the first packet if I replace require-pap with 
> require-chap.
> 
> debug   # (from /etc/ppp/pppoe-server-options)
> nodetach   # (from command line)
> idle 43200   # (from /etc/ppp/options)
> dryrun   # (from /etc/ppp/pppoe-server-options)
> plugin /etc/ppp/plugins/rp-pppoe.so   # (from /etc/ppp/pppoe-server-options)
> plugin /etc/ppp/plugins/radius.so   # (from /etc/ppp/pppoe-server-options)
> plugin /etc/ppp/plugins/radattr.so   # (from /etc/ppp/pppoe-server-options)
> require-pap   # (from /etc/ppp/pppoe-server-options)
> login   # (from /etc/ppp/pppoe-server-options)
> eth1   # (from command line)
> rp_pppoe_service   # (from command line)
> rp_pppoe_sess 234:00:03:47:92:cf:e1   # (from command line)
> eth1   # (from command line)
> rp_pppoe_service   # (from command line)
> rp_pppoe_sess 234:00:03:47:92:cf:e1   # (from command line)
> noaccomp   # (from command line)
> default-asyncmap   # (from command line)
> mru 1492   # (from /etc/ppp/options)
> mtu 1492   # (from /etc/ppp/options)
> nopcomp   # (from command line)
> lcp-echo-failure 5   # (from /etc/ppp/pppoe-server-options)
> lcp-echo-interval 60   # (from /etc/ppp/pppoe-server-options)
> novj   # (from command line)
> novjccomp   # (from command line)
> ms-dns xxx # [don't know how to print value]   # (from /etc/ppp/options)
> proxyarp   # (from /etc/ppp/options)
> 80.168.87.200:10.67.15.234   # (from command line)
> nobsdcomp   # (from command line)
> nodeflate   # (from command line)
> noipx   # (from /etc/ppp/options)
> 
> 
> Any ideas on my next call of action? Would 'lsof' of pppoe-server and pppd 
> processes on working and non-working configurations be of any use?
> 
> I have tried replacing my kernel with the 2.4.20 from the working SuSE 
> configuration, to no avail - should I start downgrading pppd or rp-pppoe ?
> 
> Regards,
> 
> Charlie Price
-- 
Michal Ostrowski <mostrows@earthlink.net>

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2004-10-19 10:30 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
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 [this message]

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=1098181830.25095.199.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