From: Rusty Russell <rusty@rustcorp.com.au>
To: andrew.cramer@cramer-ts.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: routing & ipchains
Date: Wed, 25 Apr 2001 22:42:27 +1000 [thread overview]
Message-ID: <m14sOcl-001Q8NC@mozart> (raw)
In-Reply-To: Your message of "Wed, 25 Apr 2001 00:55:40 EST." <3AE6208C.8379.146C84FE@localhost>
In message <3AE6208C.8379.146C84FE@localhost> you write:
> Greetings All,
> After upgrading from kernel 2.0.38 w/ slackware-3.4 to
> kernel 2.2.16 w/ slackware-7.1 I have developed the following
> routing problems.
>
> Hardware -
> eth0 - 10meg on net 192.168.0.0 i/f 192.168.0.1 subnet
> 255.255.255.128
> eth1 - 100meg on net 192.168.0.128 i/f 192.168.0.130 subnet
> 255.255.255.128
>
> >From either network I can use ipchains and surf/telnet/ftp/... on
> each network to the ppp0 dialup connection. I cannot ping or
> anything from eth0 to eth1 or back.
Um, I don't see what this has to do with ipchains, but my guess is:
echo 1 > /proc/sys/net/ipv4/ip_forward
Rusty.
--
Premature optmztion is rt of all evl. --DK
next prev parent reply other threads:[~2001-04-25 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-25 5:55 routing & ipchains Andrew B. Cramer
2001-04-25 12:42 ` Rusty Russell [this message]
2001-04-26 9:18 ` james rich
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=m14sOcl-001Q8NC@mozart \
--to=rusty@rustcorp.com.au \
--cc=andrew.cramer@cramer-ts.com \
--cc=linux-kernel@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