Troubles with incoming/outgoing address, dns.

Hi.

  I have a linux 2.1.xxx box running squid (2.0 / 2.1) for intranet
consisting of > 250 workstations and 230kbps internet connection (2*115.2
CSLIP). This box has one network devise (eth0 - IP for example 10.0.0.1)
and IP alias (eth0:1 - IP for example 10.0.0.2), based on eth0. Squid
works with three parents (i don't want squid to fetch objects directly).

  I want to force squid to bind to 10.0.0.2 (not use 10.0.0.1) - so here's
part of my squid config:

>tcp_incoming_address 10.0.0.2
>tcp_outgoing_address 10.0.0.2
>#udp_incoming_address 0.0.0.0
>udp_outgoing_address 10.0.0.2

>cache_peer w3cache.org1.foo.com parent 8080 7 weight=10 no-query
>cache_peer w3cache.org2.foo.com parent 8080 7 weight=9 no-query
>cache_peer w3cache.org3.foo.com parent 8080 7 weight=6 no-query

>cache_mem 30 MB

>cache_dir /export/w3cache 2800 32 256

But when i'm watching network traffic on our intenet link (tcpdump) i can
see packets from parents (port: w3cache) to 10.0.0.1. But why? Most of
traffic is OK - directly to 10.0.0.2, but not all.

Second question: how to force squid not to resolve dns names, just forward
client's request to parent? Squid always tries to resolve dns name (using
dnsserver), but i think that in this configuration it is obsolete.

                                with regards
                  ___________ _____
         Maciej Szulc \ / e-mail:
  Student of Computer Science \/ wodzu@pg.gda.pl
Technical University of Gdansk /\
~~~~~~~~~~~~~~~~~~~~~~~~~~~~oooooo~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         Student's hostel nr 2 network administrator
Received on Sun Nov 29 1998 - 13:40:42 MST