What's the exact problem? I believe its default behavior is to listen on portHey! I have it working now - it runs in RH 6.2, and both windows machines see no ads now. But I had to use the more insecure method of setting it up (allowing everyone to listen at that address?) with no use of the aclfile, and one line in the config file: listen-address 192.168.100.101:8000
8000 and proxy for anyone who asks.
This method works, but the docs for the program say that it is better to use the aclfile to do it. In the aclfile, I tried using :
permit 0.0.0.0/0 #which should allow all clients to read - it didn't.
permit 192.168.100.101/24 #which should do the same, but tighten security by only recognizing my range - it didn't.
permit 192.168.100.101/24 0.0.0.0/0 #which the docs say should allow all clients on 192.168.100.xxx can read everything (0.0.0.0/0) - it didn't work either.
So I gave up on that, changed config to reflect that listen line (listen-address 192.168.100.101:8000), and everything works fine ...! I knew it would work this way, but didn't want to use that line...
I am kind of new to network security and was concerned, based on the docs, that someone might be able to spoof one of my local boxes on the listening port 8000. I run an IP Spoofing routine in my 'firewall' script in rc.local so I would assume this doesn't concern my situation, and that the proxy is safe to use. I would hope that the use of the ip spoof protection script would restrict anyone from using that open port to do anything but ping back (which won't even happen when I install PortSentry later ;-)) ...
Thanks for the tips Brady, I appreciate it - Maybe your setup is using
the aclfile, and you could tell me what your permit statements look
like... That 'lsof -i tcp:' was new to me - Thanks! One for the notebook...
Now here's a question about the program itself - Couldn't the blockfile
data just be placed inside the hosts.deny file? Eliminating the
need for the program taking up 2.8% of my memory! I wonder if hosts.deny
would relate to what the browser receives....?
Take care,
Mike
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
