netdev
[Top] [All Lists]

Re: Dynamic access lists

To: SVR Anand <anand@xxxxxxxxxxxxxxxxx>
Subject: Re: Dynamic access lists
From: Alberto Bertogli <albertogli@xxxxxxxxxxxxx>
Date: Mon, 25 Feb 2002 23:38:04 -0300
Cc: netdev@xxxxxxxxxxx
In-reply-to: <200202251644.WAA18555@eis.iisc.ernet.in>; from anand@eis.iisc.ernet.in on Mon, Feb 25, 2002 at 10:14:47PM +0530
Mail-followup-to: Alberto Bertogli <albertogli@xxxxxxxxxxxxx>, SVR Anand <anand@xxxxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx
References: <20020223125506.A200@telpin.com.ar> <200202251644.WAA18555@eis.iisc.ernet.in>
Sender: owner-netdev@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Mon, Feb 25, 2002 at 10:14:47PM +0530, SVR Anand wrote:
> Alberto,
> 
> Thanks for your mail!
> 
> I am actually not looking at VPN/PPP kind of scenario. A plain campus LAN on
> which some of the hosts get great service without their knowledge :), Of 
> course
> only after they get authenticated. As you rightly pointed out a simple
> scripting might suffice to begin with. Since I have to deal with host 
> idle times to update my filters in TC, per-host "last heard from" information
> is necessary.

Don't underestimate the power of the scripts. You can handle this
scenario using scripts and a web interface to start/stop the session in
an incredibly clean and efficient way.

If you are thinking about something even more clean, PPPoE is exactly
what you want: individual authenticated tunnels through a lan that end
in your router, where you do the link to the internet.

You can do all that with linux, without needing an expensive and closed
firewall which has limited capability.

As for the PPPoE client, i found RASPPPoE to be a great choice.

In fact, this scheme is pretty simmilar to a regular dsl connection, so
there is nothing scary about it =)

                Alberto



<Prev in Thread] Current Thread [Next in Thread>