From mboxrd@z Thu Jan 1 00:00:00 1970 From: "D Webster" Date: Fri, 13 Jul 2001 11:45:26 +0000 Subject: Re: [LARTC] Multiple Internet Interface Issue MIME-Version: 1 Content-Type: multipart/mixed; boundary="----=_NextPart_000_000D_01C10B56.A2BEF0C0" Message-Id: List-Id: References: In-Reply-To: To: lartc@vger.kernel.org This is a multi-part message in MIME format. ------=_NextPart_000_000D_01C10B56.A2BEF0C0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Destination Gateway Genmask Flags Metric Ref Use Iface 209.26.145.1 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 24.250.85.128 0.0.0.0 255.255.255.128 U 0 0 0 eth2 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 24.250.85.129 0.0.0.0 UG 0 0 0 eth2 #default route 0.0.0.0 209.26.145.1 0.0.0.0 UG 0 0 0 ppp0 #default route These default routes were added automatically when the interfaces are brought up separately. The IP address for ppp0 is 209.26.145.189. If I try to ping 209.26.145.189 from an external machine over the internet, the packets are received, but none are sent. What configuring is needed for data to be sent and received over both interfaces (and retain their source/destination addresses)? Assuming you don't care about sending the data down the shortest path (which would require something like BGP4), configure your kernel for equal cost multipath and then just set both devices as your default route. ------=_NextPart_000_000D_01C10B56.A2BEF0C0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Destination=A0=A0=A0=A0 Gateway=A0=A0=A0=A0=A0=A0=A0=A0 = Genmask=A0=A0=A0=A0=A0=A0=A0=A0 Flags Metric Ref=A0=A0=A0 Use Iface

209.26.145.1=A0=A0=A0 0.0.0.0=A0=A0=A0=A0=A0=A0=A0=A0 = 255.255.255.255 UH=A0=A0=A0 0=A0=A0=A0=A0=A0 0=A0=A0=A0=A0=A0=A0=A0 0 ppp0

24.250.85.128=A0=A0 0.0.0.0=A0=A0=A0=A0=A0=A0=A0=A0 = 255.255.255.128 U=A0=A0=A0=A0 0=A0=A0=A0=A0=A0 0=A0=A0=A0=A0=A0=A0=A0 0 eth2

192.168.0.0=A0=A0=A0=A0 0.0.0.0=A0=A0=A0=A0=A0=A0=A0=A0 = 255.255.255.0=A0=A0 U=A0=A0=A0=A0 0=A0=A0=A0=A0=A0 0=A0=A0=A0=A0=A0=A0=A0 0 eth0

0.0.0.0=A0=A0=A0=A0=A0=A0=A0=A0 24.250.85.129=A0=A0 = 0.0.0.0=A0=A0=A0=A0=A0=A0=A0=A0 UG=A0=A0=A0 0=A0=A0=A0=A0=A0 0=A0=A0=A0=A0=A0=A0=A0 0 eth2 #default route

0.0.0.0=A0=A0=A0=A0=A0=A0=A0=A0 209.26.145.1=A0=A0=A0 = 0.0.0.0=A0=A0=A0=A0=A0=A0=A0=A0 UG=A0=A0=A0 0=A0=A0=A0=A0=A0 0=A0=A0=A0=A0=A0=A0=A0 0 ppp0 #default route

These default routes were added automatically when = the interfaces are brought up separately. The IP address for ppp0 is 209.26.145.189. If I try to ping 209.26.145.189 from an external machine = over the internet, the packets are received, but none are sent. What = configuring is needed for data to be sent and received over both interfaces (and retain their source/destination = addresses)?

Assuming you don't care about sending the data down = the shortest path (which would require something like BGP4), configure your = kernel for equal cost multipath and then just set = both devices as your default route.

------=_NextPart_000_000D_01C10B56.A2BEF0C0-- _______________________________________________ LARTC mailing list / LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/