My TP-Link CPE610 refuses to capture an IP address from my internal router. I wanted to share my home Internet connection via this device over the RF mesh. I feel as though I'm missing something fundamental here. I've tried setting the WAN to DHCP and also tried assigning an IP to it.
Help!
Mark, KM6ZPO
File Attachment:
Support File Attachment:
https://www.arednmesh.org/content/sharing-internet-connection-lan
https://www.arednmesh.org/content/understanding-vlans
Hi, Mark:
I think you need a VLAN (802.1Q) capable switch...properly programmed.
Chuck
Mark, sounds like you might need to verify that your VLAN-capable network switch or "Smart Switch" is correctly configured. Here's a great example post if you're using a Netgear GS105e or GS305e switch: https://www.arednmesh.org/content/configuring-netgear-gs105e-switch-lanwan-ports
Thank you for the advice. I purchased a Netgear GS108PEv3 8-Port Gigabit Ethernet Smart Managed Plus Switch and followed the linked directions that AB7PA supplied (https://www.arednmesh.org/content/configuring-netgear-gs105e-switch-lanwan-ports). My VLAN ports are a bit different than the guide (all ports are VLAN 1), but my setup works. I was finally able to upload the node's location to the mesh map and am able to do package installs and updates directly from the node instead of having to upload them. I don't see my node on the map yet, but I suspect it will show up in time.
My only disappointment is that the POE ports (apparently) don't supply enough power to power up the TP-Link CPE610. But that's OK. I have the AC-DC POE injector that came with it and I also have a battery backup that works. (See: https://www.amazon.com/gp/product/B07K2Z6CFK/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1)
For field use now I just need another battery backup device like the one above that supplies 48V for the switch.
THANK YOU! 73, Mark, KM6ZPO
Mark, I don't know about your specific switch but most PoE switches have a way to detect whether the connected device is IEEE 802.3af/at compliant before it supplies the standard 48v DC. According to the TP-LINK CPE610 datasheet, it operates with an input voltage range of 16-27v DC so you don't want to feed it with 48v (which is too much power rather than too little).
One step forward, one step back...
I wasn't able to install the tunnel software so I matched up my VLAN settings exactly as shown in the guide. Alas, no luck. Any ideas why I wouldn't be able to download packages?
When I click the "refresh" button next to "Download Package" (in order to populate the list) I get the following errors:
Mark, it looks like your package "paths" were set to query the 3.20.3.1 version, but I assume you may have been running one of the nightly build firmware versions at the time? If you upgraded to the latest nightly build you sometimes need to navigate to the Advanced Configuration display and verify that the package URLs are pointing to the correct location. If you are running the 3.20.3.1 version, you will see 3.20.3.1 in the package URLs. If you are running the nightly build version, you will see something like "snapshots/trunk/packages" in the URL path (screenshot example). If you see a discrepancy, you can click the "Set to Default" button and it should reset the package path to be correct for the firmware version you are currently running on the node.
Thank you, Steve.
I set default / save setting to each of the lines referencing the original firmware and that solved it. Now I see that the package list downloaded:
I reverted back to version: 3.20.3.1 and am now able to install packages.
this looks like a defect in that we are not clearing those particular advanced config values upon an upgrade....
workaround: hit "Set to Default" then "Save Setting" for each of the "download" values.
Yup, that was the issue. Thanks!