All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin A. Brown" <mabrown-lartc@securepipe.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] problem in routing
Date: Tue, 12 Nov 2002 16:19:41 +0000	[thread overview]
Message-ID: <marc-lartc-103711807028401@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103711402622386@msgid-missing>

 : Ok..
 : i've done that without success.
 : Please watch that the routing is made in the router machine and the
 : marking is made in the linux box before and because of that it doesn't
 : matter where i mark the packets.

Ah, now I understand!  But it does matter, tremendously.

I didn't perceive in your previous post that you had two hosts.  Perhaps I 
was being dense.

The "fwmark" is a field on the packet which only exists in the data 
structure used to represent the packet on a single machine.  In short, the 
fwmark does not survive a single machine.  As soon as the packet is 
transmitted, the fwmark is lost.

You could use the mangle table with the TOS target and then change your ip
rule to route based on ToS.  I'm unsure of the implications for your
network, but this is a possible solution.  If you modify the ToS on the 
packet, this will be visible to other hosts.

Good luck,

-Martin

 : Thanks anyway
 : Nuno Fernandes
 : 
 : On Tue, 2002-11-12 at 15:51, Martin A. Brown wrote:
 : > Hello Nuno,
 : > 
 : > I'd suggest s/POSTROUTING/PREROUTING/ here:
 : > 
 : >  : iptables -t mangle -A POSTROUTING -d SOME.IP.IN.INTERNET -j MARK
 : >  : --set-mark 21
 : >  : 
 : >  : In my ROUTER i want to redirect packets according to MARK and i'm doing:
 : >  : 
 : >  : root@euroter(~)# more /etc/iproute2/rt_tables 
 : >  : 255	local
 : >  : 254	main
 : >  : 253	default
 : >  : 200	over
 : > 
 : > Consult Stef Coene's kernel packet traveling diagram, which should 
 : > explain (visually) why you want to mark the packet before the routing 
 : > stage.
 : > 
 : >   http://www.docum.org/stef.coene/qos/kptd/
 : > 
 : >  : root@euroter(~)# ip route ls table over
 : >  : default via XXX.XXX.XXX.XXX dev eth1
 : >  : 
 : >  : where XXX.XXX.XXX.XXX is the gateway of the provider 1.
 : >  :
 : >  : Doing ip rule ls, i can see that all packets with mark 21 go to table
 : >  : over.
 : >  : root@euroter(~)# ip rule ls 
 : >  : 0:	from all lookup local 
 : >  : 32765:	from all fwmark       21 lookup over 
 : >  : 32766:	from all lookup main 
 : >  : 32767:	from all lookup default 
 : > 
 : > Naturally, the RPDB (displayed with "ip rule show") is consulted as part 
 : > of the routing process.
 : > 
 : > So, in short, your host euroter is doing as follows:
 : > 
 : >   - routing the packet
 : >   - marking the packet
 : >   - transmitting via provider2
 : > 
 : >  : And table over only has default gw, but when i do a
 : >  : ping XXX.XXX.XXX.XXX it goes throw proveider2 and not provider1.
 : > 
 : > Good luck,
 : > 
 : > -Martin
 : 

-- 
Martin A. Brown --- SecurePipe, Inc. --- mabrown@securepipe.com



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

  parent reply	other threads:[~2002-11-12 16:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-12 15:13 [LARTC] problem in routing Nuno Miguel Pais Fernandes
2002-11-12 15:51 ` Martin A. Brown
2002-11-12 16:13 ` Nuno Miguel Pais Fernandes
2002-11-12 16:19 ` Martin A. Brown [this message]
2002-11-12 17:53 ` Nuno Miguel Pais Fernandes

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-103711807028401@msgid-missing \
    --to=mabrown-lartc@securepipe.com \
    --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.