On 21.06.2012 00:48, Ton Muller wrote:
> Hello.
> This my setup:
> routerbox openBSD 5.0, squid..(and some other fancy stuff installed)
> webserver is on routerbox on port 80
> Mailserver is a difrent machine, inc webmail access.
> swat for SAMBA is also installed.
> added port 901 to acl list in squid.
Relevance?
> NAMED installed, and correcyt running (serving local names)
> own OS windows7 / ubuntu ,browser, firefox.
>
Right that is your hardware inventory, with a few small hints about
connectivity topology.
How are they connected together?
ie...
is all traffic going through the router box on its way to Squid?
are Squid and client machines on the same sub-net?
are Squid and the servers on the same subnet?
Are they are all on the same company network OR with routing between
such that you can resolve host domain names in DNS and ping any one of
them from the Squid box?
The OR is important here. I've recently had these same problems seen
by someone who tried to place Squid on the cloud and still reach RFC
1918 private IP ranges from the global Internet. The actual destination
IP does not matter to Squid, connectivity configurations to and from it
are paramount.
> i have here a stupid problem.
> i installed squid for a while back, went wel, configed it as it
> should be.
Hmm. Obviously wrong. Since you are having problems.
> works as it should, all sites come over squid in.
>
> however as it come to my lan servers.
> i got each time a timeout when i access my routerbox over squid when
> i
> want to check my webserver, or trying to access swat.
What is the config?
>
> access webmail is not possible when i use name lookup, i must use IP
> adres for it.
Aha. This hints that connectivity is working but your DNS system or
squid configuration is screwed up.
>
> so, my question..
> where did i make a mistake , i used basic squid config, and added
> only
> some ports for access.
What is this squid.conf file?
So far the only clear thing in the above is that you have a few server
machines and Squid seems to be working for clients accessing the public
Internet, but not the LAN.
Amos
Received on Thu Jun 21 2012 - 00:17:22 MDT
This archive was generated by hypermail 2.2.0 : Thu Jun 21 2012 - 12:00:03 MDT