All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Giannis Stoilis" <giannis@stoilis.gr>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Making packets be reflected in a router
Date: Thu, 19 Jun 2003 07:55:00 +0000	[thread overview]
Message-ID: <marc-lartc-105600941631876@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105488833321519@msgid-missing>

----- Original Message ----- 
From: "BALU Frédéric" <frederic.balu@cegetel.fr>
To: <lartc@mailman.ds9a.nl>
Sent: ÐÝìðôç, 19 Éïõíßïõ 2003 10:20 ðì
Subject: [LARTC] Making packets be reflected in a router


> Hello,
>
>  I use a debian 2.2 server, with 2 ethernet cards.
>
>  For a course, I need to make packets from 192.168.1.0/24 to
192.168.2.0/24
> go through eth0:0(192.168.1.254), another internal IP, again another
> internal then out to 192.168.2.0/24 by eth1:0 (192.168.2.254/0).
>
>  Any idea on how to do this (I know this is NOT the mechanism a router may
> apply ...) ?
>
> eth0   : 192.168.1.1
> eth0:0 : 192.168.1.254
> eth0:1 : 192.168.3.254
> eth0:2 : 192.168.5.254
> eth1   : 192.168.2.1
> eth1:0 : 192.168.2.254
> eth1:1 : 192.168.3.254
> eth1:2 : 192.168.5.254

How many times are you going to send this e-mail, until you realize that
people in here don't know the answer? Anyways...
What you are trying to do, is somewhat impossible.
You CANNOT route traffic inside a linux box, between aliased interfaces. You
could, using some old kernels, but this feature was removed from the kernel
long ago. I remember seeing a patch somewhere but, if I remember correctly,
it us outdated.
Besides, when a subnet is connected directly on an interface, it is
automatically using a metric of 0, which automatically overrides any routing
command you may give. Any routing command uses the metric of 1 and above.
I wonder what EXACTLY were you supposed to do for the course, to imagine the
configuration you mentioned. I am curious...

- Giannis Stoilis

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

      parent reply	other threads:[~2003-06-19  7:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-06  8:30 [LARTC] Making packets be reflected in a router BALU Frédéric
2003-06-10  7:38 ` BALU Frédéric
2003-06-11  5:16 ` BALU Frédéric
2003-06-11  6:32 ` BALU Frédéric
2003-06-16 17:56 ` [LARTC] " BALU Frédéric
2003-06-19  7:20 ` BALU Frédéric
2003-06-19  7:55 ` Giannis Stoilis [this message]

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-105600941631876@msgid-missing \
    --to=giannis@stoilis.gr \
    --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.