Skip to main content
52000cc
52000cc
New Member
January 30, 2026
Question

VPN issue

  • January 30, 2026
  • 2 replies
  • 251 views

I set up a WireGuard (192.168.100.61) on the internal network and created a WireGuard VPN to connect to another network (192.168.101.0/24). I configured a static route for 192.168.101.0/24 pointing to WireGuard (192.168.100.61). The issue now is that I can access the remote network, but when the other side tries to access here, it shows a "no session matched" error. If NAT is not configured, how can this issue be resolved?

logs

vd-root:0 received a packet(proto=1, 192.168.100.25:1->192.168.101.51:0) tun_id=0.0.0.0 from vlan100. type=0, code=0, id=1, seq=101.
find a route: flag=05000000 gw-192.168.100.61 via vlan100
no session matched

 

2 replies

Jean-Philippe_P
Staff & Editor
Jean-Philippe_P
Staff & Editor
February 2, 2026

Hello 52000cc, 

 

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible. 

Jean-Philippe - Fortinet Community Team
funkylicious
SuperUser
funkylicious
SuperUser
February 2, 2026

if i understand correctly your setup, subnet 192.168.101.0/24 is behind your WireGuard which also has a connection to 192.168.100.0 network ( interface with ip 192.168.100.61 ) . where is the static route that you mentioned created? is it on the FGT ?

 

when traffic is initiated from 192.168.101.X towards 192.168.100.X its ok, since the WireGuard is the def gw for that network. is NAT enabled on WG for this traffic or not ?

 

when traffic is intiated from 192.168.100.X towards 192.168.101.X the traffic reaches the FGT which drops it. is the FGT the default gw for this network?

"jack of all trades, master of none"
Terms & ConditionsAccessibility statement