Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: "Rimas" <rmocius@auste.elnet.lt>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iproute2 and Kernel 2.6
Date: Fri, 19 Dec 2003 07:53:24 +0000	[thread overview]
Message-ID: <marc-lartc-107182225828638@msgid-missing> (raw)
In-Reply-To: <marc-lartc-107175697326945@msgid-missing>

Hi,

I use iproute2_now_ss020116_try-i386-4 which comes with Slackware 9.1 (what
I use it for my linux boxes).
These commands work just fine with kernel 2.4.x but not with 2.6.x.

IF1=eth1
IP1=xxx.xxx.xxx.xxx
P1=xxx.xxx.xxx.xxx
P1_NET=xxx.xxx.xxx.xxx/32

IF2=eth0
IP2=xxx.xxx.xxx.xxx
P2=xxx.xxx.xxx.xxx
P2_NET=xxx.xxx.xxx.xxx/29

# One creates two additional routing tables.
# Then you set up routing in these tables as follows:

ip route add $P1_NET dev $IF1 src $IP1 table T1
ip route add default via $P1 table T1
ip route add $P2_NET dev $IF2 src $IP2 table T2
ip route add default via $P2 table T2

# Next you set up the main routing table.
ip route add $P1_NET dev $IF1 src $IP1
ip route add $P2_NET dev $IF2 src $IP2

# Then, your preference for default route:
ip route add default via $P1

# Next, you set up the routing rules. These actually choose what routing
table to route with. You want to
# make sure that you route out a given interface if you already have the
corresponding source address:
ip rule add from $IP1 table T1
ip rule add from $IP2 table T2


# This set of commands makes sure all answers to traffic coming in on a
particular interface get answered
# from that interface.

# Lotus Notes server 10.105.105.196 goes via eth0
ip rule add from 10.105.105.196 table notes
ip route add default via $P2 dev eth0 table notes

# Virtual HTTP server 10.105.105.201 goes via eth0
ip rule add from 10.105.105.201 table http1
ip route add default via $P2 dev eth0 table http1

# local VPN server 10.105.105.20 goes via eth0

ip rule add from 10.105.105.20 table vpnsrv
ip route add default via $P2 dev eth0 table vpnsrv


# local smtp
iptables -t mangle -A PREROUTING -i eth2 -s 10.105.105.198 -p tcp --dport
25 -j MARK --set-mark 0x950

ip rule add fwmark 0x950 table localsmtp
ip route add default via $P2 dev eth0 table localsmtp


# local VPN clients and ssh out

# PPTP
iptables -t mangle -A PREROUTING -i eth2 -s 10.105.105.0/24 -p tcp --dport
1723 -j MARK --set-mark 0x960
iptables -t mangle -A PREROUTING -i eth2 -s 10.105.105.0/24 -p 47 -j
MARK --set-mark 0x960

# ssh
iptables -t mangle -A PREROUTING -i eth2 -s 10.105.105.0/24 -p tcp --dport
22 -j MARK --set-mark 0x960

ip rule add fwmark 0x960 table localvpn
ip route add default via $P2 dev eth0 table localvpn
------------------------------------------------------------------


I tried to recompile"iproute2" against current (2.6.0) kernel sources, but
it does not help.

Remus






----- Original Message ----- 
From: "Ben Efros" <ben-ra@efros.com>
To: <lartc@mailman.ds9a.nl>
Sent: Thursday, December 18, 2003 4:46 PM
Subject: Re: [LARTC] iproute2 and Kernel 2.6


> Can you please tell us the version of iproute2, how you are making the
> routing decisions (ie, what commands are you using?).
>
>
> ----- Original Message ----- 
> From: "Remus" <rmocius@auste.elnet.lt>
> To: <lartc@mailman.ds9a.nl>
> Sent: Thursday, December 18, 2003 5:47 AM
> Subject: [LARTC] iproute2 and Kernel 2.6
>
>
> Hi folks,
>
> I have a linux box with three NICs (two for external ISP, and one local).
> Today I tried to use 2.6.0 kernel and somethings is wrong because iproute2
> does not work corretly.
> No routed packets go via second ISP NIC. With 2.4.22 kernel I have no
> problems at all with packet routing.
>
> I compiled 2.6.0 kernel myself, maybe I missed something in .config file?
>
> Thanks
>
> Remus
>
>
>
> "Slackware Linux - Simplicity is Divine."
>
>
> BACKUP IMPORTANT DATA !
>
> This is the most important thing !
> Remember that all damages done to your system is at your own risk !
> Always important when you are running Bill Gates Windows ;-)
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
>

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

      parent reply	other threads:[~2003-12-19  7:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-18 13:47 [LARTC] iproute2 and Kernel 2.6 Remus
2003-12-18 16:46 ` Ben Efros
2003-12-18 20:00 ` Jose Luis Domingo Lopez
2003-12-19  7:53 ` Rimas [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-107182225828638@msgid-missing \
    --to=rmocius@auste.elnet.lt \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox