Text 4543, 47 rader
Skriven 2005-11-23 17:23:09 av Russell Tiedt (5:7105/1)
   Kommentar till text 4537 av Maurice Kinal (1:261/38.9)
Ärende: Protecting a 2 Gig ADSL c
=================================
Hello Maurice.

21 Nov 05 21:33, you wrote to me:

 MK> Just use the 233 on the backplane as a dhcp server for the LAN and
 MK> then base access to the DSL connection on whatever you want it too,
 MK> say a MAC address.  If a different MAC address then what you configure
 MK> into the dhcp server then don't give them an address which will
 MK> prevent neighbour's machines from getting out.  Also if that
 MK> particular machine you plan to masquerade for has exceeded some sort
 MK> of predetermined quota, then don't give them an ip address either.
 MK> Without that then they aren't going anywhere without learning how to
 MK> hack, and given Windows I doubt very much they would know how let
 MK> alone have the tools needed.  Windows boxes being crippled are really
 MK> easy to control as far as access to any network interface(s) goes.
 MK> Piece of cake.  Also I'd use iptables to control masquerading for
 MK> anything on any particular interface on the router.  Works great even
 MK> for linux boxes.

Using the 233 on the backplane has just moved a step closer to being possible, 
as I have just come into possesion of a IDE-CFDisk adapter. I don't have any 
HDD's I can use with with that 233, none small enough for the BIOS to handle, 
and anything to big, locks the BIOS up solid. :-(( Another thing, I don't have 
any memory sticks larger than 16MB, and as that board only can accept 2xmemory 
sticks, that gives me 32M which should be enough, but I figure 64MB would be 
much better.

Problem is, I want the machines on the network, to be networked, but be able 
to limit their internet access only, ie. they must still be able to play games 
etc. across the network, but without internet access. That should keep them 
happy, busy and keep them from causing to much problems. If you take away all 
their toys, then they are inclined to get up to all sorts of un-needed 
mischief. :-)

Not that your suggestion does not have appeal. :-))

 MK> ttylinux is what you need on the router but also with the addition of
 MK> dhcp so that the router can decide if and what gets an ip address and
 MK> whether or not that particular ip address gets anywhere beyond the lan
 MK> it's on.  Piece of cake.  :-)

ttylinux, has distict possibilities in the above problem/solution. <VBG>

Russell

--- GoldED+/LNX 1.1.5
 * Origin: Rusty's BBS - Bloemfontein, Free State, South Africa (5:7105/1)