ER605 v2.0 fw 2.2.2 Wire guard peer - can't select interface to create peer (solved; not fw issue)
I've just upgraded to fw v2.2.2 from 2.0.1.
Attempting to create a Wireguard VPN Peer, the first field is requesting the "Interface". The field is greyed out and the interface can't be selected or entered. I'm currently just using a single WAN interface on the router.
Without being able to provide the interface here, trying to create the client with "OK" fails with a "Please select an item" pop-up pointing to the Interface field. Tried this in two different browsers and same thing occured.
I haven't tried this before, so don't know if it worked in the earlier firmware.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Clive_A Thanks for the reply. In my situation I'm trying to set up a site-to-site Wireguard VPN between two ER605 controllers. Ideally without using the Omada Controller software.
I was able to figure out the source of my problem (confusion) and it of course isn't a firmware bug. Adding what I realized here to hopefully benefit others.
On the VPN > WireGuard there are two tabs.
> Wireguard and > Peers
On the > Wireguard tab, you have to +Add and specify a "Name:" that will identify the wireguard interface you're creating along with related parameters. After this is set up, you can proceed to the > Peer tab, do +Add, and the "Interface" for the peer can be selected from interfaces created on the > Wireguard tab.
I was trying to create a peer prior to creating the interface, and mistakenly thought "Interface" refered to a WAN interface.
- Copy Link
- Report Inappropriate Content
Thanks for posting in our business forum.
Please refer to the Configuration Guide How to Configure WireGuard VPN on Omada Controller
- Copy Link
- Report Inappropriate Content
@Clive_A Thanks for the reply. In my situation I'm trying to set up a site-to-site Wireguard VPN between two ER605 controllers. Ideally without using the Omada Controller software.
I was able to figure out the source of my problem (confusion) and it of course isn't a firmware bug. Adding what I realized here to hopefully benefit others.
On the VPN > WireGuard there are two tabs.
> Wireguard and > Peers
On the > Wireguard tab, you have to +Add and specify a "Name:" that will identify the wireguard interface you're creating along with related parameters. After this is set up, you can proceed to the > Peer tab, do +Add, and the "Interface" for the peer can be selected from interfaces created on the > Wireguard tab.
I was trying to create a peer prior to creating the interface, and mistakenly thought "Interface" refered to a WAN interface.
- Copy Link
- Report Inappropriate Content
Thanks for posting in our business forum.
onemorecable wrote
@Clive_A Thanks for the reply. In my situation I'm trying to set up a site-to-site Wireguard VPN between two ER605 controllers. Ideally without using the Omada Controller software.
I was able to figure out the source of my problem (confusion) and it of course isn't a firmware bug. Adding what I realized here to hopefully benefit others.
On the VPN > WireGuard there are two tabs.
> Wireguard and > Peers
On the > Wireguard tab, you have to +Add and specify a "Name:" that will identify the wireguard interface you're creating along with related parameters. After this is set up, you can proceed to the > Peer tab, do +Add, and the "Interface" for the peer can be selected from interfaces created on the > Wireguard tab.
I was trying to create a peer prior to creating the interface, and mistakenly thought "Interface" refered to a WAN interface.
Not sure what the other site looks like. WG contains the Interface and the Peer. TBH, all VPNs contain this Interface which represents the VPN interface. There is actually no site-to-site in WG where WG changes them into peers. If you want to route the traffic, you need to set the Allowed IP.
This is one of the big confusion for most people. I think you should refer to the WG official guide more then you get a clue about what's going on in WG on Omada. It actually simplifies a lot and makes it easier.
We don't have a standalone guide for WG but the controller version is good enough to illustrate the steps. Steps are the same in either standalone or controller mode. Set up the interface and configure the Peer.
- Copy Link
- Report Inappropriate Content
@Clive_A Thanks for the reply. I was also able to find this in the forums showing how to set up a site-to-site bi-directional wireguard VPN. It's using the Controller software too, but it's also basically a direct recipe for what needs to be done in the two ER605 Web interfaces to implement this.
https://community.tp-link.com/en/business/forum/topic/620506
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 597
Replies: 4
Voters 0
No one has voted for it yet.