> I don't believe I have anything other than the selinux-libs installed, > don't think there is anything running related to them though. The trouble we see a lot of here is the SELinux does a lot of its own magic silently in the background unless you known how to whip it into line properly. I'd seek out an expert on that to check it anyways if we can;t find a simple fix elsewhere. > Here are the settings you were asking about <snip basic config> Okay with that setup squid leaves all IP and routing stuff up to the kernel. It still feels to me like the OS is assigning the outgoing requests with an IP that does not route anywhere useful. It may be time to drag out the packet tracing tools. Amos > > Im wondering if this may be a driver issue, I have three nics in this > machine and the are all using the same driver. may be nothing but I am > looking into that as well > > Liam Campbell, Computer Tech > > Desert Valley Hospital > > 16850 Bear Valley Road > > Victorville, CA 92392 > > (760) 241-8000 x 8727 > > > > "Patience is the companion of wisdom." > > -- Saint Augustine > > > > > > Notice: This e-mail (including attachments) is covered by the Electronic > Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential and may > be legally privileged. If you are not the intended recipient, you are > hereby notified that any retention, dissemination, distribution, or > copying of this communications is strictly prohibited. Please reply to the > sender that you have received the message in error, then delete it. Thank > you. > -----Original Message----- > > From: Amos Jeffries [mailto:squid3@xxxxxxxxxxxxx] > Sent: Wednesday, April 29, 2009 2:13 AM > To: Liam Campbell > Cc: squid-users@xxxxxxxxxxxxxxx > Subject: Re: Getting Connection Refused When Multiple > Interfaces Enabled > > 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 > >
