netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Brendan Cully <brendan@kublai.com>
Cc: netdev@vger.kernel.org
Subject: Re: Question on advanced routing and/or virtual routers.
Date: Sat, 20 Jan 2007 14:41:14 -0800	[thread overview]
Message-ID: <45B29A8A.8010704@candelatech.com> (raw)
In-Reply-To: <20070108182327.GB19417@ventoux.cs.ubc.ca>

Brendan Cully wrote:
> I started something like this a while ago (posted at
> <20051006215312.GD24375@zakopane.cs.ubc.ca> with a couple of replies
> by Thomas Graf, but I can't seem to find it in the archives) but then
> dropped the ball. It seems to work fairly well with a one-line kernel
> patch to allow route lookup before the local address check. Oh, and I
> didn't get traceroute working quite right either - I think there was
> some trick to finding the source address for the generated reply.
>
> I've got some info and code here: http://dsg.cs.ubc.ca/~brendan/remus/
>   
Using your scripts as a starting point,  and the one-liner kernel patch, 
I was able
to get it mostly working as well.  I also see trouble with traceroute 
and agree
that the problem is getting the right source-address in the ICMP and/or 
UDP response
packets.

I'm going to start digging into the kernel to see if there is some way I 
can force the
response out the same interface as it came in from, and also to force 
the source IP
to be the same as the port it is leaving on.

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com> 
Candela Technologies Inc  http://www.candelatech.com



      parent reply	other threads:[~2007-01-20 22:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08 17:08 Question on advanced routing and/or virtual routers Ben Greear
2007-01-08 18:23 ` Brendan Cully
2007-01-10  2:53   ` Ben Greear
2007-01-20 22:41   ` Ben Greear [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=45B29A8A.8010704@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=brendan@kublai.com \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).