Port 443 is rarely used and ONLY necessary if your ISP blocks all kinds of other ports.
Most folks use something in the 13-15,000 range.
Post your config to see what you have done.
/export file=anynameyouwish ( minus router serial # and any PUBLIC wanip information )
On the note, you stated your ISP provides a Private IP, so its a modem/router. and your WANIP is fixed/static of 192.168.0.X its private so why you hide it makes no sense??
The subnet on the MT is 192.168.88.0/24
If this is the case then you cannot use Wireguard.
NEED PUBLICLY accessible WANIP.
a. MT is connected to the ISP MODEM and gets a public IP.
b. MT is connected to another ROUTER which gets a public IP and then and then port forwards the listening port to a LANIP ( in this case the LANIP of the MT router on the ISP LAN → also is the WANIP of the MT ).
c. MT is connected to the ISP modem/router which gives the MT a private IP address on the LAN subnet of the ISP router and then port forwards the listening port to the MT.
In other words you either
a. get a public IP
b. get an upstream router to port forward the listening port to your MT router.
MT is behind the ISP Gpon but I have a static/public IP available and I can port forward on the ISP Gpon.
The forwarding is done like: UDP EXT port & INT port 13231 to MT local adress (Eg 192.168.0.111)
Did the above mentioned update and redone the config all the way from scratch and now the MT Wireguard server works and also a windows 11 client.
Another client on IOS also works but with with intermitence - I’ll open another thread for that issue to keep these apart.
Thanks for the help.
