FYI, you need to connect the WAN/Internet port of Router 2 to a LAN port of Router 1.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Can I have a network within a network?
- Thread starter macgrl
- Start date
- Sort by reaction score
FYI, you need to connect the WAN/Internet port of Router 2 to a LAN port of Router 1.
router 2 only has lan ports, it has a dsl input port but the ethernet cable is too big. tc has 3 lan and one port with a little circle above it which i presume is wan
when i go to the settings in tc there is an option to "connect to a network using ethernet to extend the network or create a second network" which is what i want so I click on that and then select "i want to create an additional network" but when it comes to the finish it just says none of the tc settings have been changed from what they were and so nothing changes.
ok so i have got it to change the settings but now tc just has a constant amber light and doesn't show up as a network or as a network drive
ok so i have got it to change the settings but now tc just has a constant amber light and doesn't show up as a network or as a network drive
Fixed it. How cool is that. I now have my own little network. yay.
I have set it with wpa2 personal security so i am presuming that it will be the same as any other network with security settings. No one will be able to access it without permission
I have set it with wpa2 personal security so i am presuming that it will be the same as any other network with security settings. No one will be able to access it without permissionFixed it. How cool is that. I now have my own little network. yay.
Anyone have any thoughts on potential double NATing? I have never experienced an issue personally but I have been told that some services on lan (2) might experience some issues NATing through 2 routers? I believe most people that experience issues are playing games etc.
Anyone have thoughts?
It comes down to addressing and the subnet mask.
Run the main eithernet to the Belkin router's wan port and then run a cable from the Belkin to the Time Capsule's wan port. You can set the Time Capsule to only allow certain MAC addresses to connect as I remember. The Belkin should be on a certain subnet (say 10.100.100.x) and the Time Capsule should be setup for a 'New Network' and work on a different subnet like say 10.100.200.x. You could also set the Time Capsule up with another IP address range too if you wanted (like 192.168.x.x). It can use NAT and DHCP to handle access and addressing.
This kind of thing is done all the time... You do not want to bridge the connection as you would lose control on who/what connects.
A separate network needs a distinct networking address scheme and DHCP to make it easier to maintain. Then with NAT (Network Address Translation) the actual connection to the internet is managed. The Belkin provides an address to the Time Capsule and supports NAT-ing the internet connection conneting to it and the Time Capsule provides addresses to the devices that connect to it and provides NAT-ing to connect through it to the Belkin. They have to have a dissimilar enough network address scheme to avoid overlap. If you connect the Time Capsule to the Belkin through the Time Capsule's lan port, things aren't going to work like you want it to and it's a common mistake. Clear as mud?
Run the main eithernet to the Belkin router's wan port and then run a cable from the Belkin to the Time Capsule's wan port. You can set the Time Capsule to only allow certain MAC addresses to connect as I remember. The Belkin should be on a certain subnet (say 10.100.100.x) and the Time Capsule should be setup for a 'New Network' and work on a different subnet like say 10.100.200.x. You could also set the Time Capsule up with another IP address range too if you wanted (like 192.168.x.x). It can use NAT and DHCP to handle access and addressing.
This kind of thing is done all the time... You do not want to bridge the connection as you would lose control on who/what connects.
A separate network needs a distinct networking address scheme and DHCP to make it easier to maintain. Then with NAT (Network Address Translation) the actual connection to the internet is managed. The Belkin provides an address to the Time Capsule and supports NAT-ing the internet connection conneting to it and the Time Capsule provides addresses to the devices that connect to it and provides NAT-ing to connect through it to the Belkin. They have to have a dissimilar enough network address scheme to avoid overlap. If you connect the Time Capsule to the Belkin through the Time Capsule's lan port, things aren't going to work like you want it to and it's a common mistake. Clear as mud?
IF the address scheme is separate enough, it will work. When you try to do overlays on the same addresses is where the trouble comes in. That and mixing up the ports. The second (and subsequent routers/AP's) MUST see the earlier network as a 'WAN'. Each layer MUST have a different address range for DHCP, and then obviously must have NAT enabled (usually by default).
I've seen networks where the AP's are all connected via their LAN ports and then people wonder why things don't work. You should only have ONE DHCP server per address range. I've worked on networks that had two and that made things an instant mess... (I've seen some pretty Rube Goldberg fixes in my day for bad setup decisions)
Apple's 'extend an existing network' basically turns off NAT and DHCP. Creating a new network uses NAT and DHCP and then the first network has to be on the WAN port. I connect through an Airport Extreme connected to another network. I actually have three AP's due to the size and construction of my house (freaking rebar and thick concrete walls). All are connected through their WAN ports to the main switch and all give different addresses via DHCP and NAT their own address ranges. Everything works great. Today's 'easy to use' networking equipment makes it easy to misconfigure your network...
It's not applicable in this case but you have to be aware that there is a limit for the 'hops' that a network connection can go through. You don't want to put to many layers or to many network routers between your computer and the internet... Each layer, depending on how it functions can add to a lag time and create a 'pinch point' in the connection speed also depending on how many devices connect to it and what they are doing/how much bandwidth they are using. That might be a concern depending on how the layers of the network are used. The farther from the main Internet connection you are in the layers, you might get less bandwidth (a measure of capacity/capability)...