All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tarek W." <ticallion@terra.net.lb>
To: lartc@vger.kernel.org
Subject: [Fwd: Re: [LARTC] 2 internal NIC's in the same network]
Date: Tue, 26 Nov 2002 07:25:49 +0000	[thread overview]
Message-ID: <marc-lartc-103829554501394@msgid-missing> (raw)

-----Forwarded Message-----

> From: Tarek W. <tarek@cyberia.net.lb>
> To: lartc@mailman.ds9a.nl
> Subject: Re: [LARTC] 2 internal NIC's in the same network
> Date: 26 Nov 2002 09:12:33 -0200
> 
> 
> ur deliverance is by way of echo 1 > /proc/sys/net/ipv4/conf/eth{1,2},
> that's what everybody says...however, this is not the whole story, ur
> tryina setup two ips on the same subnet on two separate interfaces... in
> simple routing, the first route to match is taken... so the traffic goes
> out the first interface regardless of the source ip... u need to look
> into source-based routing or "policy routing". read the iproute2 docs.
> 
> On Mon, 2002-11-25 at 11:14, virdzek, roman wrote:
> > hi,
> > i have two internal nics
> > 
> >             at PC1
> >                  
> >     eth1                 eth2
> > 10.0.0.1               10.0.0.2
> > 
> >             |              |
> >             switch 
> >                  |
> >               pc2
> >               eth0
> >             10.0.0.3       
> > 
> > 
> > 
> > 
> > and when I ping from pc2 -> PC1:eth2,
> > using tcpdump i see that PC1
> > send reply to (arp who has 10.0.0.2),
> > 10.0.0.2 is at .....eth1.
> > why PC1 send back not proper HW address?
> > how I can force PC1 to say that 10.0.0.2
> > is at eth2?
> 



_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2002-11-26  7:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-26  7:25 Tarek W. [this message]
2002-11-26  7:35 ` [Fwd: Re: [LARTC] 2 internal NIC's in the same network] Tarek W.
2002-11-27 11:54 ` virdzek, roman
2002-11-28 12:35 ` Tarek W.

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-103829554501394@msgid-missing \
    --to=ticallion@terra.net.lb \
    --cc=lartc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.