[wplug] @home : SETUP

[John-the chicken slayer-Harrold]

On Thu, 22 Feb 2001, Dr.SDM wrote:

> Hope this helps....
> I got it to work not on @home but my dedicated T-line, however watch
yourself, so you don't loose $
> But remember if you open a port....anyone can get into it...
                                     ^^^^^^^^^^^^^^^^^^^^^^
actually useing the ipchains (in 2.2) and ip tables in (2.4) you can block
ports based on the source of the request. so you can say that only subnet
.xxx.xxx.xxx has access to port 21. this is done at the kernel level so
when someone tries to connect to port 21 and they are not on an approved
subnet the kernel will reject the request. this will make it appear as
though there is no server running on that port. if you are on the approved
subnet then it will let you through as though there is nothing strange
going on. 

that is the advantage over tcp wrappers. if you have tcp wrappers
setup and you try to connect from an unauthorized host you can still see
the server running. you still cannot connect. 

at least that is my understanding of how it works.

john