VDOM link not working

Forum|Forum|9 years ago
September 2, 2016
6 replies
11066 views

We have an old 80C unit with two vdoms for different subnets (10.0.0.0 and 10.1.0.0) and a VDOM link to connect the two. I've gone through setting up the VDOM link and have assigned an arbitrary address for each end (10.0.40.10/255.255.255.0 for 10.0.0.0 and 10.1.40.10/255.255.255.0 for 10.1.0.0).

The problem I'm seeing is that nothing is actually able to connect through the VDOM link for some reason. I'm by no means an expert on this so I may have something wrong. When I do a tracert from one side to the other I'm getting the to the firewall but it just dies on the link address. I can however ping the gateway address for the other subnet. (10.1.0.1 from the 10.0.0.0 subnet for example).

Any ideas? Really hoping I'm just missing something simple.

Carl_Wallmark

New Member

Hi,

Have you checked that routing is correct on "the other side" ?

Also policies ?

For example:

You are on network 192.168.1.0/24 and want to ping 172.16.16.100 (on the other side)

You need a route on both VDOMs:

172.16.16.0/24 -> VDOM Link2

192.168.1.0/24 -> VDOM Link1

support_swilsonAuthor

New Member

Thanks for the reply. I should have mentioned that I do have static routes in place on both VDOMs directing traffic for the appropriate subnets through the VDOM link interfaces.

Policies are also in place and since it's just internal I have them wide open (ALL/ACCEPT) for testing purposes.

MrSinners

New Member

The best would be to run a debug flow trace to see what the Fortigate is doing with the traffic on each VDOM and most likely shows a reason if the traffic stops somewhere. Are both IP addresses on the VDOM links in the same network? Are they 10.1.40.0/24 and 10.0.40/24? If so then they are not on the same network and that should be corrected. Do you know how to run a debug flow trace?

Sign up

Login with SSO

Login to the community

Login with SSO