From: Geoff Crompton <geoffc@trinity.unimelb.edu.au>
To: whiplash <whiplash@bofhland.org>
Cc: netfilter@vger.kernel.org
Subject: Re: ip rule fwmarks letting me down
Date: Fri, 09 May 2008 11:57:42 +1000 [thread overview]
Message-ID: <4823AF96.1010107@trinity.unimelb.edu.au> (raw)
In-Reply-To: <4822F740.4070400@bofhland.org>
whiplash wrote:
> Geoff Crompton wrote:
>
>> So when I ping from a machine behind this firewall, it should be routed
>> via 203.28.240.92, but it isn't. I've been running tcpdump on both
>> 203.28.240.92 and 203.28.240.91, and the packets are definately being
>> routed via 203.28.240.91.
>
> Did you
> ip route flush cache
> before testing?
No, but I have now, and it made no difference. From my perspective, it
looks like a failure in the routing policy database, so I'm not suprised
that an 'ip route' command didn't change the situation. (However I know
nothing about the code internals, so I'm happy to conceed the point if
someone knows better).
BTW, how long do route caches last?
--
+-Geoff Crompton
+--Debian System Administrator
+---Trinity College
prev parent reply other threads:[~2008-05-09 1:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 5:58 ip rule fwmarks letting me down Geoff Crompton
2008-05-08 12:51 ` whiplash
2008-05-09 1:57 ` Geoff Crompton [this message]
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=4823AF96.1010107@trinity.unimelb.edu.au \
--to=geoffc@trinity.unimelb.edu.au \
--cc=netfilter@vger.kernel.org \
--cc=whiplash@bofhland.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox