Subject: per-interface default routes
To: None <tech-net@NetBSD.ORG>
From: Michael C. Richardson <mcr@sandelman.ottawa.on.ca>
List: tech-net
Date: 03/11/1998 09:20:52
-----BEGIN PGP SIGNED MESSAGE-----


  Ted, awhile ago you said you might do some patches to allow a per-interface
default route --- i.e. a TCP connection that came in on one interface would
send its packets out the same interface.
  Two questions:
	1. did you ever do this for NetBSD?
	2. will an application be able to pick its outgoing interface
	by bind(2) its socket before it connect(2)s?

  I have two internet connections: one gives me useful addressing, and
appropriate business AUP, the other just gives me personal-use bandwidth
(Wave@Home). I want to put a web cache on my firewall that will do #2 above
to use the cable bandwidth instead of my ISDN bandwidth for HTTP. 

   :!mcr!:            |  Sandelman Software Works Corporation, Ottawa, ON  
   Michael Richardson |Network and security consulting and contract programming
 Personal: mcr@sandelman.ottawa.on.ca. PGP key available.
 Corporate: sales@sandelman.ottawa.on.ca. 




-----BEGIN PGP SIGNATURE-----
Version: 2.6.3ia
Charset: latin1
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface

iQB1AwUBNQadwtiXVu0RiA21AQGvZAMAipfQgER1T03slryLqwM7uzbAJqKtuE+O
ngeeEtlMjFGFpt+CfgMPD6JuqjvLUXb1i0BPjXX/Q49qFLlz7el/L1BeDe4Wa8VS
8xY1WJLdQIUQwGcl7z8ikKCTg3fKkdcE
=qWak
-----END PGP SIGNATURE-----