gluon 🚀 - Support for TP-Link WBS210 v2.0

Not supported in OpenWrt yet and no pull request yet. You might want to ask around and send your device to someone who is able to build the support.

Until that is resolved Gluon support is out of the question, sorry.

mweinelt on 30 Sep 2018

I guess it is the same hardware as v1.2 I added following strings:

                   "WBS210(TP-LINK|UN|N300-2|00000000):2.0\r\n"
                   "WBS210(TP-LINK|US|N300-2|55530000):2.0\r\n"
                   "WBS210(TP-LINK|EU|N300-2|45550000):2.0\r\n"

to .support_list of tplink-safeloader.c, compiled openwrt and could upload the image and log in via ssh.

it looks similar to the patch included for CPE210 V2. I'll have a look at where I can report that to openwrt

datendelphin on 5 Oct 2018

Support added to OpenWrt master in 5c5bf8b8658a588423f6ec445d7ef6a36f99a396. You'll probably also need 2524febf7927a1bf430d64b7790feb126023e3d1.

mweinelt on 26 Nov 2018

Moin, is the recommended "fix" already tested to not brick a router? We got a User in our community who would like to use a WBS210 but only got a v2 version.

MTRNord on 18 Jan 2019

I compiled openwrt with the dirty hack i mentioned above, and that works and did not brick my device. Now I'm trying to go the route with the mentioned patches, building dedicated v2 images, though I did not manage yet to build them, mostly due to lack of time and this is the first time tinkering with openwrt.

datendelphin on 19 Jan 2019

Hm ok so I guess this needs to wait a bit longer. I will report that to the user.

MTRNord on 28 Jan 2019

Support added to OpenWrt master in 5c5bf8b8658a588423f6ec445d7ef6a36f99a396. You'll probably also need 2524febf7927a1bf430d64b7790feb126023e3d1.

This looks like it is about the CPE210 v2, not the WBS210 v2?

RalfJung on 13 Feb 2019

👍1

The expectation is that it is mainly the same hardware, except that the WBS has antenna connectors while the CPE has internal antennas.
My device in the mean time doesn't want to flash with the factory firmware properly. Still trying with tftp.

datendelphin on 13 Feb 2019

FWIW, we have just successfully flashed a WBS v2 with our firmware, after patching it as described above. Wifi meshing is working as well.

RalfJung on 13 Feb 2019

@RalfJung so you could go through our checklist and create a pull request maybe

rotanid on 13 Feb 2019

Well I don't have the device nor did I do the flashing, but maybe I can get the people that did to do that.^^

Which checklist? I checked the README and CONTRIBUTING files and found no checklist.

RalfJung on 14 Feb 2019

@RalfJung maybe the device integration checklist: https://github.com/freifunk-gluon/gluon/wiki/Device-Integration-checklist

@ all: it took me several minutes to find that page, are there links to that page somewhere, beside the "pages" dropdown of the wiki (and other tickets of cause)?

bobcanthelpyou on 14 Feb 2019

👍1

I'm one of those @RalfJung mentioned, the one who bought a WBS210 V2 and flashed the "FrankenFirmware" onto it. After that worked, I bought another 10 WBS210. While we did flash the first one from the normal login, we used TFTP to flash the other ten. It worked, but it's different compared to other TP-Link routers though. It expects the TFTP-Server to run on a host with IP 192.168.0.100 instead of 192.168.0.66 and it asks for "recovery.bin" instead of something bearing the router specifications in the file name.

I didn't make the firmware, but we'll see what we can do to get into OpenWRT and from there down the stream. It contains a minor bug that I don't understand yet: On the map, it shows up as a WBS210 V2.[insert a whole lot of bad encoding symbols here]0. Aside from that, it works.

A WBS510 is on its way, we'll see what happens.

gobold1979 on 18 Feb 2019

Moin, is the recommended "fix" already tested to not brick a router? We got a User in our community who would like to use a WBS210 but only got a v2 version.

I can at least say, that thanks to TFTP, it is not possible to brick these things by just flashing something weird onto them.

gobold1979 on 19 Feb 2019

JFTR: The WBS510 has arrived and it's a V1.20. But that's not what this thread is about anyway.

gobold1979 on 19 Feb 2019

It seems like our Firmware ignores the PoE-Passthrough-Setting. Does anyone have an idea how to deal with that?

gobold1979 on 19 Feb 2019

On 19.02.19 15:39, gobold1979 wrote:

It seems like our Firmware ignores the PoE-Passthrough-Setting. Does
anyone have an idea how to deal with that?

What is it exactly that is being ignored?

Power over Ethernet should be toggleable from withing the Network tab in
the config mode. It represents a subset of gpio switches below uci show system.gpio_switch.

Compare
https://github.com/freifunk-gluon/gluon/blob/master/package/gluon-web-network/luasrc/lib/gluon/config-mode/model/admin/network.lua#L110-L130

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/freifunk-gluon/gluon/issues/1538#issuecomment-465154467,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAICD7p3SvRlAQBA1We5-LujSINaAiKBks5vPAy5gaJpZM4W7Uho.

mweinelt on 19 Feb 2019

What is it exactly that is being ignored? Power over Ethernet should be toggleable from withing the Network tab in the config mode.

That's exactly what I mean. In detail, let's compare the expected behaviour, as it can be observed as actual behaviour on the WBS510 V1.2 to the actual behaviour of a WBS 210 V2.0:

For the WBS510V1.2...

Go to the network tab ("Erweiterte Einstellungen" -> "Netzwerk")
Check the box next to Activate PoE Passthrough ("PoE-Passthrough aktivieren")
Click "Save" / "Speichern"
Switch to the wizard
Click "Save and reboot" / "Speichern und neustarten"
The device reboots. After a minute or so, it activates PoE passthrough, i.e. the LAN port starts to provide passive PoE.

For the WBS210V2.0
Steps 1 through 5 as above.

It reboots, but there's no PoE on the LAN port.

It represents a subset of gpio switches below uci show system.gpio_switch. Compare https://github.com/freifunk-gluon/gluon/blob/master/package/gluon-web-network/luasrc/lib/gluon/config-mode/model/admin/network.lua#L110-L130

I don't have any knowledge on that, but I'll have a look. Thanks for the link!

gobold1979 on 22 Feb 2019

Here are patches for OpenWrt and Gluon adding support for the WBS 210 V2.0:
ftp://ftp.geierb.de/gluon/
Most likely PoE passthrough won't work (didn't test it), but it builds an own image for the wbs210v2 which can be flashed using TP-Links web GUI, the model shows up correctly and Wifi works as expected.
I have no real clue about the whole thing, so I'd highly appreciate if someone else could take over.

citronalco on 14 Jun 2019

Here are patches for OpenWrt and Gluon adding support for the WBS 210 V2.0:
ftp://ftp.geierb.de/gluon/
Most likely PoE passthrough won't work (didn't test it), but it builds an own image for the wbs210v2 which can be flashed using TP-Links web GUI, the model shows up correctly and Wifi works as expected.
I have no real clue about the whole thing, so I'd highly appreciate if someone else could take over.

As nobody else seems to be interested, I'll try to bring these patches into shape.
Flashing the factory image using the web ui works, but a sysupgrade on command line fails with

Image metadata not found
Invalid image magic '003a0d3d'. Expected '01000000'.
Image check 'platform_check_image' failed.

Does anyone know how to solve this? Any hints? Is it sufficient to add the image magic in target/linux/ar71xx/base-files/lib/upgrade/platform.sh like below?

wbs210-v2)
    tplink_pharos_check_image "$1" "003a0d3d" "$(tplink_pharos_v2_get_model_string)" '\0\xff\r' && return 0

Edit: Yes, it is. #1827

citronalco on 23 Sep 2019

I am interested but sadly didn't have the time to test it yet as I don't own the device myself but only a community member who really would like to use his device. If I can do any tests that help, please ping me. But keep in mind I do not have the device on my desk. Max would be to build a firmware, get it to the device owner and remote shell into it if it works :)

MTRNord on 28 Sep 2019

It works properly, but unfortunately won't be merged. See my pull request #1827
Porting the device was not that hard, I could build upon old gluon pull requests for similar TP-Link devices. But porting it to OpenWRT's target ath79, as it is required now for gluon, is probably above my abilities.

citronalco on 28 Sep 2019

Ok :/ I don't have the required knowledge to do the port either.

MTRNord on 28 Sep 2019

But porting it to OpenWRT's target ath79, as it is required now for gluon

this is not true.
Gluon does not support hardware, that is not supported by OpenWrt.
And OpenWrt does not contain WBS210 v2 at the moment, neither in ar71xx target nor in ath79 target.
Therefore, Gluon does not accept a patch as was always the policy, so we don't carry downstream patches forever which aren't upstream.

Regarding OpenWrt, they do not accept new devices into ar71xx target as it got replaced by ath79.
Even if they would accept a device, it would need to be supported in ath79 before

rotanid on 28 Sep 2019

👍1

But, isn't it a consequence of that those OpenWRT and gluon policies that the device could only get into gluon if it gets ported to ath79? Or am I missing something?

If what I said is accurate, how is the statement "porting to ath79 is required for gluon" not true? (Either way the clarification for where that policy comes from is appreciated, I am just trying to figure out what was wrong about the original statement.)

RalfJung on 2 Oct 2019

But, isn't it a consequence of that those OpenWRT and gluon policies that the device could only get into gluon if it gets ported to ath79? Or am I missing something?

If what I said is accurate, how is the statement "porting to ath79 is required for gluon" not true?

you are right

rotanid on 2 Oct 2019

The WBS210 v2 is now supported by Openwrt
https://github.com/openwrt/openwrt/commit/3930aab2cb067d04f5c9ebbf1af57744e19355eb

TomTheDragon on 3 Nov 2019

great, so as soon as Gluon has the ath79 target we can support this device via a backport of the linked patch.

until then, someone could now try to get the ar71xx variant supported in openwrt, too.
but maybe they reject it for ar71xx, there's no clear policy that i know of.

rotanid on 3 Nov 2019

We are ready to tackle this one on master.

mweinelt on 3 Mar 2020

Any updates on the WBS210 v2 support of Gluon?

TomTheDragon on 2 Sep 2020

We rely on third-party contributions for device support, since we need someone to verify the hardware support.

mweinelt on 2 Sep 2020

We rely on third-party contributions for device support, since we need someone to verify the hardware support.

... unless someone donates such a device.

rotanid on 2 Sep 2020

Gluon master still uses an OpenWRT branch too old to support WBS210 v2.
If I'm not wrong it would currently not only be testing and then enabling the device in Gluon, but also backporting all the stuff.

citronalco on 10 Sep 2020

you could try it with the "next" branch and as soon as next branch becomes master, you can create your Pull Request

rotanid on 10 Sep 2020

Did a quick(!) test: Device works with the factory image that's built in the "next" branch when adding the line
device('tp-link-wbs210-v2', 'tplink_wbs210-v2')"
to targets/ath79-generic
Still have to check sysupgrade and LEDs.

But: The device has two ethernet ports: eth0 with PoE, and eth1(without PoE).
Config mode is on eth0, while WAN is on eth1. As this is an outdoor device and can only be powered using the PoE port, this seems somewhat impractical to me. Any hint where I can set WAN to eth0?

citronalco on 12 Sep 2020

Switch LAN and WAN in package/gluon-core/luasrc/lib/gluon/upgrade/020-interfaces
Add the device to the lists of outdoor devices in package/gluon-core/luasrc/usr/lib/lua/gluon/platform.lua
to get Config Mode on WAN instead of LAN

NeoRaider on 12 Sep 2020

Done. Config Mode and WAN are both on the PoE port, sysupgrade works, LEDs are ok. Everything is fine.

As far as I know it's not possible to make a PR in the "next" branch. Currently support for WBS210v2 is only in OpenWRT's master branch, not in a release. So if anyone's eager to test or not able to wait here's the relevant commit: https://github.com/citronalco/gluon/commit/2e6c7fbdc4d412ef1e13f502a9e51b6872ca405e

citronalco on 15 Sep 2020

Gluon: Support for TP-Link WBS210 v2.0

All 37 comments

Related issues