From: Jouko Nikula <nikujo@luukku.com>
To: linux-ppp@vger.kernel.org
Subject: Intervening IPCP Configure Requests
Date: Wed, 11 Aug 2010 13:12:45 +0000 [thread overview]
Message-ID: <29408130.post@talk.nabble.com> (raw)
Hello,
I'm using pppd as a server and I would want to do the following:
1.) Client sends IPCP configure request including an IP-address for the
client
2.) Before pppd responds I want to decide on accepting or rejecting the IP
address outside pppd
3.) Based on the decision in 2.) I want either to ACK the IPCP configure
request or terminate the ppp connection.
Second use case is when client does not specify an IP-address. Then I would
want to acquire a dynamic address, again outside pppd. If I found out that
dynamic addresses are not allowed I would terminate the ppp connection,
otherwise I would want to NAK the IPCP configure request with the acquired
IP-address.
I have looked into pppd plugin interface, but if I understand correctly the
current interface only provides the address given on the command line or
options file, not the ip-address requested by the other end. The ip-up or
ip-pre-up scripts don't seem to work for me because they are called when the
IPCP negotiation has already ended.
Could you please give me some ideas how I could implement this? Should I
extend the plugin interface so that I add hooks for IPCP negotiation and
create a plugin for this?
Thanks in advance!
Regards,
Jouko Nikula
--
View this message in context: http://old.nabble.com/Intervening-IPCP-Configure-Requests-tp29408130p29408130.html
Sent from the linux-ppp mailing list archive at Nabble.com.
next reply other threads:[~2010-08-11 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 13:12 Jouko Nikula [this message]
2010-08-12 13:20 ` Intervening IPCP Configure Requests James Carlson
2010-08-16 13:33 ` Jouko Nikula
2010-08-16 14:07 ` James Carlson
2010-08-18 10:59 ` Jouko Nikula
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=29408130.post@talk.nabble.com \
--to=nikujo@luukku.com \
--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.