Hello, I also logged a ticket for this with Fortinet, but there's still no solution that works.
For a customer I configured a Fortigate VM with several vdoms and vdom links
What happens is that routing table in External vdom is configured to route traffic to network 192.168.247.0/24
via the internal vdomlink. What happens is, that traffic is routed out of another interface, i.e. the default gateway to the internet.
What is remarkable is that the routing monitor shows the correct route to that 192.168.247 network, while the kernel routing table doesn't mention this subnet.
Someone who recognizes this strange behaviour? Is it a vmware issue?
I also upgraded the firewall from 5.0.11 to 5.2.5 already, what -unfortunately- did not solve it!
Kind regards
Ralph Willemsen
Arnhem, Netherlands
Solved! Go to Solution.
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Ok, problem solved. Fyi: there were vips configured where I had to disable arp replies for them. Now it seems to work well.
Regards,
Ralph Willemsen
Arnhem, Netherlands
Ok, problem solved. Fyi: there were vips configured where I had to disable arp replies for them. Now it seems to work well.
Regards,
Ralph Willemsen
Arnhem, Netherlands
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1633 | |
1063 | |
751 | |
443 | |
210 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.