On Sun, 2003-04-06 at 19:02, Frank Sorenson wrote: > On Sun, 6 Apr 2003, David Smith suggested we build a large wooden badger: > > I am running a Debian firewall for my local network. It is NAT/Masq'ing > > connections to the outside world and running DansGuardian/Squid. Pretty > > cool. I run some essential network services like Squid, Apache, Exim, > > etc, that I would like to only be available to the internal network > > (192.168.2.*). My external network card has a puclically routeable IP > > address. In httpd.conf, I was able to make Apache bind to the private > > IP, and that made it so that Apache is only visible to the internal > > network, just like I want. However, is there a global way to do this > > (without the use of iptables)? I ask because I can't find a place to do > > the same thing in Exim, Squid, or DansGuardian config files. > > > > --Dave > > You may be able to do some of this through tcpwrappers. Do "man > hosts.allow" and "man hosts.deny" for information on those. > > To configure squid to only respond to some hosts, look into configuring > acls in the /etc/squid/squid.conf file: > acl davenet src 192.168.2.0/255.255.255.0 > http_access allow davenet > > I haven't configured exim or DansGuardian, so I couldn't say anything > about how they operate. Doesn't DansGuardian get called as a > redirect_program from squid? If that's the case, you can probably just > configure squid.
Actually, DansGuardian calls Squid. I already locked down Squid to only accept connections from localhost with an acl. That's fine, but it still listens on port 8080. I'd like to make it not show up when I nmap it at all. I guess this is a per-application deal, agreed? --Dave ____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
