Mailing List Archive

Redirection to WWW determined by AVP
Hi,



We have a ADSL VPDN over L2TP product.



Has anyone implemented the following?



ADSL users who have failed to meet their T&C's are directed toward a WWW
page and have no net access.



Thought that this would be moving towards Policy-Based-Routing, routing
on source rather than destination. Is this a possibility, or is their a
smarter way to implement this via RADIUS?



Thanks

Mark
Re: Redirection to WWW determined by AVP [ In reply to ]
Try thinking along a solution that would "send" these clients to a closed VRF...
Arie

On 7/8/05, Mark Tohill <Mark@u.tv> wrote:
>
>
> Hi,
>
>
>
> We have a ADSL VPDN over L2TP product.
>
>
>
> Has anyone implemented the following?
>
>
>
> ADSL users who have failed to meet their T&C's are directed toward a WWW
> page and have no net access.
>
>
>
> Thought that this would be moving towards Policy-Based-Routing, routing on
> source rather than destination. Is this a possibility, or is their a
> smarter way to implement this via RADIUS?
>
>
>
> Thanks
>
> Mark
>
>
> _______________________________________________
> cisco-bba mailing list
> cisco-bba@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-bba
>
>
>
Re: Redirection to WWW determined by AVP [ In reply to ]
On Fri, 8 Jul 2005, Mark Tohill wrote:

> Thought that this would be moving towards Policy-Based-Routing, routing
> on source rather than destination. Is this a possibility, or is their a
> smarter way to implement this via RADIUS?

Assign the users you wish to redirect a block of RFC1918 address space
when they login. This address space is policy-routed to your 'playpen'
machine. This is how we do it for customers who are suspended or have to
change their dial number or similar.

access-list 98 remark *** Playpen
access-list 98 permit 10.100.0.0 0.0.255.255
!
route-map PLAYPEN permit 5
match ip address 98
set ip next-hop 10.13.102.1
!
route-map PLAYPEN permit 20

The next hop can either be your web server, or a tunnel towards a router
on the same subnet.

The only drawback to this approach is the customer has to disconnect to
get 'real' Internet access once they're done paying their bill/agreeing to
the T&C's/etc.

Other suggestions include:

- Use a VRF with a different default route. You'd still need the directly
connected web server, or a tunnel to it, or MPLS to get traffic to go
the right direction.

- Investigate Cisco's SSG stuff. I only know Marketing-speak about it, but
apparently it does exactly what you're after. Multiple services are
defined ('Internet', 'Playpen', 'Free Gaming only', etc). RADIUS
authenticates the user when they want to access each service (defined by
IP address or interface) giving access based on business rules. So if I
understand the whole thing correctly, you could put all users by default
in the 'Playpen' service, then only let the signed up customers access
anything else.

- If you already transparently cache users, intercept them here using an
LDAP lookup or similar.

Rgds,




- I.

--
Ian Henderson, CCIE #14721
Senior Network Engineer

iiNet Limited
Chime Communications Pty Ltd
RE: Redirection to WWW determined by AVP [ In reply to ]
Ian,

Thanks for reply.

I think we'll definitely give your first option a go.

Seems fairly simple to implement.

BTW, is your first suggestion Policy-Based Routing or does it just do
something similar?

Thanks
Mark

-----Original Message-----
From: Ian Henderson [mailto:ianh@chime.net.au]
Sent: 10 July 2005 06:29
To: Mark Tohill
Cc: cisco-bba@puck.nether.net
Subject: Re: [cisco-bba] Redirection to WWW determined by AVP

On Fri, 8 Jul 2005, Mark Tohill wrote:

> Thought that this would be moving towards Policy-Based-Routing,
routing
> on source rather than destination. Is this a possibility, or is their
a
> smarter way to implement this via RADIUS?

Assign the users you wish to redirect a block of RFC1918 address space
when they login. This address space is policy-routed to your 'playpen'
machine. This is how we do it for customers who are suspended or have to
change their dial number or similar.

access-list 98 remark *** Playpen
access-list 98 permit 10.100.0.0 0.0.255.255
!
route-map PLAYPEN permit 5
match ip address 98
set ip next-hop 10.13.102.1
!
route-map PLAYPEN permit 20

The next hop can either be your web server, or a tunnel towards a router
on the same subnet.

The only drawback to this approach is the customer has to disconnect to
get 'real' Internet access once they're done paying their bill/agreeing
to
the T&C's/etc.

Other suggestions include:

- Use a VRF with a different default route. You'd still need the
directly
connected web server, or a tunnel to it, or MPLS to get traffic to go
the right direction.

- Investigate Cisco's SSG stuff. I only know Marketing-speak about it,
but
apparently it does exactly what you're after. Multiple services are
defined ('Internet', 'Playpen', 'Free Gaming only', etc). RADIUS
authenticates the user when they want to access each service (defined
by
IP address or interface) giving access based on business rules. So if
I
understand the whole thing correctly, you could put all users by
default
in the 'Playpen' service, then only let the signed up customers access
anything else.

- If you already transparently cache users, intercept them here using an
LDAP lookup or similar.

Rgds,




- I.

--
Ian Henderson, CCIE #14721
Senior Network Engineer

iiNet Limited
Chime Communications Pty Ltd
RE: Redirection to WWW determined by AVP [ In reply to ]
Mark Tohill wrote on Wednesday, 13 July 2005 4:43 PM:

> BTW, is your first suggestion Policy-Based Routing or does it
> just do something similar?

Yes, just policy routing.

--
Ian Henderson, CCIE #14721
Senior Network Engineer

iiNet Limited
Chime Communications Pty Ltd