On 2/6/06, Zhao Peng <[EMAIL PROTECTED]> wrote:
> I heard that it's possible to make A a router, so that I connect B to A via
> a Cat5 cable (not interested in wireless), and then both A and B can get
> online at the same time
A number of people have pointed out that it's often easier to buy a
c
On 2/7/06, Paul Lussier <[EMAIL PROTECTED]> wrote:
> Technically, if all you want to do is turn a system into a router,
> then IPTables is NOT what you want, but rather, something like routed.
Well, *technically*, what routed does is implement various dynamic
routing protocols. You don't *need*
Neil Joseph Schelly <[EMAIL PROTECTED]> writes:
> The way to do this is with IPTables
s/The/One/
Technically, if all you want to do is turn a system into a router,
then IPTables is NOT what you want, but rather, something like routed.
IPTables is technically a sw firewall, which happens to pass
On Mon, 2006-02-06 at 09:50 -0500, Zhao Peng wrote:
> I heard that it's possible to make A a router, so that I connect B to
> A via a Cat5 cable (not interested in wireless), and then both A and B
> can get online at the same time
I think you'll find it simpler to get an inexpensive ethernet rout
The way to do this is with IPTables, the linux firewall facilities, on Machine
A. If you're unfamiliar with how to configure that, I would suggest
installing firestarter on the FC4 machine and that will have an option to use
IPTales, Masquerading (NAT) to allow the second machine out into the w
Hi, all linux experts:I have 2 computers (A & B)A:a desktop (running Fedora Core 4), has 2 ethernet cards. (When I installed Fedora Core 4 on A, I chose "server" among 4 installation types, and I chose DHCP for both ethernet cards.)
One card is connected to a Motorala cable modem via a Cat5 cable.