Subject: per-interface default routes
To: None <tech-net@NetBSD.ORG>
From: Michael C. Richardson <email@example.com>
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.
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: firstname.lastname@example.org. PGP key available.
-----BEGIN PGP SIGNATURE-----
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
-----END PGP SIGNATURE-----