> >Hubs go "poof" far less often than PCs running Linux.
I agree... if you really want guaranteed uptime, then just make
everything redundant. I.e., extra NICs, extra hubs/routers, and lots of
extra wires, and take the hardware out of the equation. That's still
going to be cheaper than buying a
> >Hubs go "poof" far less often than PCs running Linux.
I agree... if you really want guaranteed uptime, then just make
everything redundant. I.e., extra NICs, extra hubs/routers, and lots of
extra wires, and take the hardware out of the equation. That's still
going to be cheaper than buying
>Hubs go "poof" far less often than PCs running Linux.
I have to whole heartedly agree with Russell on this. I have been running a
handful of el cheapo 4 and 8 port hubs here for years and the only failure
in thousands of hours of use was loseing a BNC port on 2 from a lightning
strike on the thi
On Sun, 27 Aug 2000, Peter Billson wrote:
>I am trying to avoid using a hub (hub goes *poof* neither machine can
>talk to the Net) to connect 2 internal machines to the net through a
Hubs go "poof" far less often than PCs running Linux.
>Linux box configured as a router. The box has three NIC car
Put box 2 on 192.168.3.X instead. I suspect you have box 1 & box 2 setup with
a subnet mask that makes them think they are on the same subnet and so ARP
for the address locally instead of passing the traffic to your router.
Matt.
On Sun, 27 Aug 2000 03:23:01 Peter Billson wrote:
> I am trying
>Hubs go "poof" far less often than PCs running Linux.
I have to whole heartedly agree with Russell on this. I have been running a
handful of el cheapo 4 and 8 port hubs here for years and the only failure
in thousands of hours of use was loseing a BNC port on 2 from a lightning
strike on the th
On Sun, 27 Aug 2000, Peter Billson wrote:
>I am trying to avoid using a hub (hub goes *poof* neither machine can
>talk to the Net) to connect 2 internal machines to the net through a
Hubs go "poof" far less often than PCs running Linux.
>Linux box configured as a router. The box has three NIC ca
Put box 2 on 192.168.3.X instead. I suspect you have box 1 & box 2 setup with
a subnet mask that makes them think they are on the same subnet and so ARP
for the address locally instead of passing the traffic to your router.
Matt.
On Sun, 27 Aug 2000 03:23:01 Peter Billson wrote:
> I am trying
Someone may have a better idea, but how about using ipchains to set up
forwarding? Seems like you need your router box to forward stuff
destined for eth1 from eth2 to eth1, and visa versa.
Don't take this as gospel . . . I'm fighting ipchains right now
so, "when all you have is a hammer, all pr
I am trying to avoid using a hub (hub goes *poof* neither machine can
talk to the Net) to connect 2 internal machines to the net through a
Linux box configured as a router. The box has three NIC cards as
follows:
eth0 - 192.168.1.6 connection to my Internet gateway (192.168.1.1)
eth1 - 192.168.2
Someone may have a better idea, but how about using ipchains to set up
forwarding? Seems like you need your router box to forward stuff
destined for eth1 from eth2 to eth1, and visa versa.
Don't take this as gospel . . . I'm fighting ipchains right now
so, "when all you have is a hammer, all p
I am trying to avoid using a hub (hub goes *poof* neither machine can
talk to the Net) to connect 2 internal machines to the net through a
Linux box configured as a router. The box has three NIC cards as
follows:
eth0 - 192.168.1.6 connection to my Internet gateway (192.168.1.1)
eth1 - 192.168.
12 matches
Mail list logo
