A brief aide on the most proficient method to legitimately include a second (or third) switch to a current LAN that as of now has a SOHO switch associated with the web.
The general setup of SOHO Router's is comparative. While some utilization an alternate subnet, each one I've worked with utilizations a Class C Private IP Addressing Scheme. I'm going to utilize the fundamental Class C private for this instructional exercise (192.168.0.0)
I'm going to give two setup guides:
Adaptation 1 will be for a straightforward, single subnet setup
Adaptation 2 will be spread separate subnets
The expression "Router1" will allude to the switch associated with the web. Any others (ie: Router2, Router3) will be downstream of Router1
Version 1:
-----------------
-----------------
When connecting a second router to an existing LAN it’s easiest to connect LAN port to LAN port and configure the LAN side of the downstream router as compared to connecting to the WAN side.
Router1 (LAN Side):
Router1 (LAN Side):
IP: 192.168.0.1
SM: 255.255.255.0
DHCP Enabled = Yes
DHCP Scope: 192.168.0.100 to 192.168.0.199
Router2 (LAN Side):
IP: 192.168.0.2
SM: 255.255.255.0
Default Gateway: 192.168.0.1
DHCP Enabled = No
You will note in the above design that the LAN IP of Router2 is inside the same subnet as Router1 yet is outside of the DHCP Scope characterized on Router1. This is imperative. On the off chance that you utilize an IP inside the degree, the DHCP administration may endeavor to give that IP to another PC you connect to your system. Utilizing an IP outside of the degree stays away from this potential issue. Additionally, gadgets like Routers, Servers, system printers ought to dependably have a statically doled out IP address so that the IP never shows signs of change.
On the off chance that you have everything designed accurately, any PC connected to Router2 will get an IP from the DHCP administration on Router1 and will have full LAN and web availability.
The DHCP Scope's Default Gateway IP location ought to point at Router1 (192.168.0.1) as it is the entryway to the web.
In the event that you have to include another switch, or a few, basically set the LAN IP on Router3 to 192.168.0.3 and arrange all other TCP/IP settings the same as Router2. Do likewise for any others you may include. I might want to bring up, utilizing a switch bodes well than utilizing a switch as a switch requires no setup.
Version 2:
--------------------
When you wish to have a different, and secure, LAN joined to your current system you should isolate the new LAN utilizing an alternate, and separate subnet. Keeping in mind the end goal to do this, and give web availability (without giving network between the two LAN's) you should design your downstream switch (Router2) and use directing to go between subnets. For this situation, you will utilize the WAN port on Router2 to associate with the upstream switch (Router1).
Router1 (LAN Side):
IP: 192.168.0.1
SM: 255.255.255.0
DHCP Enabled = Yes
DHCP Scope: 192.168.0.100 to 192.168.0.199
Router2 (WAN Side):
IP: 192.168.0.2
SM: 255.255.255.0
Default Gateway: 192.168.0.1
Router2 (LAN Side):
IP: 192.168.1.1
SM: 255.255.255.0
DHCP Enabled = Yes
DHCP Scope: 192.168.1.100 to 192.168.1.199
Each SOHO Router I've setup like this designed the course between subnets naturally when both the WAN and LAN side are arranged effectively. It's sufficiently straightforward to see whether it's working, connect a PC to a LAN port on Router2, in the event that you can get to the web, it's working. In the event that you can't, you may need to check the steering table to guarantee you have the course between the two subnets (WAN and LAN side) legitimately designed.
When setup and working legitimately, the 192.168.1.0/24 LAN will have web access, network with whatever else connected to Router2 however won't have admittance to anything connected to Router1. The opposite is genuine additionally, PCs connected to Router1 will have web access and LAN access to gadgets connected to Router1. Be that as it may, they won't have admittance to anything connected to Router2.
About Unknown
0 comments:
Post a Comment