How to configure wifi device and switch

I have the following equipment

-netgear r6300 router
-Netgear ProSafe 24-Port Gigabit JGS524NA

My internet connection terminates in a box that the telecomunications company set up. It has wifi and 4 ports on the back. The problem i'm having is i need more wired ports and the wifi reception is weak and i have many deadspots. I would like to integrate this 24 port switch and the r6300 for its wifi capabilities. I need some clarification on the connection sequence and how to configure this.
glenn_rAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Fred MarshallPrincipalCommented:
There are two ways to do this in general:

Case 1) you can use the NAT in the R6300 Router to preserve your LAN IP addresses.  This is handy if the ISP provides a new interface that uses a different LAN IP address range.  It protects your LAN addresses.  It also might complicate things if you're doing any port forwarding or IPSEC passthrough but perhaps not too much really.

Case 2) you can use the DHCP from the ISP router for your LAN.  This may seem easier in some respects and not in others.

You didn't say anything about guest wireless.

Case 1 approach (see the diagram for Case 1). The diagram has one more cascaded level of routers than you will have.

- Connect the R6300 WAN port to one of the ISP router LAN ports.
Set the R6300 to get its WAN address automatically / via DHCP (from the ISP router).
Set the R6300 LAN address and DHCP range to an "unusual" range like 192.168.44.0/24.  (where the "44" can be anything but should not be "0" or "1" for sure.  The reason for this is that the ISP router may well decide to use:
192.168.0.1/24 or 192.168.1.0/24 or 10.0.0.0/24 or 10.10.10.0/24 .... the "common" ones.
You don't want your LAN range to be the same as the addresses on the R6300 WAN side.  So this should take care of that.
Just remember if you do a hard reset on the R6300 that you will then have to reset it's LAN address - not too likely and totally under your control.
- Turn off the wireless on the ISP router.
- Turn on the DHCP on the R6300 router and set the range and lease time as you'd like them to be.  I suggest 8 hours lease time for an office.
- Turn on the wireless on the R6300 router and set it up as you like.
- Connect the switch to one of the LAN ports on the R6300 router.
- Make all the wired connections to the switch and save the remaining LAN ports on the R6300 as "spare" LAN ports.

Case 2 approach (see the diagram for Case 2)

- Turn off the wireless on the ISP router.
- Connect one of the LAN ports on the R6300 router to a LAN port on the ISP router.
- Give the R6300 a static IP address that matches what the ISP router LAN range and is outside the DHCP range.  Something at the top of the range might be good like xxx.xxx.xxx.254 or .253.  Write it down for future access.
- Turn OFF the DHCP on the R6300 router.
- Turn on the wireless on the R6300 router and set it up as you like.
- Connect the switch to one of the LAN ports on the ISP router.
- Make all the wired connections to the switch and save the remaining LAN ports on the ISP router and on the R6300 router as "spare" LAN ports.
Multiple-Subnets.pdf
Wireless-Router-as-a-Simple-Switch-and-A
0
glenn_rAuthor Commented:
I'll be using this in my home environment. I don't see the number of ports expanding beyond 24. Is one approach better then the other and why?
0
Fred MarshallPrincipalCommented:
Each case has its advantages and disadvantages:

Case 1)

Pro:  Case 1 is handy if the ISP provides a new interface that uses a different LAN IP address range.  It protects your LAN addresses so you don't have to do anything with them in that event because the NAT in your router keeps your LAN addresses intact.  It also gives you the option to "split" your network between two distinct LAN address spaces which may have some benefits re: isolation of one from the other.  For example, you might set up a guest wireless network that's separate from your home LAN.

Con:  Unless the ISP provides a public IP address to your router WAN (which it surely does not if it has mutiple LAN ports and a wireless capability) then there is double NAT.  That is, NAT in the ISP router and NAT in your router.  By itself, this isn't a bad thing.  But, if you need to do port forwarding or IPSEC passthrough then it may be a bit more challenging.

 Case 2)

Pro:  There is no double NAT even though you may well not care about this.  So, some configurations may be simpler if you do have this level of complexity.   Everything is on the same LAN address subnet - which really doesn't amount to much.

Con: You may well not be able to separate the wireless subnets.  That is, if you turn on the ISP router wireless AND use your own router, they will be on the same subnet even if they are on separate channels.  For simple routers without VLAN capabilities, this may eliminate the possibility of a guest network on a separate LAN address range.
Some routers (in this case your R6300) don't like to be set up if there's no internet connection on the WAN.  That may cause a bit of initial confusion but it's usually surmountable.  It's more prevalent in commodity routers that try to provide the user with some "help".

These are fairly fine points and I doubt that it matters that much which one you choose - unless you have the sorts of objectives that I mention.

The simplest setup is to cascade the routers as in Case (1).  It's almost plug and play unless the default subnet address ranges match for both routers.
0
glenn_rAuthor Commented:
Home network
wireless (using 6300)
wired (using switch)
port forwarding for vnc/ftp
0
Fred MarshallPrincipalCommented:
So, in that case, Case 2 might be easier IF you can take care of the port forwards in the ISP router.  And, if you can't then none of these will work.  
With the wireless capability and all, one assumes that you do have access to the ISP router controls.

In Case 1 it's a bit more to do.  You would do the port forwards from the ISP router to the 8300 router WAN address and then do the port forwards in the 8300 to the target computer IP address and port.  The ports need not be the same in every case.
For example:
Let's say you want to forward port 3300 from the outside world to port 2200 at the target computer.
You could forward port 3300 to port 3311 on the 8300.
Then you could forward port 3311 on the 8300 to port 2200 on the target computer IP address.
Of course, it may be simpler to forward Port 3300 to port 2200 and then port 2200 to port 2200 thereafter.
I imagine folks would do 3300 to 3300 in the first router and, next,  3300 to 3300 in the second router and be done with it.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Wireless Networking

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.