1 |
On 20:44 Sat 04 Mar , Trey Sizemore wrote: |
2 |
> My current home network consists of several PC connected to a Netgear |
3 |
> wireless router (using its default factory IP of 192.168.0.1). It also |
4 |
> serves DHCP address to machines that need it. It, in turn, is |
5 |
> connected to my DSL modem. |
6 |
> |
7 |
> I will be adding a firewall to the mix and plan to use the Netgear |
8 |
> wireless router solely as a hub and WAP. I will disable it's DHCP |
9 |
> serving functionality. |
10 |
> |
11 |
> My questions are: |
12 |
> |
13 |
> a) Given it's new role, will it still require an IP address? If so, it |
14 |
> will be on my internal network (vs. DMZ with servers) and have an |
15 |
> address of 192.168.1.1 for example. Should this be changed now before |
16 |
> I rearrange the configuration? I assume it needs an IP as I will need |
17 |
> to access the web-based admin interface to turn wireless on and off, |
18 |
> etc. |
19 |
> |
20 |
> b) I would assume the WAN port would not be used and all machines |
21 |
> using the "hub" would just plug into one of the four LAN ports. |
22 |
> |
23 |
> c) I have a "true" hub that will be used in the DMZ consisting of |
24 |
> machines with addresses like 192.168.0.x. Here I assume the hub would |
25 |
> *not* have an IP assigned to it. |
26 |
|
27 |
The key, I think, is the capability of your wireless router. Can it act as |
28 |
a bridge? If so, you may have the choice of setting it up with or without |
29 |
an ip address. Normally, you would want it with a ip address, so that you |
30 |
can easily http in and reconfigure it as necessary. |
31 |
|
32 |
If you can set it up as a bridge with an ip address, the address will be on |
33 |
the internal network, 192.168.1.0, not the DMZ network. |
34 |
|
35 |
If you cannot set it up as a bridge, it will need two ip addresses, the |
36 |
"external" address on the DMZ network, and the "internal" network on the |
37 |
192.168.1.0 network. It will then do NAT'ing, which will require you to put |
38 |
a route on your firewall, letting it know where to send the 192.168.1.0 |
39 |
traffic. |
40 |
|
41 |
Good luck |
42 |
|
43 |
Bill Roberts |