All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Ahlberg" <aliz@telia.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Routing based on source port - Solution ?
Date: Fri, 19 Apr 2002 14:11:03 +0000	[thread overview]
Message-ID: <marc-lartc-101922555728697@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101922226325230@msgid-missing>


> I have the same problem and tried all possibities i know.
>
> "ip rule" in fact doesnt route based on port because
> IP protocol dont know about ports. BUT u can solve the problem
> by using iptables/ipchains with help of MARKs - as u said.
>
> Unfortinuatly netfilter can only set MARKs in the moment the
> packets travers the INPUT Queue (of corresponding interface).
>
> -->
> netfilter is not able to set mark for _local_ created packets,
> because the INPUT Queue of netfilter is not passed.
>
> => In fact the MARK mechanism can only be used for incoming packets.
>
> In my scenario i would like to do port based routing on local sockets
> i cannot use the MARK feature at all. :(
>
>
> I dont know of any other method to solve the problem.
> Any other solutions ??

I too have encountered problems with the marking of packets. When I mark
packets destined to port 80 using iptables and dump the traffic using
tcpdump I can see the packet coming into the local interface (eth0) and
leaving the external interface (eth1), getting a reply from the website I'm
trying to visit on eth1 but the reply isnt sent to my computer on the local
interface. I am however using old versions of iptables (1.2.2) and iproute
(20001007) and I have yet to try out a newer version of both iproute and
iptables


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

  reply	other threads:[~2002-04-19 14:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-19 13:18 [LARTC] Routing based on source port - Solution ? Tobias
2002-04-19 14:11 ` Daniel Ahlberg [this message]
2002-04-19 15:31 ` Greg Scott
2002-04-19 15:34 ` Adrian Chung
2002-04-19 18:59 ` Tobias

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-101922555728697@msgid-missing \
    --to=aliz@telia.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.