Debugging Wireguard client that is not working

Debugging Wireguard client that is not working

Debugging Wireguard client that is not working
Debugging Wireguard client that is not working
Yesterday
Model: ER7206 (TL-ER7206)  
Hardware Version: V2
Firmware Version:

Hello,

 

I have setup 3 Windows clients using the Omada VPN connecting via Wireguard to an ER7206. All three clients where previously working fine.


Recently it was reported to me that one of the clients has stopped working, but the other two client still work fine. 

 

This client has two Wireguard profiles to two different sites. One is working fine the other has stopped working.

 

I have completely setup a new profile and re-built the peer on the router, but with no luck. 

 

Is there anyway to diagnose the problem using debug or log files?

 

It seems there is very little logging on the router (even using CLI) and there is no visible debug or log setting on the Omada VPN client. 

 

Regards

 

Stephen

  0      
  0      
#1
Options
3 Reply
Re:Debugging Wireguard client that is not working
Yesterday

  @AussieMan 

Wireguard can be used with Wireshark to analyze. 

Instead of asking the reason why, try with the basic guides and make sure there is no change to the public IP on the WAN.

VPN Connectivity and Access Troubleshooting Guide

 

It fails to work out of a sudden, basically means there is a problem with the network environment instead of the router. 

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced. ● I don't provide ETA for any products/features. No comment.
  0  
  0  
#2
Options
Re:Debugging Wireguard client that is not working
Yesterday
Hi Clive, Thanks for the reply. I am not a newby (35+ years in telecoms and IP networking) and have check all the typical things - including if the public IP on the WAN (note two other clients are working fine), Public keys on the Firewall and the peer. The reason I ask if there are any debugging options is I dont have access to the windows client workstation. They are remote and don't understand wireshark or what it even is. Having the debugging on the gateway would allow me to see what is happening like I can with other platforms. Don't get me wrong, Omada and the SDN is great, but your routers are a bit limited in functionality. It would be great if packet capture could be enabled for gateways - not just EAPs.
  0  
  0  
#3
Options
Re:Debugging Wireguard client that is not working
18 hours ago

  @AussieMan

AussieMan wrote

Hi Clive, Thanks for the reply. I am not a newby (35+ years in telecoms and IP networking) and have check all the typical things - including if the public IP on the WAN (note two other clients are working fine), Public keys on the Firewall and the peer. The reason I ask if there are any debugging options is I dont have access to the windows client workstation. They are remote and don't understand wireshark or what it even is. Having the debugging on the gateway would allow me to see what is happening like I can with other platforms. Don't get me wrong, Omada and the SDN is great, but your routers are a bit limited in functionality. It would be great if packet capture could be enabled for gateways - not just EAPs.

There is no option for the gateway capture packet yet. 

You can submit a request on the request page. 

Best Regards! If you are new to the forum, please read: Howto - A Guide to Use Forum Effectively. Read Before You Post. Look for a model? Search your model NOW Official and Beta firmware. NEW features! Subscribe for the latest update!Download Beta Here☚ ☛ ★ Configuration Guide ★ ☚ ☛ ★ Knowledge Base ★ ☚ ☛ ★ Troubleshooting ★ ☚ ● Be kind and nice. ● Stay on the topic. ● Post details. ● Search first. ● Please don't take it for granted. ● No email confidentiality should be violated. ● S/N, MAC, and your true public IP should be mosaiced. ● I don't provide ETA for any products/features. No comment.
  0  
  0  
#4
Options

Information

Helpful: 0

Views: 44

Replies: 3