Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 20 Oct 2005 12:31:59 +0000
From:      Marcin Jessa <lists@yazzy.org>
To:        Marcin Jessa <lists@yazzy.org>
Cc:        glebius@FreeBSD.org, current@FreeBSD.org, net@FreeBSD.org
Subject:   Re: PPPoE and Radius on 6.0RC1
Message-ID:  <20051020123159.33f6fa33.lists@yazzy.org>
In-Reply-To: <20051020131549.5e432073.lists@yazzy.org>
References:  <20051019235111.2225345e.lists@yazzy.org> <20051020070145.GA59364@cell.sick.ru> <20051020131549.5e432073.lists@yazzy.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 20 Oct 2005 13:15:49 +0200
Marcin Jessa <lists@yazzy.org> wrote:

> On Thu, 20 Oct 2005 11:01:45 +0400
> Gleb Smirnoff <glebius@FreeBSD.org> wrote:
> 
> > On Wed, Oct 19, 2005 at 11:51:11PM +0200, Marcin Jessa wrote:
> > M> It seems like PPPoE stoped working with support for radius on 6.0
> > M> The log of pppoe and freeradius does not show pppoe attempting to
> > M> even talk to the radius server. Additionally this message pops up
> > M> when enabling pppoed: WARNING: attempt to net_add_domain
> > M> (netgraph) after domainfinalize() My setup worked fine before on
> > M> FreeBSD 5.x Is that a known issue and is it being worked on?
> > 
> > Please show your PPPoE server configuration. Do you use pppoed or
> > mpd?
> 
> I use pppoed.
> Adding 
> netgraph_load="YES"
> ng_socket_load="YES"
> to /boot/loader.conf fixed it on my 6.0RC1 ( thanks Julian Elischer )
> Frankly I don't understand why this is needed since pppoed loads those
> modules when it starts up.

Just tested the same setup on 7.0 built tonight and it did not work.
The pppoed daemon never sends any requests to freeradius...
I tried to additionaly with those modules listed in loader.conf with no
luck:
ng_ether_load="YES"
ng_pppoe_load="YES"


> This is my ppp.conf, just for the record:
> 
> default:
>  #set log Chat Command Phase     #turn on some logging. See man
> ppp.conf for info set log Chat Command Phase hdlc lqm ipcp
>  enable mschapv2 mschap chap mppe       #turn on chap and pap
> accounting
>  #enable pap mschapv2 mschap chap mppe  #turn on chap and pap
>  #accounting enable pap                    #turn on chap and pap
>  #accounting
>  allow mode direct              #turn on ppp bridging
>  enable proxy                   #turn on ppp proxyarping (redundant of
> above???) disable ipv6cp                 #we don't use ipv6, don't
> want the errors set mru 1472                   #set mru below 1500
> (PPPoE MTU issue) set mtu 1472                   #set mtu below 1500
> (PPPoE MTU issue) set timeout 0                  #no mins time
> restriction on users #set timeout never
>  set mppe 128 *
>  set ifaddr 192.168.2.8 192.168.2.100-192.168.1.120 255.255.255.255
>  set log phase ipcp lcp debug           #additional debugging
>  nat enable yes
>  set dns 192.168.2.45 192.168.2.8
>  #set speed sync
>  set cd 3                       # checks for the existence of carrier
> once per second for 5 seconds #set cd 5!
>  #enable echo
>  enable lqr
>  set reconnect 1 5              # Should the line drop unexpectedly ,
> a connection will be re-established after the given timeout.
> 
> #Specify my wifi gateway IP as well as DHCP pool range
>  set radius /etc/ppp/radius.conf        #turn on radius auth and use
> this file accept dns                             #turn on dns
> cacheing/forwarding
> 
> #enable pap mschapv2 mschap chap mppe   #turn on chap and pap
> #accounting
>  disable pap pred1 deflate              #disable pred1 and deflate
> compression along with pap deny pap pred1 deflate
> #refuse when ask for it
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to
> "freebsd-current-unsubscribe@freebsd.org"



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051020123159.33f6fa33.lists>