Liam Campbell wrote:
Let me explain my setup before I go into any details
I have a squid proxy with network A(192.168.1.0) connecting through eth1
and network B(172.16.29.0) connecting through eth2.
the Interface going out to the internet is eth0. The Proxy had been
working just fine when only network A was connected however I needed to
add network B to the mix. Installed the card, added new network to the
acl and brought the interface up. Now when I try connecting to anything
with my client machines on either network I either get Connection
Refused(error received from squid) or the Connection Times out. When I
drop eth2 so network B is no long connected network A is again able to
connect. So my question is what would be causing this and how can I
fix/get around it. At the moment I have no iptables rules in affect. I
have Squid 3.0 installed.
I reflexively think ... With what settings?
http_port
acl
http_access
But on re-reading. You may be having issues with routing. Check the IPs
assigned to the interfaces, and the routes, particularly the default
route are not being affected.
Do requests sent through NIC B get to the Internet properly? Sounds a
bit like that is being attempted somehow.
Also, maybe the router for network 192.168.*.* is firewalling 172.*.*.*
outside your box. If squid is somehow grabbing one of those IPs from the
system on send that could be an issue.
Also, on the rare chance, do you have SELinux or something doing nasty
magic behind your back?
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE14
Current Beta Squid 3.1.0.7
