* [LARTC] Forcing return route
@ 2002-01-11 4:41 Michael T. Babcock
0 siblings, 0 replies; only message in thread
From: Michael T. Babcock @ 2002-01-11 4:41 UTC (permalink / raw)
To: lartc
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/
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2002-01-11 4:41 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-01-11 4:41 [LARTC] Forcing return route Michael T. Babcock
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.