Fortigate vm view license1/29/2024 ![]() ![]() I've deployed this 3 times and everything works flawlessly after the deployment. Id=65308 trace_id=11 func=vf_ip_route_input_common line=2605 msg="find a route: flag=04000000 gw-192.168.0.1 via port3"īased on the above, looks like everything is ok. Below i've done a simple debug to 8.8.8.8 to catch pings, with show function enable: DHCP on the fortigate interface, issues an address to the virtual machine and acts as the DNS server and DNS queries from the VM work against the FG interface. From the my virtual machine, i can ping the fortigate, from the fortigate i can ping the internet (8.8.8.8) and fortiguard servers are connected. The following day, I can no longer browse even though there were no config changes. ![]() I can ping, browse, windows updates (everything). Oddly, when i first deploy the VM, everything works (tested this 3 times). ![]() One policy for testing purposes: any/any/all. We are utilizing Fortinet products in our environment for a few years now, so to better help my journey as an effective administrator, i tried setting up a home lab using VMware. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |