lkml.org 
[lkml]   [2000]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Linux 2.2 - BSD/OS 4.1 ARP incompatibility
Rogier Wolff wrote:

> Hmm. Doesn't the spec say something about that you should preferrably
> use the "closest" IP number that you can find to communicate with a
> host?
>
> Yes, adding a route to "a.b.c.1 gw d.e.f.1" on the BSD box should
> work.
>
> But having a multi-homed host with a.b.c.1 on one side and d.e.f.1 on
> the other, then I'd expecit it to use d.e.f.1 to communicate with
> d.e.f.2, even if both are physically on the same ethernet.

Then as we say, set up routing properly. Specify the correct source to be used
on a route rather than the implicit primary interface address.

ip r a d.e.f.0 dev int0 src d.e.f.1, and assuming the .0 represents the network,
all traffic destined to this network not having an explicit source will get
assigned the route source and appear as d.e.f.1 on the wire.

-d

--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."


begin:vcard
n:Ford;David
x-mozilla-html:TRUE
org:<img src="http://www.kalifornia.com/images/paradise.jpg">
adr:;;;;;;
version:2.1
email;internet:david@kalifornia.com
title:Blue Labs Developer
x-mozilla-cpt:;28256
fn:David Ford
end:vcard
\
 
 \ /
  Last update: 2005-03-22 12:38    [W:0.090 / U:8.384 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site