I now have iptables up and running, the net connection is shared throughout the house
again!
Between your hints, a couple of files sent my a friend, some issues with the bash
shell, some pam.d issues, and the ip masq howto it is working just fine.
Next few days will try to figure out how to ti
Howdy, Y'all:
Add another ethernet card to one of the 4 computers on the hub.
and it can be your 'server/router/firewall'.
Have the 'server/router/firewall' route from 192.168.0.x<>192.168.1.x.
This doesn't consume additional ports on your hub.
telephone-line -> DSL -> eth0-server/router/firewa
OK. This additional info makes it pretty easy to advise you. (In contrast
to your practice, my responses below follow each item, not precede prior
discussion of it.)
At 09:48 AM 7/1/02 -0700, Alan Womack wrote:
>It's not actually a DSL router, but just a DSL modem capable of being
>hooked to e
It's not actually a DSL router, but just a DSL modem capable of being hooked to
ethernet directly. My current hub only has 4 ports, and all 4 are in use before the
modem arrived. The modem does indeed to nat and uses PPPoA encapsulation for it's VPN
portion from my system to MSN via qwest.
OK. You should be able to do what you want. But we do need to know quite a
bit more.
1. Why do you want to use the Linux host this way? If the DSL router itself
has a /30 netmask on its internal side, that sounds like a DSL modem that
connects multiple computers without any help. The 192.168.
Windows Internet Connection Sharing is giving me fits getting my DSL shared onto my
private home network.
I have 2 network cards in my linux server (redhat 7.2)
Eth0 is set up as 192.168.0.5
Eth1 is set up as 192.168.0.6
My internal network is plugged into Eth1 and I am able to ping all my wi
