[rbak-nsp] Fwd: Dual-Stack configuration for PPPoE subscribers

[Alex D.]

no suggestion ?

-------- Original-Nachricht --------
Betreff: 	[rbak-nsp] Dual-Stack configuration for PPPoE subscribers
Datum: 	Thu, 31 Oct 2013 11:13:34 +0100
Von: 	Alex D. <listensammler at gmx.de>
An: 	redback-nsp at puck.nether.net



Hi,

currently we have ~8000 PPPoE users terminated on a SE600 running
SEOS-11.1.2.4p3. All users get IPv4 addresses either from a dynamic pool
or as a framed-ip assigned via RADIUS. In the near future, i also want
to assign IPv6 addresses to the customers. The SE600 itself is already
configured for IPv6, but i didn't activate it in the logical
"subscriber"-interface.
Can someone give me a hint, which stebs are necessary for extending my
setup?
Questions:
- Is it enough to configure a ipv6 pool on the "SUBSCRIBER" interface
and refer to it in the "subscriber default" ?
- Where can i configure my delegated-prefix pool ?
- Is it possible to activate or deactivate IPv6 for certain customers,
e.g. based on a specific RADIUS attribute (compared to Ciscos AVpair
"lcp:interface-config#1=ipv6 enable") ?

Here's the relevant IPv4 part of my configuration:

context local
~
  interface LOOPBACK-0 loopback
   ip address<ip>/32
   ipv6 address<ipv6>/128
    ip source-address snmp radius tacacs+ syslog
!
  interface SUBSCRIBER multibind lastresort
   ip unnumbered LOOPBACK-0
   ip clear-df
   ip pool<network>/18
!
  subscriber default
    ip address pool name SUBSCRIBER
    port-limit 6
    ppp mtu 1492
    dns primary<ip>
    dns secondary<ip>
!

Thanks in advance...
Regards,
Alex
_______________________________________________
redback-nsp mailing list
redback-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/redback-nsp


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/redback-nsp/attachments/20131106/81dfd2fc/attachment.html>