All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Artūras Šlajus" <x11@h2o.pieva.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Route P2P on separate link
Date: Mon, 31 May 2004 05:42:51 +0000	[thread overview]
Message-ID: <40BAC5DB.2020301@h2o.pieva.net> (raw)
In-Reply-To: <20040530003837.C0ABA4029@outpost.ds9a.nl>

[-- Attachment #1: Type: text/plain, Size: 899 bytes --]

Mihai Vlad wrote:
> Hello,
> 
> Is there a way to route p2p traffic on a separate ISP connection, just as
> you would choose a separate connection for http traffic?
> 
> I tried all sorts of setups based on:
> http://www.braindump.dk/en/wiki/?wikipage=PolicyRouting but with no luck.
> 
> Please help :)
> 
> (ipp2p is up and running)
you should MARK your packets in PREROUTING -t mangle, then identify them 
in iproute2 with fwmark. It's simmilar to this:

table_syn=mytable
$IPT -t mangle -I PREROUTING -i $LAN \
-m multiport -p udp --dports $INET_LOWLAT_UDP_PORTS -j MARK \
--set-mark 1
$IPT -t nat -I POSTROUTING -s $LAN_NET -o $INET_LOWLAT -j MASQUERADE
ip rule del fwmark 1 lookup $table_syn &> /dev/null
ip rule add fwmark 1 lookup $table_syn
ip route del table $table_syn &> /dev/null
inet_lowlat_gw=192.168.22.22
ip route add default via $inet_lowlat_gw dev $INET_LOWLAT table \ $table_syn

[-- Attachment #2: x11.vcf --]
[-- Type: text/x-vcard, Size: 250 bytes --]

begin:vcard
fn;quoted-printable:Art=C5=ABras =C5=A0lajus
n;quoted-printable;quoted-printable:=C5=A0lajus;Art=C5=ABras
email;internet:x11@h2o.pieva.net
tel;cell:+37068958733
x-mozilla-html:FALSE
url:http://h2o.sky.lt/
version:2.1
end:vcard


      reply	other threads:[~2004-05-31  5:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-30  0:08 [LARTC] Route P2P on separate link Mihai Vlad
2004-05-31  5:42 ` Artūras Šlajus [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=40BAC5DB.2020301@h2o.pieva.net \
    --to=x11@h2o.pieva.net \
    --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.