Omada network: adding pharos wireless point to point connection
New to TPLink, omada, and pharos.
I started new position and came into an existing omada stack. I was tasked with adding two pharos cpe710s to wireless bridge a second building that has a unmanaged switch with 6 poe ip cameras.
From instructions, multiple how-to videos, and other research, it should be as simple to configure ip on first 710, set it as ap mode, set wpa2 and psk and connect to switch. Then on ap2 set ip, configure as client mode, survey and lock to first ap, set wpa2 and psk and should work. They are connected, but when testing plugged in client to client side, it is not getting dhcp address across wireless point to point. Even if I configure the client with an ip on same network, it cannot get across wireless and out to the internet.
Thoughts? what additional information is needed? If this should be in a different forum, let please let me know.
Thanks,
jdsn2g
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi @jdsn2g
Thanks for posting in our business forum.
Did you survey and join the AP? Or did you simply put up the info instead of scanning the AP SSID and joining it?
Do you find information of link speed on the page of the Client CPE? If there is no link speed, you did not even join the SSID from AP.
You are telling the correct steps but somewhere must be wrong.
And, AP CPE should be connected to a router with DHCP enabled. You can test the AP SSID with your cellphone first.
- Copy Link
- Report Inappropriate Content
Thanks for the reply.
Did you survey and join the AP?
-Yes. Client mode set. Survey, finds AP CPE and choose 'Lock to AP'
Or did you simply put up the info instead of scanning the AP SSID and joining it?
-No
Do you find information of link speed on the page of the Client CPE? If there is no link speed, you did not even join the SSID from AP.
-That I do not recall. I did see tx/rx in graph
You are telling the correct steps but somewhere must be wrong.
And, AP CPE should be connected to a router with DHCP enabled. You can test the AP SSID with your cellphone first.
-Correct. AP CPE is connected to omada switch which is configured to serve dhcp for that network. This AP CPE is actually set to dhcp and gets an ip from dhcp. I was able to connect to point to point ssid from my laptop and get out to the internet. So the AP CPE is working. The issue is on the client AP side. If I connect to lan port in POE injector with my laptop and try to do ipconfig /release and /renew to get a dhcp address, it is not happening. The network the AP CPE is on is vlan1 and port is set to ALL profile. (I do not see a place to set port as either client or trunk explicitly. On the other side the client AP will just be plugged into an unmanaged switch along with ip cameras.
Also, if I change the client AP to dhcp, it does not pick up dhcp from across the link from AP CPE either.
Other things we have tried (which should be set anyways): set distance to 1km, set timezone and dst settings.
It could because time is not updated on client AP cause it has not connected to internet yet. Will keep that in mind for next visit for troubleshooting.
Will plan on doing normal troubleshooting steps including updating firmware, physical tests, connectivity tests, etc.
Found this doc that outlines troubleshooting too:
https://www.tp-link.com/us/support/faq/2575/
thanks,
jdsn2g
- Copy Link
- Report Inappropriate Content
Hi @jdsn2g
Thanks for posting in our business forum.
jdsn2g wrote
Thanks for the reply.
Did you survey and join the AP?
-Yes. Client mode set. Survey, finds AP CPE and choose 'Lock to AP'
Or did you simply put up the info instead of scanning the AP SSID and joining it?
-No
Do you find information of link speed on the page of the Client CPE? If there is no link speed, you did not even join the SSID from AP.
-That I do not recall. I did see tx/rx in graph
You are telling the correct steps but somewhere must be wrong.
If you are positive about these, then it is not a problem with the AP or Client. It seems to be DHCP then.
jdsn2g wrote
And, AP CPE should be connected to a router with DHCP enabled. You can test the AP SSID with your cellphone first.
-Correct. AP CPE is connected to omada switch which is configured to serve dhcp for that network. This AP CPE is actually set to dhcp and gets an ip from dhcp. I was able to connect to point to point ssid from my laptop and get out to the internet. So the AP CPE is working. The issue is on the client AP side. If I connect to lan port in POE injector with my laptop and try to do ipconfig /release and /renew to get a dhcp address, it is not happening. The network the AP CPE is on is vlan1 and port is set to ALL profile. (I do not see a place to set port as either client or trunk explicitly. On the other side the client AP will just be plugged into an unmanaged switch along with ip cameras.
Also, if I change the client AP to dhcp, it does not pick up dhcp from across the link from AP CPE either.
Other things we have tried (which should be set anyways): set distance to 1km, set timezone and dst settings.
It could because time is not updated on client AP cause it has not connected to internet yet. Will keep that in mind for next visit for troubleshooting.
Will plan on doing normal troubleshooting steps including updating firmware, physical tests, connectivity tests, etc.
Found this doc that outlines troubleshooting too:
https://www.tp-link.com/us/support/faq/2575/
thanks,
jdsn2g
So far, you are doing things right. Don't see any specific errors in it. DHCP does not seem to be a problem as you have verified the WIFI from the AP.
I recommend you call the technical support when you do a visit next time. And report what you see instantly and get feedback from the rep instantly.
I hope you can pay attention to RX/TX on the info page which is important. It determines if it is connected to the AP or not. So, look for it when you are there. If no data, you need to redo the survey and connect things.
- Copy Link
- Report Inappropriate Content
There might be a configuration issue causing the DHCP and garage door internet access problems. Have you double-checked the settings and tried troubleshooting each step,
- Copy Link
- Report Inappropriate Content
@jdsn2g Just something to try: Put the bridge on a subnet that's not part of your network, you may just be having an ip conflict. Set one of them to something like 192.168.33.250 and the other to 192.168.33.249. They do not need to be on the same network as the rest of your network. This also keeps nosy people out of places they don't belong.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Have you checked the subnet settings Lesco Online Bills and DHCP configurations on both ends? Sometimes a small adjustment there can resolve connectivity issues.
- Copy Link
- Report Inappropriate Content
Thanks to all the replies. I was able to resolve after the last troubleshooting session. I compiled a list of exact steps from the various videos and written documentation and followed that: Confirmed everything was seated properly, updated firmware, stepped through setup again, and was able to successfully connect. Was able to see tx/rx from dashboard and confirm connectivity. Was able to get dhcp to clients and connect to the internet over the ptp connection. pretty impressive. getting near full ac throughput at ~100 yards.
- Copy Link
- Report Inappropriate Content
Double-check the network settings and ensure the AP and Client have the same SSID and encryption. Also, make sure the main router’s DHCP server is configured to serve IPs to devices connected through the PGSharp bridge.
- Copy Link
- Report Inappropriate Content
It is like you've covered the basic setup steps correctly. Have you checked the VLAN settings on both CPE710s and the switch? Sometimes VLAN mismatches can cause connectivity issues even if everything else seems configured properly and you can check more about on squishmallowshalloween.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 772
Replies: 10