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] 2 router on one server web
Date: Thu, 22 May 2003 15:25:27 +0000	[thread overview]
Message-ID: <marc-lartc-105361721007184@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105361408702941@msgid-missing>

Hello Michele,

 : |194.243.12.15 (eth0)   SERVER WEB (eth1) 194.184.12.85 |
 :                                            adsl2
 :                                            194.184.12.81

So, you have a server with two ADSL connections.
                  +-----------------------------------+
194.243.12.1 -----| 194.243.12.15  SRV  194.184.12.85 |----- 194.184.12.81
             eth0 +-----------------------------------+ eth1


You are handling the inbound packets properly, but if you were to use
tcpdump on eth0, you'd see reply packets (to your ping) leaving on eth0
with a source address of 194.184.12.85.

This is not an uncommon thing to overlook when dealing with routing
systems--there is a path in to the box, and you have correctly identified
how to handle that, but you need to tell the box how to send the outbound
packet.

 : #for f in /proc/sys/net/ipv4/conf/*/rp_filter; do echo 0 > $f; done

Yes, you need to do this!

 : #echo 1 > /proc/sys/net/ipv4/route/flush

This is equivalent to "ip route flush cache", and should be performed
after altering the routing tables or the RPDB.

 : #iptables -A PREROUTING -i eth1 -p -t mangle -j MARK --set-mark 1

 : and iproute:
 : #echo 201 ruteradsl2 >>/etc/iproute2/rt_tables
 : #ip rule add fwmark 1 table  routeradsl2
 : # ip rule ls
 : 0:      from all lookup local
 : 32765:  from all fwmark        1 lookup routeradsl2
 : 32766:  from all lookup main
 : 32767:  from all lookup default
 : # /sbin/ip route add default via 194.184.12.81 dev eth1 table routeradsl2

Try adding the following:

# ip rule add from 194.184.12.85 lookup routeradsl2

If you want to see another full example, please consult the section on
multiple Internet connections in the linux-ip.net documentation.

  http://linux-ip.net/html/adv-multi-internet.html

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/

  reply	other threads:[~2003-05-22 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 14:33 [LARTC] 2 router on one server web Michele
2003-05-22 15:25 ` Martin A. Brown [this message]
2003-05-27 12:39 ` Michele
2003-05-27 13:28 ` Martin A. Brown

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-105361721007184@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.