This was apparently the heart of the problems I was having. I
originally connected two separate NICs to the same switch because I had
a need for two zones (loc and dmz) and only one switch. The
documentation for /etc/shorewall/hosts made it sound like something I
shouldn't try, and NICs are c
At 11:04 AM 10/30/02 -0500, Christopher Audley wrote:
[...]
Heres another thing I've noticed, the problem will appear separately for
each client. On the DMZ I have two machines, A and B. A can't ping the
Bering, but if I ping A from the Bering, after the first few packets it
works. After thi
Thanks for the responses.
The Bering router is replacing a machine that was doing double duty as a
file server and NAT router for the rest of the network to a DSL link.
Previously the file server had three IP addresses, on one NIC it had an
external address for itself and one for the rest of
> I've put together a router using Bering rc4, but it has a strange
> startup issue. Once the router is up and running, if I try and ping
it
> from a machine on the interior network, it won't respond. However, if
I
> try and ping from the router to the machine on the network, the first
> four pac
That must be a negotiation issue.
Try to force duplex and 10/100 settings.
How is your network setup?
-Original Message-
From: Christopher Audley [mailto:Christopher.D.Audley@;jhu.edu]
Sent: Wednesday, October 30, 2002 6:35 AM
To: [EMAIL PROTECTED]
Subject: [leaf-user] Strange network
I've put together a router using Bering rc4, but it has a strange
startup issue. Once the router is up and running, if I try and ping it
from a machine on the interior network, it won't respond. However, if I
try and ping from the router to the machine on the network, the first
four packet fa
