I'm playing with another VDOM setup. This time the Root vdom will hold
the primary traffic while a sub vdom will only have an inbound IPSec VPN
connection for remote clients to connect too via forticlient. I've got
the root vdom setup and it's passin...
I know that you can have like VDOM-A and VDOM-B that both have the same
IP space, such as 10.10.0.0/16 when Root is just passing traffic to
physical interfaces. However, can you have Root have the same IP space
as VDOM-A if all traffic runs through r...
Background on environment.Root vdom contains all the physical interfaces
for traffic to the internet and vmware stack. All traffic coming into or
flowing out of the VDOMs has to route through Root. Vdom-A and Vdom-B
share IP schemes, so everything ha...
Quick background on the environment.Root vdom contains all the physical
connections to the VMWare stack and the internet. VDOM A - All internet
bound traffic (inbound or outbound) runs through an intervdom link.
Everything works as expected.I underst...
I've got a couple of VDOMs set up using a shared internet connection
through Root. Root has to have firewall policies to allow/foward/nat the
traffic from the VDOMs to the internet. I will have the security
profiles implemented at the individual VDOM...
Just FYI - from the VDOM-A context (which I call 'Bubble') So you can
see it does not matter what context you run the debug in. I see the
traffic in both.
I respectfully disagree. When tested in another known working config, it
does not matter what context the debug is run in. When I figured out the
issue, I instantly started seeing the traffic even though I was in a
root vdom context.
OMG guys, I'm an idiot. I'm thinking that the problem is with the VDOM
because I'm learning that and don't fully understand it. So that's where
the problem has to be, right?Well Mr idiot here, for WHATEVER reason, on
the client side didn't have an "a...
