Brad Macpherson wrote:
> Lenard wrote:
>
>
>>Grant Nosbush wrote:
>>
>>
>>>I've been working on this for hours and haven't gotten very far so I'm
>>>hoping someone can help me out. I'm trying to setup a basic network
>>>at my home with the following configuration:
>>>
>>>DSL Modem
>>> |
>>> |
>>>Linux Box
>>> |
>>> |
>>>Wireless Hub
>>> | \
>>>Computer #1 Computer #2, etc
>>>
>>>The linux box has two NIC cards, one for the DSL modem and one for the
>>>wireless hub. The DSL model has a built in DHCP server and the linux
>>>box connects fine with address 10.0.0.3. I also setup a DHCP server
>>>on the linux box for eth1 (the card connected to the wireless hub) and
>>>have
>>> gotten the wireless hub to connect to the linux box. The computers
>>>connects to the wireless hub and I'm able to ping the linux box. The
>>>problem is I can't access the internet from computers 1, 2, etc. Is
>>>there another component I'm missing on the linux box? I have the ip
>>>address for eth1 (linux box to wireless) set at 192.168.1.0. The
>>>gateway in the dhcp server is also set at 192.168.1.0 for the wireless
>>>hub to use. Can anyone offer any ideas or suggestions as to how to
>>>finish this so I can get this to work? Thanks for your help.
>>
>>http://www.tldp.org/HOWTO/IP-Masquer...WTO/index.html
>>
>>
>
>
> Another tip would be that 192.168.1.0 is not a valid IP address for your
> machine - are you sure you don't mean 192.168.1.1 or 192.168.0.1?
(all 0's and all 1's as the host part of an IP address have special
meaning and should be avoided.)
Have you tried accessing the Internet from the Linux box, nslookup/host,
ping, lynx, wget etc just to make sure the links up and running properly.
If the Internet connection is working then the next step is to work out
how you want to foward traffic from your local LAN to the Internet.
Basic options are NAT/Masquerade or Proxy.
NAT basically passes all your LAN traffic through to the Internet but
changes the source address to you public Internet address rather than
your private LAN address. Generally done with iptables on Linux. The
advantage to this method is that it will handle pretty much any protocol
(with the possible exception of active ftp connections and other
protcols that assign inbound ports dynamically).
Proxying runs a server on the Linux box which accepts requests then
re-issues them. The benefit is that the request/results can be
manipulated (content/virus scanned etc). Done on a per protocol basis
and used mainly for web access.
If you're a relative beginner you might want to take a look at IPCop
(
http://ipcop.org/) or Smoothwall (
http://smoothwall.org/). Both are
firewall distributions with NAT & Proxying already built in. They
provide a boot iso image to get you up & running (careful - they both
wipe your hard drive as part of their install). The also have a web
based admin screen. If nothing else they will give you a good
understanding of what goes into a firewall type system and how its put
together.
B.