From: Jan Just Keijser <jan.just.keijser@gmail.com>
To: linux-ppp@vger.kernel.org
Subject: Re: pppd, pptpd and radius DNS assigns
Date: Tue, 08 Sep 2015 11:37:26 +0000 [thread overview]
Message-ID: <55EEC876.9030503@gmail.com> (raw)
In-Reply-To: <CANso6eGvSYC8WdCD5d7ZXVqb+RQhS4BXz69ZxQX2QQ8YuQ1Yew@mail.gmail.com>
Edwardo Garcia wrote:
> On 9/8/15, James Carlson <carlsonj@workingcode.com> wrote:
>
>> On 9/7/2015 2:46 AM, Edwardo Garcia wrote:
>>
>>> Nobody?
>>>
>> I delayed responding because I'm not using freeradius. I don't know who
>> might be. If there's a support list for that software, you might have
>> better luck over there. If not, you might be on your own.
>>
>>
>>>> I try strace but it not too helpful, maybe I miss an option to make
>>>> pppd do this?
>>>>
>> strace doesn't sound like the right sort of tool for this problem.
>> Instead, have you tried the pppd "debug" option?
>>
>
> strace using -ff show far more information than ppp debug which we also try.
>
>
>> Looking at the RADIUS source (and knowing nothing about it), it looks
>> like it needs to be compiled with "MSDNS" defined and that you need
>> RADIUS attributes 28 and 29 set. Have you done that?
>>
>>
>
> Yes, this is default and is not freeradius problem as freeradius send
> the information in accept packet, just pppd ignore it, my colleuge has
> email someone at roaring penguin about it, but will not be available
> until next couple hours so do not know if he has receive answer or not
>
>
did you read/follow
http://wiki.freeradius.org/guide/PopTop-HOWTO
? the radius server *must* respond with the Microsoft vendor id (311)
set, otherwise the plugin will not pick up the supplied DNS values.
JJK
next prev parent reply other threads:[~2015-09-08 11:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 23:44 pppd, pptpd and radius DNS assigns Edwardo Garcia
2015-09-07 6:46 ` Edwardo Garcia
2015-09-07 14:26 ` James Carlson
2015-09-08 6:28 ` Edwardo Garcia
2015-09-08 11:37 ` Jan Just Keijser [this message]
2015-09-08 11:39 ` Edwardo Garcia
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=55EEC876.9030503@gmail.com \
--to=jan.just.keijser@gmail.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.