From: "Michael T. Babcock" <mbabcock@fibrespeed.net>
To: lartc@vger.kernel.org
Subject: [LARTC] Forcing return route
Date: Fri, 11 Jan 2002 04:41:36 +0000 [thread overview]
Message-ID: <marc-lartc-101072412819328@msgid-missing> (raw)
Is there a way to force responses to go out on the interface the
request came in on?
I have a situation where an incoming IPSEC packet (for FreeS/WAN) is
being received on eth0 but being responded to on ipsec0 because of a
route that stays up too long. I can't fix the route problem easily;
can I force a response to go out on eth0 when the request was received
on eth0 though?
On second thought, it occurs to me that there is no way for the Linux
network code to know which packet the response packet relates to.
Perhaps the tearing down of the route based on the incoming packet
would be most appropriate?
Thank-you for your help.
--
Michael T. Babcock
CTO, FibreSpeed Ltd. (Hosting, Security, Consultation, Database, etc)
http://www.fibrespeed.net/~mbabcock/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
reply other threads:[~2002-01-11 4:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-101072412819328@msgid-missing \
--to=mbabcock@fibrespeed.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.