Hi all,
I do not know if it has something to do with my issue, but my previously working site-to-site tunnel between two GL-MT300N works only in one direction (servers from one side can trace/ping to the other locations but not the other way) since the last firmware upgrade (3.201). Has anyone faced this issue before?
Hi,
Could you show me the wg1 interface info with two routers? Command wg can get the info.
Hi Riho, thanks for your reply.
From the router that is not able to reach the “other” side:
/root$ wg
interface: wg1
public key: O/zcjRJ6OdgpIrMQxlYigAKect9IPvY7bNgbWc4HDwo=
private key: (hidden)
listening port: 35619
peer: 30cfljIQfwnQLyCVch49vRMtqN+jRjyuWaEF4dzeOgI=
endpoint: 80.26.179.116:51830
allowed ips: 10.148.18.0/24, 192.168.8.0/24
latest handshake: 43 seconds ago
transfer: 364.44 MiB received, 946.36 MiB sent
persistent keepalive: every 25 seconds
And from the side that is able to ping the other network:
/root$ wg
interface: wg1
public key: 30cfljIQfwnQLyCVch49vRMtqN+jRjyuWaEF4dzeOgI=
private key: (hidden)
listening port: 51830
peer: O/zcjRJ6OdgpIrMQxlYigAKect9IPvY7bNgbWc4HDwo=
endpoint: 82.213.251.123:35619
allowed ips: 10.0.0.0/24, 10.148.18.2/32
latest handshake: 11 seconds ago
transfer: 126.84 MiB received, 291.33 MiB sent
I forgot to mention that this tunnel has been created from h t t p s://eu.goodcloud.xyz/. Maybe is failing because the wrong route is not configured for a single “gateway” as on the good one? I will sent also the static routes of the bad routing (I can not send both because of my user)
Many thanks.