From: "Jason Opperisano" <Jopperisano@alphanumeric.com>
To: netfilter@lists.netfilter.org
Subject: RE: Change of ip addresses continues.... :(
Date: Thu, 26 Aug 2004 17:26:07 -0400 [thread overview]
Message-ID: <D5C9032B2B09C64EA2409D6214E91AC90512EE@asimail2.alphanumeric.com> (raw)
> I have been trying various set of rules in various table in order to have packets go over
> the right link. ie. packet's src add should match outgoing link's ip address.YET, there
> are some packets that always tend to go over the wrong link and thus causing ip address
> change. They mostly seem to be ICMP Destination Unreacheable messages or DNS queries.
please verify that the ICMP dest-unreach & DNS queries are not locally generated packets from the firewall machine itself. everything you're doing thus far applies to packets being routed through the firewall; not from the firewall--that's a whole different story...
> I tried out the rules that Daniel Chemko so generously had provided me with...and they
> don't seem to work. I am probably not doing something right. I just tried thefollowing
> rules with no luck:
>
> iptables -t mangle -A PREROUTING -j CONNMARK --restore-mark
> iptables -t mangle -A PREROUTING -m mark ! --mark 0 -j ACCEPT
> iptables -t mangle -A PREROUTING -m mark ! --mark 0 -p icmp -j MARK --set-mark 1
> iptables -t mangle -A PREROUTING -m mark ! --mark 0 -j MARK --set-mark 2
> iptables -t mangle -A PREROUTING -j CONNMARK --save-mark
> iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE
> ptables -t nat -A POSTROUTING -o ppp1 -j MASQUERADE
>
> Are these rules supposed to create 2 routing tables???? If they do, I don't seem them?
> This is what I see:
>
> [ ]# ip rule list
> 0: from all lookup local
> 32766: from all lookup main
> 32767: from all lookup 253
no--iptables commands do not create extra routing tables--you have to do this yourself. hopefully, you've been studying up on http://lartc.org/howto/index.html (specifically http://lartc.org/howto/lartc.netfilter.html)
something like:
echo 500 icmp >> /etc/iproute2/rt_tables
ip rule add fwmark 1 table icmp
ip route add default via $ICMP_LINK dev $ICMP_LINK_IF table icmp
will make the packets marked with "--set-mark 1" (icmp packets in your example), get their default gateway from the alternate routing table named "icmp"
again--this applies to packets being routed through the gateway, not to packets coming from the gateway.
-j
next reply other threads:[~2004-08-26 21:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 21:26 Jason Opperisano [this message]
2004-08-26 21:33 ` Change of ip addresses continues.... :( Eric Leblond
2004-08-26 21:57 ` Odd question with source based blocking Michael Sconzo
-- strict thread matches above, loose matches on Subject: below --
2004-08-26 21:48 Change of ip addresses continues.... :( Daniel Chemko
2004-08-26 21:36 Daniel Chemko
2004-08-26 21:30 Jason Opperisano
2004-08-26 21:10 dravya
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=D5C9032B2B09C64EA2409D6214E91AC90512EE@asimail2.alphanumeric.com \
--to=jopperisano@alphanumeric.com \
--cc=netfilter@lists.netfilter.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