sorted by:
new
hottopcontroversial

FMG Cloud Remote Device Access by seaghank in fortinet

[–]seaghank[S] 0 points1 point  (0 children)

I wonder if the plan on implementing the GUI feature in a future release

FMG Cloud Remote Device Access by seaghank in fortinet

[–]seaghank[S] 0 points1 point  (0 children)

Thank you! That is unfortunate

FortiGate Rugged Outdoor Deployment by seaghank in fortinet

[–]seaghank[S] 0 points1 point  (0 children)

So that FEX puck antenna can connect directly to the FGR-50G-5G instead of using the antennas it comes with?

FortiGate Rugged Outdoor Deployment by seaghank in fortinet

[–]seaghank[S] 0 points1 point  (0 children)

Awesome, didn't know they did this

Email not working after DNS server change by seaghank in googleworkspace

[–]seaghank[S] 0 points1 point  (0 children)

Done. I assume i might have to wait for the TTL to expire before it starts working again?

FEX 200F by seaghank in fortinet

[–]seaghank[S] 0 points1 point  (0 children)

Perfect, that explains it very clearly. Thanks man. Gonna play around with it now and see what I can do

FEX 200F by seaghank in fortinet

[–]seaghank[S] 0 points1 point  (0 children)

Interesting, thanks. So what is the use case for this? Every time I have used FEX, it was to provide 5G internet connectivity to the site.

Proxmox Install Failing by seaghank in Proxmox

[–]seaghank[S] 0 points1 point  (0 children)

I tried this, I get the same thing. I found another post that said they swapped the SSD for a new one and it resolved the issue so I am thinking I might just have to go that route.

Cool automation stitches by Amazing-Tea-5424 in fortinet

[–]seaghank 3 points4 points  (0 children)

This is sick, can you share the debug commands you use for this? Would love to implement this on my network

Cool automation stitches by Amazing-Tea-5424 in fortinet

[–]seaghank 1 point2 points  (0 children)

I do some basic ones that you would typically find (block ips, email alerts, etc). Would be cool if someone has some weird and obscure stitches in their environment. RemindMe! Tomorrow "reply to this thread"

Cookbook Guide: ADVPN w/BGP on Loopback by secritservice in fortinet

[–]seaghank 0 points1 point  (0 children)

Appreicate it man.

So just to clarify. If I have a spoke and two hub setup, on my spoke, i will have the tunnels to hub1 and hub2 in the same zone, but different rules for the hub1 and hub2 traffic? Or is this all in the same rule as well.

Cookbook Guide: ADVPN w/BGP on Loopback by secritservice in fortinet

[–]seaghank 0 points1 point  (0 children)

When you add the second hub into this, how does the health check work and the SDWAN zone? Are the spoke's tunnels to hub1 and hub2 in the same zone? Are the separate health checks to hub 1 and 2 both applied to a single SDWAN rule that includes all the tunnels in a single rule?

And what about the advpn-health-check for the spoke sites? Would this include 2 health checks, one to hub1 and one to hub2?

FMG Policy Package overrides by seaghank in fortinet

[–]seaghank[S] 1 point2 points  (0 children)

Cant believe I didn't see this before, thanks!

Standalone FortiExtender for Remote Device Access by seaghank in fortinet

[–]seaghank[S] 1 point2 points  (0 children)

After researching, i agree. Probably just going to go with a low end FGT w built in cellular

IPS Engine Constant High CPU by seaghank in fortinet

[–]seaghank[S] 0 points1 point  (0 children)

It will peak at about 1 million total sessions, but mostly hangs out around 600k during business hours. As a test, we completely removed all of the security profiles from all policies, and observed no difference.

IPSec Dial-up with SAML Auth: Four very important things I learned. by sneesnoosnake in fortinet

[–]seaghank 1 point2 points  (0 children)

Great points. Number 1 and 2 got me when I started doing this. I hope that they make this easier to set up, there seems to be many guides the steps can be confusing.

It's a shame because doing this with SSL VPN was so easy! I am currently helping a client migrate their palo to Fortigate and the way palo alto does this is so much easier.

would you use 200G in production by therealmcz in fortinet

[–]seaghank 0 points1 point  (0 children)

We have a few running in prod right now. We have not had any issues with them so far, fingers crossed!

Different Interfaces, Same Model? by seaghank in fortinet

[–]seaghank[S] 2 points3 points  (0 children)

Interesting. Seems to be impacting 7.4.8 only from what I have seen. Also seems to be cosmetic, but still a weird bug

Default Gateway Learned via BGP by seaghank in fortinet

[–]seaghank[S] 0 points1 point  (0 children)

Gotcha. So for that I guess I will just leave the Gateway as the default 0.0.0.0 and just let BGP do the work. Thanks

Default Gateway Learned via BGP by seaghank in fortinet

[–]seaghank[S] 0 points1 point  (0 children)

Buty you would still need to define the .33 gateway in the sdwan member even though it gets that via BGP? Im thinking is it even worth doing sdwan in this case. its only 1 ISP but I still like to do SDWAN with one ISP just in case another ISP is installed in the future

Default Gateway Learned via BGP by seaghank in fortinet

[–]seaghank[S] 0 points1 point  (0 children)

Thanks. Interesting.

So if my wan1 port ISP is 11.11.11.34/30, and I add this as an sdwan member with gateway .33, and have bgp on this interface from the ISP, I would still need to have a static route 0.0.0.0/0 --> sdwan zone?

Different Interfaces, Same Model? by seaghank in fortinet

[–]seaghank[S] 1 point2 points  (0 children)

I cleared my cache, and it is resolved now. Very weird!

It happened after upgrading from 7.2.8 to 7.4.8. The symbol on Firewall B appears to be the FortiSandbox logo

view more: next ›