Not Rocket Science Setup Goals
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Not Rocket Science Setup Goals
Model :
Hardware Version :
Firmware Version :
ISP :
I want all the things attached to the network via my hardwired stuff plugged into my router/switch, my TP-Link EAP225 AP, and my TP-Link EAP245 AP to be able to talk to each other.
I want them all to get a 192.168.0.x DHCP/Static IP as they do now with my router running DD-WRT. I can't seem to set my TP-Link APs properly and I'm not quite sure where to start reading. Conceptually it isn't complicated, but not beginner stuff in actual practice it seems either. As much as it pains me to adimit it, I am not far enough into the "intermediate level" of understanding to accomplish this at this time. But, I'm no insect operating off of 100% genetic instinct-- I can grow and if pointed in the right direction this task is probably within my capabilities.
I don't need my devices to automatically switch from one AP to the other sharing SSIDs or anything-- that can be 100% negotiated by the devices when they deem the signal differential sufficient. I don't know that my needs require my APs to work together. More simple, more better... right?
tl;dr: 802.11b --> 802.11ac
I have old stuff that needs to connect to the newer stuff. My toddler daughter's ASUS 1st Gen Nexus 7 Android tablet (802.11n) for instance and our new TCL TV with Roku built-in (802.11ac) so she can start watching Moana in stunning UHD with the Roku App. The boys have an 802.11b laptop running as a music server at night... I think that is the oldest crustiest thing we've got. My IoT stuff is 802.11g/n. The wireless printers are 802.11g/n. Our phones are 802.11ac. I have a small server for Virtual Machines that has a HAPRoxy VM for my dumb 802.11n IP Cams for viewing over SSL away from home. Other stuff, but that is the bulk of it.
I don't suppose it matters, but I'll likely get a third AP for the back yard in the near future...
Hardware Version :
Firmware Version :
ISP :
I want all the things attached to the network via my hardwired stuff plugged into my router/switch, my TP-Link EAP225 AP, and my TP-Link EAP245 AP to be able to talk to each other.
I want them all to get a 192.168.0.x DHCP/Static IP as they do now with my router running DD-WRT. I can't seem to set my TP-Link APs properly and I'm not quite sure where to start reading. Conceptually it isn't complicated, but not beginner stuff in actual practice it seems either. As much as it pains me to adimit it, I am not far enough into the "intermediate level" of understanding to accomplish this at this time. But, I'm no insect operating off of 100% genetic instinct-- I can grow and if pointed in the right direction this task is probably within my capabilities.
I don't need my devices to automatically switch from one AP to the other sharing SSIDs or anything-- that can be 100% negotiated by the devices when they deem the signal differential sufficient. I don't know that my needs require my APs to work together. More simple, more better... right?
tl;dr: 802.11b --> 802.11ac
I have old stuff that needs to connect to the newer stuff. My toddler daughter's ASUS 1st Gen Nexus 7 Android tablet (802.11n) for instance and our new TCL TV with Roku built-in (802.11ac) so she can start watching Moana in stunning UHD with the Roku App. The boys have an 802.11b laptop running as a music server at night... I think that is the oldest crustiest thing we've got. My IoT stuff is 802.11g/n. The wireless printers are 802.11g/n. Our phones are 802.11ac. I have a small server for Virtual Machines that has a HAPRoxy VM for my dumb 802.11n IP Cams for viewing over SSL away from home. Other stuff, but that is the bulk of it.
I don't suppose it matters, but I'll likely get a third AP for the back yard in the near future...
