[c-nsp] pppoe server config

[K bharathan]

thanks
how to forward traffic from l2tp to another router; l2tp is terminated at
the gateway router
want to put NAS for ADSL (pppoe) authenticaation



On Wed, Sep 28, 2011 at 8:47 AM, Christophe Lucas <
c.lucas at infosat-telecom.fr> wrote:

> Le 27/09/2011 23:15, K bharathan a écrit :
>
>> does anybody have any link to cisco pppoe server configuration examples
>> with
>> radius authentication
>> thanks
>> -bharathan
>> ______________________________**_________________
>> cisco-nsp mailing list  cisco-nsp at puck.nether.net
>> https://puck.nether.net/**mailman/listinfo/cisco-nsp<https://puck.nether.net/mailman/listinfo/cisco-nsp>
>> archive at http://puck.nether.net/**pipermail/cisco-nsp/<http://puck.nether.net/pipermail/cisco-nsp/>
>>
>
> Hi,
>
>
> I have skip some part of the config :
>
> [...]
> aaa new-model
>  !
>  !
>  aaa authentication ppp default group radius
>  aaa authorization network default group radius
>  aaa accounting exec default start-stop group radius
>  aaa accounting network default start-stop group radius
>  aaa accounting resource default start-stop group radius
>  !
>  aaa session-id common
>  clock timezone fr 2
>  !
>  !
>  ip cef
>  !
>  !
>  ip domain name mcom.fr
>  ip name-server 217.169.242.2
>  ip name-server 217.169.242.3
>  ip auth-proxy max-nodata-conns 3
>  ip admission max-nodata-conns 3
>  vpdn enable
> [...]
>
> !
>  bba-group pppoe global
>  virtual-template 1
>  sessions max limit 100
>  !
>  !
>  interface Loopback0
>  ip address 217.169.255.110 255.255.255.255
>  !
>  interface Tunnel0
>  ip address 192.168.37.214 255.255.255.252
>  tunnel source 217.169.240.130
>  tunnel destination 217.169.242.129
>  !
> [...]
>  interface GigabitEthernet0/1
>  ip address 172.22.14.1 255.255.255.0 secondary
>  ip address 172.22.66.1 255.255.255.0 secondary
>  ip address 172.22.68.1 255.255.255.0 secondary
>  ip address 172.22.70.1 255.255.255.0 secondary
>  ip address 172.22.96.1 255.255.255.0 secondary
>  ip address 192.168.4.1 255.255.255.0 secondary
>  ip address 192.168.6.1 255.255.255.0 secondary
>  ip address 217.169.240.73 255.255.255.252 secondary
>  ip address 192.168.240.1 255.255.255.252 secondary
>  ip address 217.169.241.129 255.255.255.128 secondary
>  ip address 92.42.220.129 255.255.255.128
>  ip policy route-map net-monitoring
>  duplex full
>  speed 100
>
>  pppoe enable group global
>
>  interface Virtual-Template1
>  ip unnumbered GigabitEthernet0/1
>  ip mtu 1492
>  ip route-cache policy
>  peer default ip address pool infosat
>  fair-queue
>  ppp mtu adaptive
>  ppp authentication ms-chap chap pap
>  ppp ipcp dns 217.169.242.3
>  ! ip local pool infosat 92.42.220.130 92.42.220.252
>  ip default-gateway 217.169.240.129
>  no ip forward-protocol nd
>  ip route 0.0.0.0 0.0.0.0 217.169.240.129
>
> !
>  radius-server attribute 31 mac format ietf
>  radius-server host 217.169.242.4 auth-port 1812 acct-port 1813 key 7
> 0103070D58460506355E4107
>
>
> Best regards,
> --
> Christophe Lucas - Network Engineer - c.lucas at infosat-telecom.fr
> Tel : +33(0)974.762.595 - Fax : +33(0)09.72.19.53.58
>
> "Ce message et toutes les pieces jointes sont etablis a l'attention
> exclusive de ses destinataires et sont confidentiels. L'internet ne
> permettant pas d'assurer l'integrite de ce message, le contenu de ce message
> ne represente en aucun cas un engagement de la part de notre societe. Si
> vous recevez ce message par erreur, merci de le detruire et d'en avertir
> immediatement l'expediteur.
>
> This message contains privileged and confidential information. Given that
> the internet does not allow us to make sure of the communication's
> integrity, the content of this message does not represent in any case a
> commitment from our company. If you are not the intended recipient, please
> notify us immediately and delete this e-mail (including any attachments)
> from your system."
>