Re: routing & ipchains

From: Rusty Russell (rusty@rustcorp.com.au)
Date: Wed Apr 25 2001 - 07:42:27 EST

Next message: Mark Hahn: "Re: #define HZ 1024 -- negative effects"
Previous message: Tim Jansen: "Re: /proc format (was Device Registry (DevReg) Patch 0.2.0)"
In reply to: Andrew B. Cramer: "routing & ipchains"
Next in thread: james rich: "Re: routing & ipchains"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Next message: Mark Hahn: "Re: #define HZ 1024 -- negative effects"
Previous message: Tim Jansen: "Re: /proc format (was Device Registry (DevReg) Patch 0.2.0)"
In reply to: Andrew B. Cramer: "routing & ipchains"
Next in thread: james rich: "Re: routing & ipchains"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Mon Apr 30 2001 - 21:00:14 EST