public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andrew B. Cramer" <andrew.cramer@cramer-ts.com>
To: linux-kernel@vger.kernel.org
Subject: routing & ipchains
Date: Wed, 25 Apr 2001 00:55:40 -0500	[thread overview]
Message-ID: <3AE6208C.8379.146C84FE@localhost> (raw)

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.

---------Route with ppp0 up----------------
Destination     Gateway         Genmask         Flags Metric Ref    
Use Iface
205.243.155.100 0.0.0.0         255.255.255.255 UH    0      0        0 
ppp0
192.168.0.0     0.0.0.0         255.255.255.128 U     0      0        0 
eth1
192.168.0.128   0.0.0.0         255.255.255.128 U     0      0        0 
eth0
192.168.0.0     192.168.0.1     255.255.255.0   UG    0      0        0 
eth1
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
0.0.0.0         205.243.155.100 0.0.0.0         UG    0      0        0 
ppp0
0.0.0.0         192.168.0.1     0.0.0.0         UG    0      0        0 eth1
0.0.0.0         192.168.0.130   0.0.0.0         UG    0      0        0 eth0
-------------------End of Route Table------------------

TIA - if other files are needed, I can forward.

Best - Andy

Andrew B. Cramer - <andrew.cramer@cramer-ts.com>
Cramer Technical Services - <www.cramer-ts.com>
Linux Resource Exchange - <www.linuxrx.com>

             reply	other threads:[~2001-04-25  5:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-25  5:55 Andrew B. Cramer [this message]
2001-04-25 12:42 ` routing & ipchains Rusty Russell
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=3AE6208C.8379.146C84FE@localhost \
    --to=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