From: Jon <jon_webb@binary-one.com>
To: Pablo Cingolani <pcingola@uolsinectis.com>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ip_route_me_harder question...
Date: Wed, 26 Nov 2003 12:19:34 -0800 [thread overview]
Message-ID: <3FC50AD6.7080105@binary-one.com> (raw)
In-Reply-To: <20031126121031.67a8265e.pcingola@uolsinectis.com>
This is a good question. I've noticed that sometimes it's needed and
sometimes it isn't. We implemented a routing protocol where all the
packets were bumped up to userspace and after fiddling with the routing
system for a long time, we ended up using some code from iproute2 to
change the table before reinjecting the packet (unmodified). This
alleviated our route_me_harder() issues. But another protocol we were
looking at during our implementation used route_me_harder() and it
seemed to work fine. Very confusing.
Regards,
Jon Webb
Computer Communications Research Group
University of California at Santa Cruz
Pablo Cingolani wrote:
>Refered to a question posted by "Zeeshan Ali <zeelists@yahoo.com>" a couple of days ago, I've suggested him to
>use ip_route_me_harder after changing a packet's saddr/daddr (at NF_IP_PRE_ROUTING).
>I've noticed that it doesn't work because after the hook changes the packet, ip_rcv_finish() calls
> skb->dst->input(skb) which seems to setted to something like 'dst_discard' (instead of 'ip_forward()' which is
>what I was expecting).
>Can someone give me a hint on what is wrong / what should be done to (correctly) change the routes
>so that the packet is forwarded?
>Thank you
> Pablo
>
>P.S.: Packet's saddr is changed to a local one.
>
>
>
next prev parent reply other threads:[~2003-11-26 20:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 15:10 ip_route_me_harder question Pablo Cingolani
2003-11-26 20:19 ` Jon [this message]
2003-11-26 21:18 ` Zeeshan Ali
-- strict thread matches above, loose matches on Subject: below --
2009-01-07 17:19 Giant Sand Fan's
2009-01-12 5:18 ` Patrick McHardy
2009-01-12 9:43 ` Giant Sand Fan's
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=3FC50AD6.7080105@binary-one.com \
--to=jon_webb@binary-one.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=pcingola@uolsinectis.com \
/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.