All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jose Sebastiao Martins <tiao@int.efoa.br>
To: lartc@vger.kernel.org
Subject: [LARTC] Routing
Date: Wed, 30 Oct 2002 12:57:41 +0000	[thread overview]
Message-ID: <marc-lartc-103598645426838@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98373940416816@msgid-missing>

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

Hi all,

I'm new to iproute2 and iptables. It's a very simple topology:



world--a.b.c.d--|router|--x.y.z.10--x.y.z.8--|linux+iptables|
                                                             |
                                                        172.16.0.1
                                                             |
                                                            / \
                                                           / HUB
                                               linux1=172.16.0.200

I can ping  x.y.z.8 from privite net linux1 or $windows but not
the router interface x.y.z.10.
Here are my settings:

ip ro sh
200.179.120.0/23 dev eth1  scope link
172.16.0.0/16 dev eth0  scope link
127.0.0.0/8 dev lo  scope link
default via 200.179.120.10 dev eth1

ip ru sh
0:      from all lookup local
32766:  from all lookup main
32767:  from all lookup 253

If I try:
ip route add 172.16.0.0/16 via 200.179.120.10
ip route add 172.16.0.0/16 via 200.179.120.8
I get
File exists

I'm already setting the rules. For now it's completly open.
iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
ACCEPT     all  --  anywhere             anywhere           state 
RELATED,ESTABLISHED
ACCEPT     all  --  anywhere             anywhere
LOG        all  --  anywhere             anywhere           LOG level warning

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination


Please, what I'm missing?

TIA
Jose Sebastiao Martins
tiao@int.efoa.br



[-- Attachment #2: Type: text/plain, Size: 167 bytes --]


---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.404 / Virus Database: 228 - Release Date: 15/10/02

  parent reply	other threads:[~2002-10-30 12:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-03 11:13 [LARTC] routing Spyros
2001-01-03 12:37 ` David
2001-01-05 12:25 ` Junus
2001-01-05 12:33 ` Junus
2001-07-06 14:03 ` [LARTC] Routing Dave Miller
2001-07-06 15:01 ` Arthur van Leeuwen
2001-07-06 15:18 ` Dave Miller
2001-07-07  6:33 ` Deepak singhal
2001-07-07 18:24 ` Arthur van Leeuwen
2001-07-07 18:33 ` Dave Miller
2001-07-07 18:37 ` Arthur van Leeuwen
2001-12-25  4:58 ` [LARTC] routing Daniel Wittenberg
2001-12-25 12:16 ` bert hubert
2002-10-30 12:57 ` Jose Sebastiao Martins [this message]
2002-10-30 15:57 ` [LARTC] Routing 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-103598645426838@msgid-missing \
    --to=tiao@int.efoa.br \
    --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.