advice for cache server,
Hello everyone, Im On FreeBSD 6.2R, I run radius and chillispot, sure my fbsd is the gateway. The internet start to be slow due the increase of the users on my lan. I was thinking to install a cache server, that would be easy and simple, even for my users, is the squid proxy server enough for this mission? any other recommendations? does it require my users to change thier browser configuration to proxy.domain.com or it will auto detect? One more thing, what is the best way to limit the bandwidth download ? some users are sucking the connection by using softwares such as imesh and many others.. Thank you. Marwan _ FREE pop-up blocking with the new MSN Toolbar - get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Cache server
Hi all, We're deploying a couple of dedicated Freebsd 6.2 servers using Squid. I remember being at the BSDCan 2006 and Poul-Henning was talking about Varnish. Was wandering if anyone deployed it since no one talks about it on the list, and if it is worth installing it as a production cache server. Thanks BSD Networking, Microsoft Notworking ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
DNS Cache Server
Noticed the tread on a caching DNS server, and that brought up a couple of questions I had. I have a DNS server set up in my home. I have a FreeBSD 5.2.1 box acting as my gateway, running ipfw and natd. It routes my one static IP address from my DSL provider to a set of internal, unroutable IPs. That part is working fine. Also on that box is a caching DNS server. The internal IP for the gateway is 192.168.0.1. My problems are two fold, and may or may not be related. 1) I cannot, from either the gateway or any of the internal machines, get DNS query responses from 192.168.0.1. I can get query responses from 127.0.0.1 and the external IP address from the gateway, and I can get query responses from the external IP from any of the internal machines (well, partially. See below). 2) When I do set up my FBSD 5.3 box inside the network with the external IP of the gateway in resolv.conf, I can ping and nslookup DNS names just fine. However, when I go to use Mozilla (Or any browser for that matter), they hang on Resolving host:. nslookup tells me it is using my gateway as the DNS server, and never tells me it's switching to another server for queries. Any ideas? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: DNS Cache Server
On 11/9/2004 4:01 PM NiY wrote: Noticed the tread on a caching DNS server, and that brought up a couple of questions I had. I have a DNS server set up in my home. I have a FreeBSD 5.2.1 box acting as my gateway, running ipfw and natd. It routes my one static IP address from my DSL provider to a set of internal, unroutable IPs. That part is working fine. Also on that box is a caching DNS server. The internal IP for the gateway is 192.168.0.1. My problems are two fold, and may or may not be related. 1) I cannot, from either the gateway or any of the internal machines, get DNS query responses from 192.168.0.1. I can get query responses from 127.0.0.1 and the external IP address from the gateway, and I can get query responses from the external IP from any of the internal machines (well, partially. See below). 2) When I do set up my FBSD 5.3 box inside the network with the external IP of the gateway in resolv.conf, I can ping and nslookup DNS names just fine. However, when I go to use Mozilla (Or any browser for that matter), they hang on Resolving host:. nslookup tells me it is using my gateway as the DNS server, and never tells me it's switching to another server for queries. Any ideas? Are you running some sort of packet filter? If you are, I'd try turning it off and then see if you still have problems. If you do, then you know that you need to modify your rules to allow the traffic through the internal interface. HTH, Drew -- Visit The Alchemist's Warehouse Magic Tricks, DVDs, Videos, Books, More! http://www.alchemistswarehouse.com smime.p7s Description: S/MIME Cryptographic Signature
Re: DNS Cache Server
On 11/9/2004 4:01 PM NiY wrote: Noticed the tread on a caching DNS server, and that brought up a couple of questions I had. I have a DNS server set up in my home. I have a FreeBSD 5.2.1 box acting as my gateway, running ipfw and natd. It routes my one static IP address from my DSL provider to a set of internal, unroutable IPs. That part is working fine. Also on that box is a caching DNS server. The internal IP for the gateway is 192.168.0.1. My problems are two fold, and may or may not be related. 1) I cannot, from either the gateway or any of the internal machines, get DNS query responses from 192.168.0.1. I can get query responses from 127.0.0.1 and the external IP address from the gateway, and I can get query responses from the external IP from any of the internal machines (well, partially. See below). 2) When I do set up my FBSD 5.3 box inside the network with the external IP of the gateway in resolv.conf, I can ping and nslookup DNS names just fine. However, when I go to use Mozilla (Or any browser for that matter), they hang on Resolving host:. nslookup tells me it is using my gateway as the DNS server, and never tells me it's switching to another server for queries. Any ideas? Are you running some sort of packet filter? If you are, I'd try turning it off and then see if you still have problems. If you do, then you know that you need to modify your rules to allow the traffic through the internal interface. HTH, -- Visit The Alchemist's Warehouse Magic Tricks, DVDs, Videos, Books, More! http://www.alchemistswarehouse.com -- I am using ipfw, and am not deying anything on the internal network. I do some filtering on traffic coming into the gateway from the external IP, but nothing on any of the internal IPs. What I'm denying inbound shouldn't have anything to do with DNS, either. Just to be sure, I did set the default type to open and used a blank ipfw config, but that didn't help any. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
