Wireguard support is available in standalone
er605 v2 has wireguard support in standalone, there is for now no wireguard support in omada, hope to see it as soon as possible as well as integration for all omada routers.
I checked right now tp-link emulators and er605 v2/v2.6 have wireguard support in standalone, you can check it with emulators from the table below
Router | HW version | Firmware version | kernel | wireguard | emulator url |
---|---|---|---|---|---|
ER605 | V1 | 1.0.1 Build 20210426 Rel.66674 | 3 | no | https://emulator.tp-link.com/er605_un_1.0/index.html |
V2 | 2.0.0 Build 20220907 Rel.77023 | 4 | yes | https://emulator.tp-link.com/dist/index.html | |
V2.26 | 20220907(UN) | 4 | yes* | https://emulator.tp-link.com/dist/index.html | |
ER7206 | V1 | 1.0.1 Build 20210426 Rel.71351 | 4 | no | https://emulator.tp-link.com/er7206_un_1.0/index.html |
ER8411 | V1 | 1.0.0 Build 20220812 Rel.66580 | 4 | ?* | ?* |
- * - emulator is only available for V2, I could not verify if V2.26 has wireguard support but would assume it since it is V2
- ?* - unknown, there is no emulator and no info in technical specification (or I was could not find it, please point to it if there is some)
Here some Screenshots of wireguard:
- Wireguard Interfaces overview
- Edit wireguard interface
- Wireguard Peers overview
- Wireguard peer edit
Sadly on emulator it is not possible to save/edit connections.
Here would be some questions for TP-Link to reply:
- From which version will er605 V1 support wireguard or if at all?
- Will er605 V1 get kernel upgrade to at least v4 or even much better v5?
- When will omada get support for wireguard?
- Does ER8411 support wireguard?
- Why did you never announce that wireguard is implemented as well as why are technical specifications about wireguard missing?
- Wireguard integration related questions:
- From which kernel version is wireguard supported with omada routers?
- Why has the implementation following restrictions which I would love to be extended:
- Wireguard interface configuration:
- only one address can be used
in case that interface needs to have a peer in another subnet, it would not be possible to predefine interface's address - missing FwMark field
- ipv6 support
- dns settings are missing, where ipv4 and ipv6 could be used
- only one address can be used
- Wireguard peer configuration
- only one address can be used in address field and no further can be added
- not sure what the default value of PersistentKeepalive is but if one is not behind proxy/isp firewall, then in most case one does not want to have PersistentKeepalive. If PersistentKeepalive has to be preset, then default should be at least 20 seconds, but not 1 second like in emulator.
- is there a max number of peers and what happens if one has more than 254 peers as there is address restriction in the interface?
- Peer management, could be own wireguard group with mandatory key field and optional psk, address list, PersistentKeepalive, email, comment, fields
mandatory key field: private key or public key if private keys are user managed, one of those two fields must be not empty - Additional optional field email and a button "Send config"
- add checkbox include all peers => will include peer configuration to all other existing peers, peers are then not dependant on router and every single of them could be used by this client as a gateway at any time
- disable keepalive or set keepalive value
- QRCode generation for simple peer config, wireguard client on mobile device can import configs from QR code. Importing QR code has its size limits and should be greyed out if checkbox "include all peers" is enabled
- there is no proper ipv6 support, please add proper ipv6 support
- in some cases users have ipv4 and ipv6 where one would require ability to add at least one additional ipv6 address.
- Wireguard interface configuration:
Hope to get reply from TP-Link to questions and suggestions above.
I would tag Fae and Hank, but if I do it in OP thread then forum software tells me that there are invalid links.