All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Williams <chris.williams@ehbas.com>
To: lartc@vger.kernel.org
Subject: [LARTC] ip rule problems ...
Date: Tue, 11 Jun 2002 12:29:13 +0000	[thread overview]
Message-ID: <marc-lartc-102379864319494@msgid-missing> (raw)

Please forgive me if this seems like a foolish enquiry but I can't get
my iproute2 to work.

Here's my ip tables

#ip rule ls
0:	from all lookup local 
32765:	from all iif eth0 lookup pixforward2 
32766:	from all lookup main 
32767:	from all lookup default 

#ip route ls table pixforward2
default via 212.74.13.1 dev eth1  proto static 

#ip route ls table main
212.74.13.0/30 dev eth1  proto kernel  scope link  src 212.74.13.2 
192.168.1.0/24 dev eth2  proto kernel  scope link  src 192.168.1.2 
192.168.1.0/24 dev ipsec0  proto kernel  scope link  src 192.168.1.2 
192.168.200.0/24 dev eth0  proto kernel  scope link  src 192.168.200.2 
default via 212.74.13.1 dev eth1 

What I'm trying to do is get packets appearing on eth0 to default to
212.74.13.1 and other traffic to default to 192.168.1.1. I want to do
this by changing the default route on the main table to 192.168.1.1.

The problem is that when I remove the default via 212.74.13.1 line from
the main table, nothing gets routed to the outside world anymore. I
thought packets would come in from eth0 leap to the pixforward2 table
and then out onto the internet, but no. I think I know that the packets
are hitting the pixforward2 table, because if I change its route to
nonsense everything stops working. So do the packets appear to choose
the right table initially and then go to the wrong table for actual
routing?

This is even more frustrating because I did get this to work at one
point. When I went to add the changes permenatly to a script, I couldn't
replicate it.

Thanks for any help you can offer, 
Chris.





This e-mail message is meant solely for the person or organisation to whom it is adressed. If you receive this email in error please do not distribute, further publish or relay upon it but let us know (telephone +44 (0)1273 234 664) and then delete it. Please treat our information in confidence as you would hope we would treat yours. Any views expressed are not necessarily those of Ehbas Limited. Thank you for your co-operation. 
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

                 reply	other threads:[~2002-06-11 12:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-102379864319494@msgid-missing \
    --to=chris.williams@ehbas.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.