![]() ![]() If your default gateway on your machine (PC) is configured correctly, the inter-VLAN traffic will pass through the FortiGate. So, I assume your client at different VLAN will have the default gateway as follow: With the given configuration, you decided the gateway (for VLAN 10,20,30) are at the FortiGate. So it's all basically depend on your network design. SVI), you will need to create a transit network between FortiGate and Cisco Switch, and as well as routing between them. If you gateways for VLAN20, VLAN30 are on Cisco Switch (e.g. You put VLAN10, 20, 30's gateways on FortiGate, such that all inter-vlan traffic are protected by Firewall. If you need inter-vlan routing, you have to plan & decide the network design. do i need route on the core swicth ? Drew up a quick pic just for a bit of clarity. Link is up on both sides but no traffic flow /no ping. LACP default is active /Tried l2forward enable /tried lacp speed slow. I have managed to get the link up via LACP-but packets are not flowing :įORTIGATE-INT-CONFIG: - Just a matter of creating an 802.3ad aggregate type of swicth. I need an internal network from the 200E to the Cisco core switch. The 200E does not appear to have the Hardware switch option like the 100E's on which I was able to just allocate an internal ip (hardware switch) and I can get access to the switch without any more configurations. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |