Re: Openap overclock / behaviour

i think the most easy way to make connection more secutre is to limit ip
adreses who can use it
and dont use dhcp because this way you are inviting everyone to use your
connection

encryption can help but it may be possible to get secret code from one of
your users.

if you disable all unnesecary ip adreses then it will be not possible to get
inside without causing ip adress conflict


----- Original Message ----- 
From: "Lluis" <[email protected]>
To: "Linux Access Point Development" <[email protected]>
Sent: Wednesday, January 21, 2004 8:34 PM
Subject: Re: [LinuxAP-dev] Openap overclock / behaviour


> El 20/01/04, a les 20:45:38, Keith Smith ens deleità amb les
> següents paraules:
> > My experience is not good with this.  One of the boards I
> have
> > actually has a 66Mhz labeled chip on it.  It works fine.  The
> rest
> > seem to get unstable.
> >
> > Further I haven't noticed any major performance increase, this
> thing
> > is so tight on RAM, your best increase is by adding netswap.
> *really*
> > it improves response dramatically when you are (for ex)
> telnetted
> > in.  YMMV.
> >
> > The bogo-mips double from 16 to 32.
> >
> never looked how nbd works, but is the connection tunnelable?
> if it is, could our box afford an encripted tunnel?
> because if you work on plain text connections... well, one malicious
> person could do nasty things with that, right? or am I too paranoid?
>
> read you!
> -- 
>  '"'And it's much the same thing with knowledge, for whenever you learn
>  something new, the whole world becomes that much richer.'"'
>  -- The Princess of Pure Reason, as told by Norton Juster in The Phantom
>  Tollbooth
>
> _______________________________________________
> LinuxAP-dev mailing list
> [email protected]
> http://linuxAP.ksmith.com/mailman/listinfo/linuxap-dev
>