You are here

TP-Link CPE210 setup issue

21 posts / 0 new
Last post
K8HMF
TP-Link CPE210 setup issue

I just purchased two CPE210 nodes from Amazon and proceeded to set them up via the Pharos software. All went well until the AREDN install rebooted. Now I cannot connect to either node using the 192.168.1.1 ip. I can ping it and get 100 percent return. I am using a HP Pavilion g6 laptop running Windows 10. I cannot reach the node using MS Edge so I loaded Chrome and now I seem to reach the node but it will not allow connection. Any help would be most appreciated. TNX es 73, Dave K8HMF

nc8q
nc8q's picture
I seem to reach the node but it will not allow connection.
Hi, Dave:

Please be more specific.

"I can ping it and get 100 percent return."
This information is helpful.

When you view http://localnode.local.mesh/cgi-bin/mesh with a web browser, what exactly is displayed?
What happened that you did not expect to happen?
What did not happen that you expected to happen?
What is the exact error message?

73, Chuck
 
K8HMF
CPE210 Issues
Returns message "Bad gateway". Nothing else. Thanks, Chuck, 73
nc8q
nc8q's picture
CPE210 Issues after loading recovery.bin
https://docs.arednmesh.org/en/latest/arednGettingStarted/installing_firm...

Says to
  1. After the node reboots, it should have a default IP address of 192.168.1.1. You should be able to ping the node at 192.168.1.1. Don’t proceed until you can ping the node. You may need to disconnect and reconnect your computer’s network cable to ensure that it has a connection.
  2. Once your device is running AREDN® firmware, you can display its web interface by navigating to either http://192.168.1.1 or http://localnode.local.mesh. Some computers may have DNS search paths configured that require you to use the fully qualified domain name (FQDN) to resolve localnode to the mesh node’s IP address. You may need to clear your web browser’s cache in order to remove any cached pages.

Did you use the fully qualified domain name?
Did you clear your browser's cache?

73, Chuck

 
AC9XU
Bad Gateway

I too am get the "Bad Gateway" after pushing the "Setup" button. I have loaded The Factor/Recovery File and wish to continue to load the Sys file. I have a TPLink CPE 210 V3.26.. I am using the Windows installation guide and the CMD line to pint 192.168.1.1 with 4 out of 4 success.
Thank you for any help.

Brian AC9XU

Chuck,
  I have been following this request. The system will allow me to get to the "NoCall XXXX " page but when I go to the set up page, after typing in 'root'/"hsmm/ this is when the Bad Gateway error is present..  
Pushing 'Setup gives the full error of

Bad Gateway
The process did not produce any response.

73 Brian

K7EOK
My CPE210 which is not very
My CPE210 which is not very old would not accept the new firmware.  I was able to get it back onto 3.22.12.0 and it's fine like that.  I did not use the Pharos method, I only have used the tinypxe method.  Perhaps trying to use the older firmware will get it going for now?

Ed
 
AC9XU
Ed,

Ed,
 One part of the  start up procedure for getting your computer ready says to use 192.168.1.xxx  in the checklist step by step it says 192.168.0.100..  the V2 and V3 software will not load unless I use th "0" in the IP address..  however in the check list it states that I need to ping the TP link with 192.168.1.1.  no connection..  I am wondering where to go from here..

Brian
P.S> I am using the Tiny PXE

nc8q
nc8q's picture
Bad Gateway!: CPE 210 V3.26

Are all these 'Bad Gateway' messages with CPE 210 v3.26?
Any not v3.26?
Does v3.26 load AREDN v3.22.12.0 ?

Recent Nightlies have an update pertaining to 'Bad Gateway' responses:
https://github.com/aredn/aredn/pull/885

73, Chuck

AC9XU
Chuck,
Chuck,
Thank you for the support here. I an not getting any version of the TPlink 210 software to load.  I will continue to monitor the forums  and hopefully we will find a fix.

Thanks again,
Brian
nc8q
nc8q's picture
I am not getting any version of the TPlink 210 software to load.
Hi, Brian:

Especially
aredn-20230704-eaa5d2f-ath79-generic-tplink_cpe210-v3-squashfs-factory.bin
aredn-20230704-eaa5d2f-ath79-generic-tplink_cpe210-v3-squashfs-sysupgrade.bin

But also including:
aredn-3.19.3.0-cpe210-v3-factory.bin
aredn-3.19.3.0-cpe210-v3-sysupgrade.bin
aredn-3.20.3.0-ath79-tplink_cpe210-v3-factory.bin
aredn-3.20.3.0-ath79-tplink_cpe210-v3-sysupgrade.bin
aredn-3.20.3.1-ath79-tplink_cpe210-v3-factory.bin
aredn-3.20.3.1-ath79-tplink_cpe210-v3-sysupgrade.bin
aredn-3.21.4.0-ath79-tplink_cpe210-v3-factory.bin
aredn-3.21.4.0-ath79-tplink_cpe210-v3-sysupgrade.bin
aredn-3.22.1.0-ath79-generic-tplink_cpe210-v3-squashfs-factory.bin
aredn-3.22.1.0-ath79-generic-tplink_cpe210-v3-squashfs-sysupgrade.bin
aredn-3.22.6.0-ath79-generic-tplink_cpe210-v3-squashfs-factory.bin
aredn-3.22.6.0-ath79-generic-tplink_cpe210-v3-squashfs-sysupgrade.bin
aredn-3.22.8.0-ath79-generic-tplink_cpe210-v3-squashfs-factory.bin
aredn-3.22.8.0-ath79-generic-tplink_cpe210-v3-squashfs-sysupgrade.bin
aredn-3.22.12.0-ath79-generic-tplink_cpe210-v3-squashfs-factory.bin
aredn-3.22.12.0-ath79-generic-tplink_cpe210-v3-squashfs-sysupgrade.bin
?

73, Chuck

 
K7EOK
Step by step

You start with the node's router out of the box at 192.168.0.? and make your fixed ip match for pxe server.

Then you upload factory, it reboots.  Now the router is 192.168.1.1 for NOCALL and you have to reset your computer fixed ip to be compatible.

If in Windows you must use BOTH ipconfig to verify your own card settings AND ping to make sure you can reach the other device.

Once you upload the sysupgrade it will reboot then the router now will give you a mesh address 10.?.?.? and you AGAIN change your network card to DHCP and then you start configuring the node with name, password, reboot ... use ipconfig and ping before trying to do anything at each step.

Each time you must unplug the ethernet cable to your computer to force the network card to accept a new setting.  Turn your wifi off so it doesn't automatically pickup other networks.  For that particular model start from scratch with 3.22.12.0 and see if you can get anywhere. 

http://downloads.arednmesh.org/firmware/html/stable_322120.html

Ed

nc8q
nc8q's picture
192.168.0.? and make your fixed ip match for pxe server.
Save a step.
If you are using the TFTP (PXE-server) method to upload the factory.bin file,
then the AREDN device has no IP address until it gets one from the TFTP server.
You may as well set your TFTP server's IP address to 192.168.1.X, then
you will not need to change your host's IP address for the sysupgrade.bin part.

73, Chuck
 
AC9XU
Ed and Chuck,
Ed and Chuck,

  I think I getting there with the older version of the Factory Bin file, I enter the 192.168.1.1 into the new browser and I get a request for Username and Password. I have not gotten to the No Call page. is there anything needed after the IP address? Ie (/setup, or /admin???) if I put in root/hsmm it gives me "404 file not found"

Thanks

Brian
K7EOK
Now I'm confused.  You say
Now I'm confused.  You say you're using pxe server and the factory bin file.  If it takes ... then you should have the device reboot and for the first time see the famous NOCALL page.  Only at that point are you going to be asked for username and password.  So if you were asked for username/password you had to have a good first step and have the NOCALL page.

Unless I'm forgetting something, the next step you DO NOT change password, but use the default password to login to setup and tell it to upload the sysupgrade bin file.  It reboots back again to NOCALL then you change the node name and password.

I'm going to guess that a screen shot of each step will be needed ... and sometimes when the devices are acting funny the more experienced folks here will give you the direct address to type to get into the setup page, rather than rely on the links on the gui. 

Ed
 
AC9XU
Now Im Confused
Ed,
Sorry for the confusion.. I have added the screenshot.. Image attachment.

Brian
Image Attachments: 
K7EOK
I'm not an AREDN expert but
I'm not an AREDN expert but that sure doesn't look like you are logging into an AREDN node during firmware install.

That looks like your computer is still connected to your home/office router and is thinking you want to log into that device instead.  You do not do firmware updates while you are on your home or office network and getting an IP address from anything other than the CPE210 itself.

Ed
 
AC9XU
It's Magic
I left the unit sit this afternoon while i worked.. Came into the office and presto... I am in and able to enter the Sys file and on my way.  Thank you Ed for being patient.  

Have a great evening..

73

Brian
K7EOK
Boy that's weird.  Go figure.
Boy that's weird.  Go figure.  All I can think of is that when you left the computer alone for a long time, one of your network cards went to sleep.  When you came back it got it's IP address from the CPE210 and there you go!

Or not ... 

73, Ed
 
kf7yrs
After the login screen I also get the "Bad Gateway" on CPE210

Hello, I have a TPlink CPE210 V3.26 that I am trying to flash with AREDN firmware.  I've been following the AREDN's instructions as well as a non-IT person can, but I can not get past the initial user/password setup step.  The Pharos firmware that came on the CPE210 made flashing new AREDN firmware easy and I installed "aredn-3.23.4.0-ath79-generic-tplink_cpe210-v3-squashfs-factory".   It booted and I could ping it successfully and reliably.   I pointed my browser (tried both Google Chrome and MS Edge) to 192.168.1.1 and was rewarded with the "NOCALL" screen.  I could open the help page and the setup page.  However, when I entered the user and password, I get a "Bad Gateway" error message.  From then on I can not get back to the enter password screen unless I restart the browser or clear the cache.  If I enter the wrong password, it just reloads the page with no "Bad Gateway" error.  I take this as a sign I am entering the proper credentials.   I've reset the CPE210 (5 second reset) many times but no change.  I tried the longer reset mentioned in the firmware help page, but nothing changes.   I've seen exactly the same behavior on two Windows 10 computers, one a complex desktop and one a minimal Celeron "hocky puck" with nothing but the CPE and mouse/keyboard attached.  The desktop has Avast antivirus which I deactivated, the Celeron has only the basic Win 10 protection.  I've tried to flash with TFTP and TFTPD64 no joy, but again, not an IT person and I'm unsure I got all the settings right.  I bought a second CPE210 and figure I get one chance to flash working firmware using the Pharos program that comes with the CPE.  Any suggestions?  I've read through the comments here, lots to learn.  Thanks!

kf7yrs
WOOHOO - Thanks Ed

I loaded the 3.22.12.0 firmware Ed suggested and the CPE210 us up and running!yes
 

w6bi
w6bi's picture
Updates
Congrats on getting the AREDN firmware installed, but keep working towards getting the most current version installed.  It has a ton of updates.  Your node and your network will thank you!
73
Orv W6BI
 

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer