<div>
If you want separate IP ranges, presumably to isolate the networks from each other, then masnrock's suggestion of using equipment that supports VLANs is the only sensible way to go. You <b>might</b> make it work by cobbling various bits of kit together, but it would be a continuing headache to manage, and the only reason that you're currently able to run two DHCP servers at the same time is because they can't see each other...<br />
<br />
You might have to spend a bit more money on equipment than you want to, but you would then have a setup that actually worked reliably and as expected.
</div>


<div>
thanks guys for the response.
</div>


<div>
hi,<br />
I just got a related question. so have re opened this .<br />
<br />
I got router with vla capability. and I got AP where i am gonna create 2 SSIDs each in one subnet.<br />
I have attached a diagram of my plan. Could anyone have a look at it and let me know whether it is coorect ?<a href="https://filedb.experts-exchange.com/incoming/2017/11_w45/1204333/IMG_2719.JPG" target="_blank" title="IMG_2719.JPG (1.1 MB)"><img alt="IMG_2719.JPG" class="file-block lazyload" style="max-width: 800px;" data-src="https://filedb.experts-exchange.com/incoming/2017/11_w45/800_1204333/IMG_2719.JPG" /></a><br />
with my pic - in router am gonna craete 2 vlans. and from router to switch its trunnk port<br />
switch to access point is trunk port.<br />
in AP create 2 &nbsp;SSID and assign one vlan each. &nbsp;<br />
are this steps coorect ?<br />
<br />
Hope you guys understand what i am trying to say.<br />
<br />
Thank you
</div>


IMG_2719.JPG

<div>
You didn't have to use a trunk port to the AP, but it's not hurting you either. At a minimum, the port going to the AP had to have the VLAN that it is getting it's actually IP from as untagged, and other VLAN(s) involved for the SSIDs as tagged.<br />
<br />
As for the AP itself (and I assume that your AP works with VLANs, that point was never clear in your original question), make sure that you specify the correct VLAN for each SSID. If you do not spell out one, it will assume that the untagged VLAN is the one you intended.
</div>


<div>
hi masnrock,<br />
when u say this . <br />
At a minimum, the port going to the AP had to have the VLAN that it is getting it's actually IP from as untagged, and other VLAN(s) involved for the SSIDs as tagged. &nbsp; &nbsp; &nbsp; - it has both untagged and tagged. it means its a trunk port ? isnt it ?
</div>


<div>
Trunk ports are intended to carry the traffic for <b>all</b> of the VLANs. However, you can have a port handle tagged and untagged traffic for only a subset of VLANs. For example, if you had 5 VLANs defined, but you only wanted a switch port to be a member of 2 of them, that isn't a trunk.<br />
<br />
But like I said, in your case, it's actually a very minor detail. However, it might come into play in the future if you decide to implement additional VLANs.
</div>


<div>
<div class="content wysiwyg-content">
Hi,<br />
&nbsp;I got a Dlink router(192.168.10.1) in which i disbaled wifi. <br />
then I got a TP-link Access point where wifi and ssid enabled.<br />
I have connected Access point to router. setup dhcp in both access point and router. everything works fine. wifi works fine from AP getting ip in 192.168.10.1 range.<br />
<br />
But i want to setup access point(192.168.20.1) in a different subnet to the router network(192.168.10.1). &nbsp; how should i set it up to make it work ???<br />
<br />
Hope my question is clear.<br />
<br />
Thank you guys.
</div>
</div>


Hi,
 I got a Dlink router(192.168.10.1) in which i disbaled wifi. 
then I got a TP-link Access point where wifi and ssid enabled.
I have connected Access point to router. setup dhcp in both access point and router. everything works fine. wifi works fine from AP getting ip in 192.168.10.1 range.

But i want to setup access point(192.168.20.1) in a different subnet to the router network(192.168.10.1).   how should i set it up to make it work ???

Hope my question is clear.

Thank you guys.

setup Access point

Wireless networking is anything related to the transfer of data between two (or more) devices without the use of a physical connection, ranging from getting advice on a new Bluetooth headset to configuring sophisticated enterprise level networks.

Wireless Networking

The Dynamic Host Configuration Protocol (DHCP) is an auto configuration protocol used on IP networks and an extension of the Bootstrap Protocol. DHCP allows for computers to be configured automatically to communicate with each other over an IP network without the need for manual setup by a network administrator. The implementation of DHCP relies on a DHCP server to hand out network configuration information to DHCP-capable clients that request an IP address (and other information required or useful in communicating with other devices on an IP network). In addition to an IP address, common configuration information served over DHCP includes a default gateway, subnet mask and DNS sever(s).

DHCP

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.