From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Erik S. Johansen" Date: Mon, 10 Apr 2006 09:17:46 +0000 Subject: Re: [LARTC] Conntrack, nat and multipath - what is wrong here? Message-Id: <200604101217.51641.lists@sperling.no> MIME-Version: 1 Content-Type: multipart/mixed; boundary="===============1970125519==" List-Id: References: <200604092142.47556.lists@sperling.no> In-Reply-To: <200604092142.47556.lists@sperling.no> To: lartc@vger.kernel.org --===============1970125519== Content-Type: multipart/signed; boundary="nextPart12192674.4hIJqi8c3P"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart12192674.4hIJqi8c3P Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline As a side note, if I put both dsls on eth2 and use the same ruleset, things= =20 start working. I still need that default route in the main table though. =2D-E.S. Johansen --nextPart12192674.4hIJqi8c3P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1-ecc0.1.6 (GNU/Linux) iD8DBQBEOiK/ds9m9uhAobARAkoFAJ46+VYbW+kxtTaIfXjGBZMAn/pI1gCgsyKB 0pV/N7KdynbEEaor7njC6ns= =8omz -----END PGP SIGNATURE----- --nextPart12192674.4hIJqi8c3P-- --===============1970125519== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc --===============1970125519==--