From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] marking in OUTPUT --mangle; locally generated packets
Date: Sun, 13 Jul 2003 21:43:48 +0000 [thread overview]
Message-ID: <marc-lartc-105813268317351@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105775061617177@msgid-missing>
I tested your setup and it works fine (with 2.5 though). Are you sure
you have
CONFIG_IP_ROUTE_FWMARK enabled for your running kernel ? ip rule won't give
errors if not ..
Bye
Patrick
lartc@manchotnetworks.net wrote:
>hello all,
>
>i have come accross a curious issue:
>
>+----------------------+ +---------------+
>| eth1 192.168.1.1 |------------| 192.168.1.250 |
>| eth1:1 192.168.1.101 | | |
>+----------------------+ +---------------+
>
>
>iptables --append OUTPUT --table mangle --jump MARK --set-mark 0x2
>ip rule add fwmark 0x2 table 2
>ip route add 192.168.1.0/24 dev eth1 src 192.168.1.101 table 2
>ip route flush cache
>
>
>telnet 192.168.1.250 ; and tcpdump gives src ip address as 192.168.1.1
>
>
>ip rule add to 192.168.1.250 table 2
>ip route flush cache
>
>
>telnet 192.168.1.250 ; and tcpdump gives src ip address as 192.168.1.101
>
>
>
>are there issues concerning the marking of OUTPUT packets generated on
>the local box that i should be aware of?
>
>
>many, many thanks
>
>charles
>
>
>
>
>_______________________________________________
>LARTC mailing list / LARTC@mailman.ds9a.nl
>http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2003-07-13 21:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 11:38 [LARTC] marking in OUTPUT --mangle; locally generated packets and route lartc
2003-07-13 21:43 ` Patrick McHardy [this message]
2003-07-15 7:59 ` [LARTC] marking in OUTPUT --mangle; locally generated packets lartc
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-105813268317351@msgid-missing \
--to=kaber@trash.net \
--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.