From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] iproute2 is not routing
Date: Sun, 24 Mar 2002 10:40:57 +0000 [thread overview]
Message-ID: <marc-lartc-101696656927694@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101696074924194@msgid-missing>
> At this point, all I want to do is route between
> these interfaces. So far all I can do is ping the
> linux-router from the devices on the various
> segments. But I cannot reach devices on the other
> side of the linux-router.
>
> i.e., From a host on the inside-net, I can ping
> every interface on the linux-router. But I cannot
> ping a host on the other side of the linux-router.
> And if sourcing from the linux-router, I am able
> to ping everything.
>
> The routes appear to be correct as far as I can
> tell. I've even turned off the firewalling
> (iptables) to see if that was the problem, but it
> was not.
>
>
>
> What am I missing?
Is the default gateway ok? It points to 192.168.1.1 which is on a private
LAN connected to eth2.
And if you want to ping from the lan to internet, you will need to do SNAT
(masquerading). You need a rule like this :
iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
If you do not do that, the host on the internet sees a package from
192.168.x. and does not know where it can find that host.
> Is there a way to 'debug' like in a cisco router?
You can use tcpdump. Or an iptables rule with -j LOG and see what appears in
the logs.
> [prompt]# ip ro
> 192.168.2.0/24 dev eth1 proto kernel scope link src 192.168.2.150
> 192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.150
> 123.4.5.0/22 dev eth0 proto kernel scope link src 123.4.5.6
> default via 192.168.1.1 dev eth2 proto static src 192.168.1.150
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-03-24 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-24 9:06 [LARTC] iproute2 is not routing Kelly Scroggins
2002-03-24 10:40 ` Stef Coene [this message]
2002-03-24 14:51 ` Kelly Scroggins
2002-03-24 15:19 ` Stef Coene
2002-03-24 15:48 ` Kelly Scroggins
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-101696656927694@msgid-missing \
--to=stef.coene@docum.org \
--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.