All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin Kellner" <mhkellner@gmx.de>
To: lartc@vger.kernel.org
Subject: [LARTC] iptables+iproute2+squid
Date: Sun, 23 Sep 2001 19:04:14 +0000	[thread overview]
Message-ID: <marc-lartc-100127164126178@msgid-missing> (raw)

[-- Attachment #1: Type: text/plain, Size: 1184 bytes --]

I think this is the right place to ask:

I'm using
- kernel 2.4.9
- iptables as firewall
- iproute2 with rule-based routing.
- squid

two internet-connection:

- 1 ADSL-based link with dynamic ip-adresses
- 1 static isdn-line with fixed ip-adresses

Everything is working but squid isn't. Any idea why? how is the
loopback-traffic handled with my two new tables? Squid uses to work as a
transparent-proxy with all the iptables-stuff. When I'm working with the
normal routing-tables and one internet-connection. Everything is ok.

I use two rules (first for user-browsing, second for mail-traffic):

ip rule add from 192.168.1.128/25 table www.out
ip rule add from 192.168.1.6 table mail.out

# default route is reset to p-t-p-adress of ppp, when ppp comes down again,
because of idle-state
ip route delete default

# this part is done dynamically when ppp comes up
ip route add default via x.x.x.x table www.out
ip route add 192.168.1.0 via y.y.y.y table www.out

# this part is setup with the firewall start
ip route add default via z.z.z.z table mail.out
ip route add 192.168.1.0 via y.y.y.y table mail.out

Thanks in advance

Martin Kellner


[-- Attachment #2: Type: text/html, Size: 1694 bytes --]

             reply	other threads:[~2001-09-23 19:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-23 19:04 Martin Kellner [this message]
2001-09-23 20:07 ` [LARTC] iptables+iproute2+squid Stephane Bortzmeyer
2001-09-26  7:12 ` Martin H. Kellner

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-100127164126178@msgid-missing \
    --to=mhkellner@gmx.de \
    --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.