From: Arindam Haldar <arindamhaldar@inbox.lv>
To: lartc@vger.kernel.org
Subject: [LARTC] Lartc & Squid
Date: Mon, 25 Nov 2002 04:20:26 +0000 [thread overview]
Message-ID: <marc-lartc-103819757613791@msgid-missing> (raw)
hi all,
We are using squid 25s1 with kernel 2.4.19 and iproute2(+julian's
Pathes) with the following acl..
acl short_path dst 128.0.0.0/8
tcp_outgoing_address myIp2nd short_path
we are linked to 2 isp--one having satelite & the other OFC. We want the
above mentioned network to go thru OFC(ispB) as the sibling resides
there. But when i use squidclient mgr:server_list command i see that rtt
is still 650ms which is the time taken by satelite provider(ispA). The
OFC takes 230ms.
On this linux box we have 2 interface linked to different isp & the 3rd
serves our local network.. The rules defined are...
50: from NETB lookup ispB
50: from ofiNetA lookup ispB
50: from ofiNetB lookup ispB
75: from NETA lookup ispA
125: from ofiNetC lookup BALANCE
125: from ofiNetD lookup BALANCE
125: from ofiNetE lookup BALANCE
32766: from all lookup main
32767: from all lookup default
the default is defined in default table & is towards ispA & the other
routes are, ascan be guessed, according to the providers.
My Question is--
what can be done so that squid uses path according to the interface
defined ?
how can local generated packets(on the linux box) uses a path as wanted
by us(in the rules) ?
Awaiting a reply/suggestion/experience from you very anxiously..
A.H
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next reply other threads:[~2002-11-25 4:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-25 4:20 Arindam Haldar [this message]
2002-11-26 17:43 ` [LARTC] Lartc & Squid Vincent Jaussaud
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-103819757613791@msgid-missing \
--to=arindamhaldar@inbox.lv \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.