TP-link TL-WR820N - using as an access point

[allie181]

I bought a TP-link TL-WR820N to use as a wireless access point for my T4.

I'm trying to set it up and I'm wondering if I've bought the wrong thing as I can't seem to configure it. Can the WR820N work as an access point for my T4?

Thanks in advance.

[Paul_oz53]

Looking at its specs I don't see any reason it wouldn't work.

Please confirm you have a wifi dongle plugged into the usb port on the T4, that it's recognized by the T4 and enabled. The wizzes have a range of drivers installed but finding a dongle that's recognized is still a bit of a challenge. They can be finicky to get going.

Mine works with older wireless N and AC adapters though we now use wired ethernet normally.

[allie181]

I want to use this instead of the dongle. I have a beyonwiz dongle but it has become unreliable. I want to plug this into the T4 and have it wirelessly connect to my network.

[MrQuade]

You don't want to set it up as an access point in that case. You want this device to act as a wireless client to your existing wireless access point.

I had a quick look in the manual and can't see anywhere that lets you set it up as a wireless client though. It's options look fairly basic.

[allie181]

Doh, thanks.

[MrQuade]

Doh, thanks.

Maybe see if you can swap it for a TP-LINK TL-WR802N. That looks like a cheap option that lists client mode as a feature.

[Grumpy_Geoff]

Do you still have the TP-LINK Archer T4U v3 adapter? Previously, on earlier firmware there wasn't an available driver for its RTL8812BU chipset, but the recent beta firmwares now have that available for download (it may even be possible to download it for earlier firmware, that's something that more knowledgable folk may be able to comment on).

Code: Select all

root@beyonwizu4:/etc/enigma2# opkg list *rtl88*bu*
enigma2-plugin-drivers-network-usb-rtl8822bu - 1.0-r0.1 - WiFi devices for Realtek 88x2BU chipsets.

If you don't still have that T4U adapter, then given you've previously had "bad luck" with an ASUS USB-AC68 adapter and the TP-Link T4U, I'd be forgetting a wireless adapter and be looking at getting an extender, access point, or router, that can operate in wireless-to-ethernet bridge mode - it connects to your existing wireless network and provides an ethernet connection to your T4.
The Edimax EW-7478APC access point can operate in 'Wireless Bridge/Wi-Fi Bridge Mode' mode, described as "The device connects to a network device for example: TV, gaming console, or media player via Ethernet cable and acts as a Wi-Fi bridge, allowing the network device to join your Wi-Fi network.".
It has AC1200 wireless (300Mbps on 2.4GHz and 867Mbps on 5GHz).
$64 @ MSY https://www.msy.com.au/edimax-ew-7478ap ... d-usb-port

[allie181]

Do you still have the TP-LINK Archer T4U v3 adapter? Previously, on earlier firmware there wasn't an available driver for its RTL8812BU chipset, but the recent beta firmwares now have that available for download (it may even be possible to download it for earlier firmware, that's something that more knowledgable folk may be able to comment on).

Code: Select all

root@beyonwizu4:/etc/enigma2# opkg list *rtl88*bu*
enigma2-plugin-drivers-network-usb-rtl8822bu - 1.0-r0.1 - WiFi devices for Realtek 88x2BU chipsets.

If you don't still have that T4U adapter, then given you've previously had "bad luck" with an ASUS USB-AC68 adapter and the TP-Link T4U, I'd be forgetting a wireless adapter and be looking at getting an extender, access point, or router, that can operate in wireless-to-ethernet bridge mode - it connects to your existing wireless network and provides an ethernet connection to your T4.
The Edimax EW-7478APC access point can operate in 'Wireless Bridge/Wi-Fi Bridge Mode' mode, described as "The device connects to a network device for example: TV, gaming console, or media player via Ethernet cable and acts as a Wi-Fi bridge, allowing the network device to join your Wi-Fi network.".
It has AC1200 wireless (300Mbps on 2.4GHz and 867Mbps on 5GHz).
$64 @ MSY https://www.msy.com.au/edimax-ew-7478ap ... d-usb-port

Hi Geoff

Yes, I do still have the adapter collecting dust in the cupboard. It would be fantastic if I could now get it to work. Do I just need to grab the recent beta firmware and install it? (ie you posted code - I don't need to try and edit any code myself, do I? )

[Grumpy_Geoff]

Give the beta firmware a go - take a backup first, so you can later reload settings and timers.
Get the 20190718 firmware from this post here - viewtopic.php?f=56&t=13422&start=100#p180210
Once you've loaded the new firmware and restored settings, then go to the plugin browser and download the driver - PLUGIN (or MENU>>Plugins)>>GREEN/Download plugins>>{wait for result}>>then expand drivers (OK).
Then select the 'network-usb-rtl8822bu' entry and install it.
Then plug your T4U wireless adapter in and reboot the T4. Then proceed to set up the wireless connection.
Hopefully the USB device ID for the V3 version of the T4U adapter is recognised by the Wiz.

[allie181]

Give the beta firmware a go - take a backup first, so you can later reload settings and timers.
Get the 20190718 firmware from this post here - viewtopic.php?f=56&t=13422&start=100#p180210
Once you've loaded the new firmware and restored settings, then go to the plugin browser and download the driver - PLUGIN (or MENU>>Plugins)>>GREEN/Download plugins>>{wait for result}>>then expand drivers (OK).
Then select the 'network-usb-rtl8822bu' entry and install it.
Then plug your T4U wireless adapter in and reboot the T4. Then proceed to set up the wireless connection.
Hopefully the USB device ID for the V3 version of the T4U adapter is recognised by the Wiz.

Unfortunately the T4U still isn't recognised by the T4

[Grumpy_Geoff]

Unfortunately the T4U still isn't recognised by the T4

Did you install the rtl8822bu driver?

I think I was a bit short-sighted when only asking peteru to add support for the Vendor and Product IDs of the v1 and v2 versions of the T4U adapter. At that time the v3 didn't have an available driver so I ignored it (particularly as my purchase was a v2 unit).

According to https://wikidevi.com/wiki/TP-LINK_Archer_T4U_v3 the v3 version USB Vendor and Product IDs are 2357:0115
Perhaps peteru can add them to the firmware at some point.

--------

We could give peteru's suggestion from an earlier thread a go, trying to force the adapter's Vendor and Product IDs to be recognised.
Here's a script containing those commands from peteru, but modified for the T4U v3 adapter.
Please take a settings backup on your T4 first, in case you need to flash the firmware if something goes wrong.
Download the attached scripts to a USB thumb drive and plug it into the T4 - ensure the T4U v3 adapter is _not_ plugged in.
As per peteru's previous instructions -

• use File Commander to run this new script, 'modprobe_T4Uv3.sh'
• then exit back to live TV,
• then attach the TP-Link T4U v3 adapter
• restart the GUI - MENU>>Power>>Restart GUI (or press 5).

Then run the logging script (LogCopy_T4U.sh) to see if it indicates the driver was loaded.
Finally give the network wizard a go.
The log files are copied to the USB thumb drive in file 'LogCopy#1.tar', so please attach it to a post here if the adapter isn't recognised.

[allie181]

Nope, still not recognised

[Grumpy_Geoff]

Nope, still not recognised

Yep, okay.
I'll take a look at the output when I've time, hopefully Monday late 'arvo after school pickup.

[allie181]

Nope, still not recognised

Yep, okay.
I'll take a look at the output when I've time, hopefully Monday late 'arvo after school pickup.

No rush, thanks for your help

[allie181]

Hi Geoff

Am I correct in guessing you've been unable to work out the problem?

[Grumpy_Geoff]

Hi Allie,

Please accept my apologies for my tardiness and not getting around to this sooner.

Did you attach the TP-Link T4U wireless dongle and restart the GUI between the executions of the two scripts?
The reason I ask is the driver appeared to load -

Code: Select all

Aug 10 13:45:54 beyonwizt4 user.info kernel: usbcore: registered new interface driver rtl8812au

then 42 seconds later a USB device is detached, then the wireless connection de-authenticates, then a further 17 secs later an ASUS USB device appears to be attached. Was that your other wireless dongle, the ASUS USB-AC68?
If so, it registers with ID 0b05:1852 but the USB device ID should be 0b05:1817 according to the websites I checked.

The TP-Link T4U appears to have not been attached to the T4.

Detected USB devices -
ID 18a5:0302 - Verbatim flash drive
ID 0b05:1852 - Asus ???

[allie181]

Hi Allie,

Please accept my apologies for my tardiness and not getting around to this sooner.

Did you attach the TP-Link T4U wireless dongle and restart the GUI between the executions of the two scripts?
The reason I ask is the driver appeared to load -

Code: Select all

Aug 10 13:45:54 beyonwizt4 user.info kernel: usbcore: registered new interface driver rtl8812au

then 42 seconds later a USB device is detached, then the wireless connection de-authenticates, then a further 17 secs later an ASUS USB device appears to be attached. Was that your other wireless dongle, the ASUS USB-AC68?
If so, it registers with ID 0b05:1852 but the USB device ID should be 0b05:1817 according to the websites I checked.

The TP-Link T4U appears to have not been attached to the T4.

Detected USB devices -
ID 18a5:0302 - Verbatim flash drive
ID 0b05:1852 - Asus ???

No need to apologise. Life can be busy!! You are doing me a favour which I greatly appreciate.

I know I followed your instructions to the letter, including when to insert the TP-Link T4U. The only ASUS USB device I have is the ASUS USB-AC68 so that must be what is being referred to.

I'll go through the process again on the weekend and record what I do step by step. Then I'll post back. I'm wondering though whether it might be worthwhile if I insert the TP-Link T4U and leave it inserted for > 1 hour to see if it registers and starts working. I say this because the wiz wifi dongle that I'm currently using often doesn't work when I first plug it in, but when I come back a while later, it is working. This contributed to why I wanted a new dongle (although the main reason was that streaming was slow with it). But maybe it wasn't the wiz dongle after all. Maybe it is the T4?

I'll report back after the weekend. Thanks again

[Grumpy_Geoff]

I know I followed your instructions to the letter, including when to insert the TP-Link T4U. The only ASUS USB device I have is the ASUS USB-AC68 so that must be what is being referred to.

The USB vendor ID '0B05' is definitely used by ASUSTek Computer, Inc. and a USB device with this vendor ID was attached to the T4, whereas vendor ID '2357' is used by TP-Link but no USB device using this ID was attached to the T4.
Perhaps by mistake you attached the ASUS dongle instead of the TP-Link dongle?

But additionally, I just checked wikidevi again for the TP-Link T4U v3, and saw it was using the RTL8812BU chip - but my script was trying to set the 8812AU driver. I've fixed the script up and attached with a different name (#2). Please try this one.
You'll have needed to install the 'network-usb-rtl8822bu' driver plugin I've previously posted about.
The previous 'LogCopy_T4U.sh' script can be used for this test (producing file 'LogCopy#1.tar' as before).

modprobe_T4Uv3#2.sh

(355 Bytes) Downloaded 68 times

Since you've also still got the USB-AC68 adapter, why not try that again using the below scripts. I'd suggest a reboot between testing with the T4U and testing with the AC68.

modprobe_AC68#2.sh

(354 Bytes) Downloaded 67 times

LogCopy_AC68.sh

(318 Bytes) Downloaded 74 times

[allie181]

Thanks Geoff. I'll do this on the weekend and report back. Fingers crossed!!