All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lluís Batlle" <viriketo@gmail.com>
To: netfilter@lists.netfilter.org
Subject: Re: Problem with routing decisions, and multihop (solved)
Date: Tue, 5 Jul 2005 09:46:29 +0200	[thread overview]
Message-ID: <45219fb005070500469fee3c9@mail.gmail.com> (raw)
In-Reply-To: <45219fb00507042252343deced@mail.gmail.com>

Argh. Stupid me..............
The tables 201 and 202, who decide the route for packets with already
defined source addres were in the rules that way:
The routing rules are:
0:      from all lookup local
50:     from all lookup main
201:    from 192.168.17.0/28 iif eth2 lookup 201
202:    from 192.168.16.0/28 iif eth1 lookup 202
222:    from all lookup 222
32766:  from all lookup main
32767:  from all lookup default

Look at the terrible "iif ethx"!!!!!!!!! The packets were routed _at
random_ by the 'equalizing routing decision', even if with decided
address. Argh.
Solution: there should not be "if ethx" in the routing rule matching

Now it works.

Even though, I'd prefer to get the Julian's patches working. When I
try them, all packets go to the same interface (the first hop). I'll
keep on working...

Always, always, there is the deadly "user fault". :)))

Thanks for your support!


      reply	other threads:[~2005-07-05  7:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-04 14:15 Problem with routing decisions, and multihop Lluís Batlle
2005-07-04 14:21 ` Lluis Batle
2005-07-04 14:32 ` Lluis Batle
2005-07-04 15:07   ` /dev/rob0
2005-07-04 15:10     ` /dev/rob0
     [not found]       ` <45219fb005070408323197bfa4@mail.gmail.com>
2005-07-04 15:32         ` Lluis Batle
2005-07-04 16:33           ` /dev/rob0
2005-07-04 16:54             ` Lluís Batlle
2005-07-04 18:06               ` /dev/rob0
2005-07-05  5:52                 ` Lluís Batlle
2005-07-05  7:46                   ` Lluís Batlle [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=45219fb005070500469fee3c9@mail.gmail.com \
    --to=viriketo@gmail.com \
    --cc=netfilter@lists.netfilter.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.