Skip to main content
rhardiman
Visitor III
Oct 28, 2024 5:24 PM UTC
Question

Traffic going to odd address instead of tunnel?

We expanded a subnet at a remote site and traffic from our main site to addresses in the new part of the remote subnet does not work. I have the correct subnet mask on the routes and on the IPSec VPN tunnel. I see the traffic in Forward Traffic being accepted and destined for the VPN interface, but if I do a traceroute the next hop after our firewall is 10.10.10.1 which is not on any network, route, or interface that we have at any site.

 

Traceroutes from a workstation show the firewall as the first hop and 10.10.10.1 as the second. Traceroutes from the firewall show that address as the first hop.

 

I'm sure more info is needed, please let me know what I can provide.

13 replies

AEK
SuperUser
SuperUser
Oct 28, 2024 5:37 PM UTC

You can start by checking if the right route is installed on FG.

get router info routing-table all

 

Translate
AEK
rhardiman
rhardimanAuthor
Visitor III
Oct 28, 2024 5:39 PM UTC

I have confirmed the 10.10.10.1 address is not in there and the route looks correct.

Translate
Toshi_Esumi
SuperUser
SuperUser
Oct 28, 2024 5:38 PM UTC

That's probably a "Tunnel ID" started from 7.0. Run "get router info routing-t all" in CLI. You would see 10.10.10.1 like .....(recursive via <tunnel_name> tunnel 10.10.10.1).
And if that's the case the packets are going over the tunnel but the other end is not replying back.

Toshi

Translate
rhardiman
rhardimanAuthor
Visitor III
Oct 28, 2024 5:44 PM UTC

I have confirmed that the address is not in the routing table.

Translate
Toshi_Esumi
SuperUser
SuperUser
Oct 28, 2024 5:41 PM UTC

What then did you see the next hop for the expanded subnet in the routing-table?

Toshi

Translate
rhardiman
rhardimanAuthor
Visitor III
Oct 28, 2024 5:46 PM UTC

S x.x.x.x/23 [10/0] via [TunnelName] tunnel x.x.x.x, [1/0]

 

As I think it should be? The IP addresses are correct.

Translate
Toshi_Esumi
SuperUser
SuperUser
Oct 28, 2024 5:56 PM UTC

try sniff the ping traffic while you're pining from a device behind the FGT.

        diag sniffer packet any 'icmp and host <device_IP_or_destination_IP>' 4 0

You might need to disable ASIC offloading on the outgoing policy toward the tunnel

        set auto-asic-offload disable



Toshi

Translate
Risk and Resilience in the Age of AI. An OT Thought Leadership Summit for Houston's Critical Infrastructure Leaders. Date: Thursday, December 3, 2026. Time: 8:30 am - 1:30 pm (CT). Location: The Westin Houston, Memorial City | 945 Gessner Road, Houston, TX 77024