I
I
Ivan Malyshev2014-05-16 23:14:04
Domain name market
Ivan Malyshev, 2014-05-16 23:14:04

How to connect a wifi router to an existing network?

Networkers, help to understand this issue. There is a task to connect a wifi router to an existing local network to distribute the network and the Internet to laptop users. How to do it right? Am I going to do it right if I plug a patch cord from the network into the WAN and specify the address area 192.168.0.80-192.168.0.100 in the DHCP settings of the router. The address range of the sleepy DHCP server is 192.168.0.10-192.168.0.79. Will laptops be able to see computers from the local network in this case? If not, how to properly implement this idea
Network in a domain. The router is a regular TpLink. Router address static 192.168.0.5

Answer the question

In order to leave comments, you need to log in

4 answer(s)
S
Samuel_Leonardo, 2014-05-17
@yos

Set the router to access point mode,
Or, if not, set up wifi, turn off dhcp on the router, plug the wire into the LAN

V
Vlad Zhivotnev, 2014-05-17
@inkvizitor68sl

> Will laptops be able to see computers from the local network in this case?
Can. But computers from the local network will not be able to see laptops.
Better to do as Samuel_Leonardo described.

T
throughtheether, 2014-05-17
@throughtheether

Am I right to do it if I plug a patch cord from the network into the WAN

If you mean connecting the WAN port of the new router (which will distribute wi-fi) and the LAN port of the already installed router / switch, then yes, this is one of the ways to solve your problem.
And here I would like to correct you. I suspect the netmask being used is /24 (255.255.255.0). In this case, in the DHCP settings of the new router (which will be active only on the wireless interface), you should specify another network specially allocated for this. For example, 192.168.1.0/24 if it is not used anywhere else (hosts 0 to 100, for example).
DHCP client must be enabled on the WAN interface.
In this case, all hosts connected via wi-fi will receive addresses from the new network (192.168.1.0/24 in the example), which will be natted to one address from the 192.168.0.0/24 network received via DHCP on the WAN port. In this case, laptops (i.e. hosts with a wifi connection) will have access to the Internet and other computers. Already installed computers will not have access to laptops in general.
Regarding the nuances that hypothetically may arise with a windows domain with such a solution (does domain authorization work through NAT, in particular), I can’t say anything. Another way - with the same physical topology (the cable from the switch or LAN port of the existing router is connected to the WAN port of the new router), enable the new router in bridging
mode between the WAN and wifi interfaces. In this case, access between wifi hosts and existing hosts will be mutual. Of the minuses - stretching the L2 domain, as it seems to me, is not the most stable solution anyway, here possible nuances associated with different physical environments are also added (excessive utilization of wifi by unnecessary broadcast / multicast, etc.).

G
grigory-1, 2016-10-21
@grigory-1

Task: Connecting new laptops to the existing wired Windows network of stationary computers via WiFi.
I connected via a D-link DIR-320 router to an existing peer-to-peer network without domains from about 15 computers with static IP addresses. A stationary computer with two network cards was used as an Inte-gateway. One, with parameters given by the provider, "looks" in the Internet. Another, with the address 192.168.0.1, "looks" into the internal network with static IP addresses for all computers on the network. This is also the gateway and DNS address for all computers on the internal network.
Did:
1. Connected a wire from the internal network hub to one D-link LAN connector.
2. In the D-link settings, I set its WEB LAN interface to a new address 192.168.0.6 (how - see the manual for your router), because. by default, D-link responded to IP 192.168.0.1, and this address is busy on the network. You can set any other unique address for this internal network. Now D-link is configured through this new address.
3. Disabled DHCP for LAN in D-link - after all, we have a network with static IP.
4. Enabled WiFI in the D-link, configured its connection with laptops in the usual way. WiFi laptop adapters were assigned unique addresses for the entire common internal network, indicated the gateway and DNS 192.168.0.1.
Result:
Everyone sees everything. Computers in the old network still see the Internet through the gateway computer and see laptops connected via D-link through the new WiFi network. Laptops connected via D-link through the new WiFi network see the old network and other computers in it and the Internet through the gateway computer.
Comment.
In order for any "guest" WiFi device to be able to work on this network, in this device you need to set not only the WiFi network key, but also a unique IP address (I allocated a couple of free ones "in my mind" for guests), the address of the gateway and DNS server (I have this 192.168.0.1).

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question