[rbak-nsp] problem of authentification on last-resort interface
Greg GOUDOU
greg.goudou at gmail.com
Mon Apr 19 09:36:12 EDT 2010
Hi Julia,
Thank you for your answer. But the clients authenticate themselves into
PPPoE service. Therefore, they retrieve their public IP address from LDAP
server.
Moreover, I have tried to configure each interface in multibind but clients
failed to authenticate. There is no attempts.
Grégory
De : Mariano Juliá [mailto:mjuliaq at gmail.com]
Envoyé : samedi 17 avril 2010 22:21
À : Greg GOUDOU
Objet : Re: [rbak-nsp] problem of authentification on last-resort interface
Hi Greg,
The following config does what you are asking for but not so sure this is
what you really want to achieve.
context A vpn-rd 1:6
interface PPP-client1 multibind
ip address 1.1.1.1/30
interface PPP-client2 multibind
ip address 2.2.2.1/30
Provided that the subs address are 1.1.1.2 and 2.2.2.2 (they fall within the
interface subnet mask) they will bind to their respective interfaces.
IIRC there is also a VSA to bind the subscriber to a specific interface, but
I have never used or tested it.
Hope this helps,
Mariano
On 16 April 2010 17:22, Greg GOUDOU <greg.goudou at gmail.com> wrote:
Hi,
I meet a problem about a configuration. I cannot create in a same context,
2 multibind last-resort interfaces.
But, I already have a PPPoE client connected in this context (we will
called context A). Below, his configuration:
Context A vpn-rd XXXX:6
interface Loop_client1 loopback
ip address A.B.C.D/32 with A.B.C.D/32 is a public IP address
interface PPP-client1 multibind lastresort
ip unnumbered Loop_client1
the second client is configured as defined below :
Context A vpn-rd XXXX:6
interface Loop_client2 loopback
ip address A.B.F.G/32 with A.B.F.G/32 is a public IP address
interface PPP-client2 multibind
ip unnumbered Loop_client2
when we verify the state of the connection of the clients, we notice :
For client 1:
client1 at realm.xx
Agent Remote ID "client1"
Circuit 4/8 vlan-id 426 pppoe 21240
Internal Circuit 4/8:1023:63/6/2/44395
Interface bound PPP-client1
Current port-limit unlimited
context-name A (applied)
dns primary X.X.X.X (applied)
dns secondary Y.Y.Y.Y (applied)
ip address A.B.C.D (applied)
forward policy in FORWARD_FIRSTBOOT (applied)
For client2, I receive this state of connection:
client2 at realm.xx
Agent Remote ID "Client2"
Circuit 4/8 vlan-id 401 pppoe 16731
Internal Circuit 4/8:1023:63/6/2/34556
Interface bound PPP-client1
Current port-limit unlimited
context-name A (applied)
dns primary X.X.X.X (applied)
dns secondary Y.Y.Y.Y (applied)
ip address A.B.F.G (applied)
forward policy in FORWARD_FIRSTBOOT (applied)
Therefore, I would like these clients have each of them, a public IP address
and pass through their own interface bound.
If somebody have a solution, let me know.
Regards,
gOOdman
_______________________________________________
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/20100419/1e75eceb/attachment.html>
More information about the redback-nsp
mailing list