trenzterra
Arch-Supremacy Member
- Joined
- Sep 18, 2002
- Messages
- 20,594
- Reaction score
- 501
Posting here to consolidate information about the TP-Link EB810v which is currently being provided by StarHub for their 10Gbps plans and sharing my experience.
First off, the default password to login is Starhub@123 in case the trooper forgot to give you the password.
I am running it in a mesh configuration (paying extra $15/mth for 24 months for the extra set), with one set in my DB box and one set in my middle bedroom. I am getting full coverage throughout my 4 room BTO, although 5GHz speeds generally seem slightly better than 6GHz. Testing using my phone (Wi-Fi 6E, S23 Ultra), I am getting about 1.4Gbps speeds if I am relatively near the router, or about 800-900Mbps if I am further away. It's pretty much gigabit LAN speeds, so nothing to complain about here.
The size of the router is gigantic. Together with the ONT, there is barely any space left in the DB Box. It also gets rather warm and suggest that you hook up a laptop cooler or something to the USB port on the router.
In terms of port selection, the EB810v is better than the BE805 and HB810. Apart from the 10Gbps LAN and WAN ports, you get three 2.5Gbps ports. This is compared to 4x1Gbps + 1x10Gbps on the BE805 and only 2x2.5Gbps + 1x10Gbps on the HB810.
Web interface wise, you can set up the router in "router" or "access point" mode, or as an EasyMesh node.
You can set VLAN settings although I have not tried it. Setting custom DNS for both IPv4 and IPv6 is possible.
There is support for TP-Link, Dyndns and No-IP dynamic DNS, but I have not tried either.
By default, there is "band steering" enabled where 2.4GHz and 5GHz can share one SSID. So far it seems to work fine for me, my 5GHz devices always connect at 5GHz. 6GHz is always on a separate band unless you enable MLO, although I do not experience much issue having 6GHz sharing the same SSID as 2.4GHz & 5GHz. In my experience, using MLO on a non-MLO device results in the device connecting to the 2.4GHz band, resulting in poor performance.
Port forwarding, DMZ, UPnP, port triggering and static DHCP are featured.
Guest networks are also supported, and they are placed on a separate subnet from your main SSIDs and therefore cannot access your main devices (a minor shortcoming vs ASUS which allow you to disable that option, although TP-Link also has a separate Multi SSID function which serves a similar purpose I guess). The guest networks also work over the mesh -- I can see devices connected to either the main router or the mesh node. The only shortcoming is that when you have band steering enabled, the setting also transfers to the guest network. Hence, there is no way to have a 2.4GHz-only guest network if you have band steering enabled, so certain IoT devices may have compatibility issues on initial pairing.
There are two other notable shortcomings I noticed compared to my previous AX86U + XD5 set up. One is that I cannot bind a specific device to a particular mesh node. However, this still seems ok for me as my devices generally connect to the closest node (I had an issue previously with my AiMesh setup where a device close to my main router would instead connect to my XD5 further away instead). Also, there is no ability to define the SNR limit at which your device is forced to change nodes, which could mean that your device would linger on one specific node even though it has poor connection. But so far in my small flat, haven't really experienced such issues and generally getting 5 bars throughout.
First off, the default password to login is Starhub@123 in case the trooper forgot to give you the password.
I am running it in a mesh configuration (paying extra $15/mth for 24 months for the extra set), with one set in my DB box and one set in my middle bedroom. I am getting full coverage throughout my 4 room BTO, although 5GHz speeds generally seem slightly better than 6GHz. Testing using my phone (Wi-Fi 6E, S23 Ultra), I am getting about 1.4Gbps speeds if I am relatively near the router, or about 800-900Mbps if I am further away. It's pretty much gigabit LAN speeds, so nothing to complain about here.
The size of the router is gigantic. Together with the ONT, there is barely any space left in the DB Box. It also gets rather warm and suggest that you hook up a laptop cooler or something to the USB port on the router.
In terms of port selection, the EB810v is better than the BE805 and HB810. Apart from the 10Gbps LAN and WAN ports, you get three 2.5Gbps ports. This is compared to 4x1Gbps + 1x10Gbps on the BE805 and only 2x2.5Gbps + 1x10Gbps on the HB810.
Web interface wise, you can set up the router in "router" or "access point" mode, or as an EasyMesh node.
You can set VLAN settings although I have not tried it. Setting custom DNS for both IPv4 and IPv6 is possible.
There is support for TP-Link, Dyndns and No-IP dynamic DNS, but I have not tried either.
By default, there is "band steering" enabled where 2.4GHz and 5GHz can share one SSID. So far it seems to work fine for me, my 5GHz devices always connect at 5GHz. 6GHz is always on a separate band unless you enable MLO, although I do not experience much issue having 6GHz sharing the same SSID as 2.4GHz & 5GHz. In my experience, using MLO on a non-MLO device results in the device connecting to the 2.4GHz band, resulting in poor performance.
Port forwarding, DMZ, UPnP, port triggering and static DHCP are featured.
Guest networks are also supported, and they are placed on a separate subnet from your main SSIDs and therefore cannot access your main devices (a minor shortcoming vs ASUS which allow you to disable that option, although TP-Link also has a separate Multi SSID function which serves a similar purpose I guess). The guest networks also work over the mesh -- I can see devices connected to either the main router or the mesh node. The only shortcoming is that when you have band steering enabled, the setting also transfers to the guest network. Hence, there is no way to have a 2.4GHz-only guest network if you have band steering enabled, so certain IoT devices may have compatibility issues on initial pairing.
There are two other notable shortcomings I noticed compared to my previous AX86U + XD5 set up. One is that I cannot bind a specific device to a particular mesh node. However, this still seems ok for me as my devices generally connect to the closest node (I had an issue previously with my AiMesh setup where a device close to my main router would instead connect to my XD5 further away instead). Also, there is no ability to define the SNR limit at which your device is forced to change nodes, which could mean that your device would linger on one specific node even though it has poor connection. But so far in my small flat, haven't really experienced such issues and generally getting 5 bars throughout.
