this is probably not even a squid issue... probably a LAN setup issue. but i'd be grateful for any help from the gurus out there.
i have set up squid w/ squidguard on a redhat 8.0 linux box (call it box A).
i have another linux RH 8.0 machine (call it box B) that im using to test with. it sits on the same LAN. i set the web browser to use A as it's proxy w/ the default squid port.
i have shutdown iptables on both machines (just for now). as far as i know this is the only firewall software running on them.
i have a linksys broadband router that connects the two machines (basically a hub for our purposes, except that squid does go out through it to accesss external stuff)
obviously this is not the final setup. eventually A will act as the router/proxy/filter for the network and the linksys will go away.
if i use a browser on A, w/ the proxy info set, squid seems to work just fine. when i use the browser on B, things go awry. it just sits there and times out.
i used ethreal to track what was going on. here's what i see from A...
TCP packet from B (port 1409) to A (squid port) SYN TCP packet from A (squid) to B (1409) SYN, ACK TCP packet from B (1409) to A (squid) RST ! (repeat ad nausium)
here is what i see from B...
TCP packet from B (1409) to A (squid) SYN TCP packet from linksys router (squid port) to B (1409) SYN, ACK TCP packet from B (1409) to linksys router (squid port) RST (repeat ad nausium)
there are also a few ARP messages flying around... the router asks for B's MAC, then B asks for A's MAC (with appropriate responses)
why would the TCP source get changed going through the router/hub? it's all internal LAN traffic. is there some way to set this up within my LAN for testing? anyone out there with any hints for me?
thanks.
-mike ([EMAIL PROTECTED])
