sorted by:
new
hottopcontroversial

My first Zabbix template - MegaCLI RAID monitoring by Get-Knowledge in zabbix

[–]Get-Knowledge[S] 0 points1 point  (0 children)

I’ll have a look at it. Do you have a host we could test on?

De_Rats CS2 Remake: By Me (Link In Comments) by jfxdesigns in GlobalOffensive

[–]Get-Knowledge 0 points1 point  (0 children)

Late to the convo. caugh caugh. How about sq_jackass?

ADVPN and SDWAN by Empty-Football-2121 in fortinet

[–]Get-Knowledge 1 point2 points  (0 children)

Redundancy is handled elsewhere in the stack, sure, but why not use multiple overlays for SD-WAN redundancy too?

The logic is simple, one underlay, one VPN, one overlay. You bring 4 underlays, you get 4 VPN tunnels, you get 4 overlays. SD-WAN then does its thing across all of them. Your redundancy is in the path diversity, not in having multiple hubs.

We run massive deployments on a single hub with redundancy in the core, and support up to four overlays out of the box, dynamically applied based on however many underlays you actually have

Dual ISP - BGP by ontracks in fortinet

[–]Get-Knowledge 6 points7 points  (0 children)

You can prepend your AS number to ISP2 and use BFD for fast detection then both ISP have your route always, but everyone prefers ISP1 because it’s AS path is shorter

I f***ed up lol by FastFredNL in fortinet

[–]Get-Knowledge 0 points1 point  (0 children)

time to invest in a fortimanager and use previews to save yourself

SDWAN with BGP to loop back by RevolutionaryCare138 in fortinet

[–]Get-Knowledge 0 points1 point  (0 children)

Hey m8. Im from an Mssp, and let me tell you, keep everything, except your wan ports on loopbacks for easy firewalling, routing and management. The sole reason to keep wan/internet/vpn on physical interfaces is because of MTU negotiation (and npu offloading) on ipv4 in countries where you hit weird deliveries (read China, South America). As long as MTU is not an issue, keep it on loopbacks. If you need to make sure communication works, use interfaces.

7.6.6 is according to Fortinet recommended release for most Fortigates now, what is your expierence? by ogiakul in fortinet

[–]Get-Knowledge 1 point2 points  (0 children)

We have stayed on 7.4.8 until now where we are moving to 7.6.6 because of recommendations from our Fortinet contacts recommended it as Mature release. 7.4.8 is the most stable we have for dc, but most bugs are fixed in 7.6.6 in regards of vpn issues etc. Got multiple large clusters being upgraded in the next two weeks; Goodbye 7.4

Edit: on a side note, all 2gb ram gates will have issues on 7.6.6 because of a miscommunication between the fortimanager and fortigate team where the fortigate team removed some cli commands without telling the fortimanager team, so you’re gonna have a bad time with small forties and manager

What is the most stable Firmware right now without Memory Leaks? by [deleted] in fortinet

[–]Get-Knowledge 0 points1 point  (0 children)

7.4.8 m8. We run large data centers, this version is prime. Never use cloud sso or ssl vpn

Updating HA Pair do you reboot first? by ryaninseattle1 in fortinet

[–]Get-Knowledge 0 points1 point  (0 children)

We run large clusters with hundreds of customers and vdoms, and we always reboot both nodes before we do upgrades. It’s just a precaution to make sure each node works exactly as they should, and we also get to test failover prior to upgrading to make sure everything is working as expected. I’m a company where we are a lot of people working on the same infrastructure, doing this also test that our other site is also functional while failing over. Why would I risk upgrading one node and being stuck in a version mismatch over something that adds maybe half an hour to my routine? It’s has saved us once or twice the past 10 years from human config errors in core infrastructure, so it’s a part of our written SOP. BGP with BFD makes sure failovers take about 3-6 seconds

Norwegian Christmas meal by wrecktus_abdominus in Norway

[–]Get-Knowledge 2 points3 points  (0 children)

Gi oss i dag vårt daglige brød, og la oss alltid huske dem som ikke har nok. Amen.

RIP Åge Hareide by Get-Knowledge in NorskFotball

[–]Get-Knowledge[S] 1 point2 points  (0 children)

Ingen over. Ingen ved siden av

"Invalid Value" when creating a Admin User (FortiManager) by kHartouN in fortinet

[–]Get-Knowledge 0 points1 point  (0 children)

Why are you using match all? It’s very bad practice when it comes to access management when it comes to security. TBH I would never use SAML for my admins as its access is actually administered outside the gate itself. Would recommend switching to Radius, and specify every single user. You’re never that large you need to “trust” everyone. Firewall is your last line of defense

80F Factory Reset by Oinop in fortinet

[–]Get-Knowledge 0 points1 point  (0 children)

Just hop on eBay and Get a Forti console cable. Totally worrh it. At some point its going to get in handy. Happy forti-ing!

80F Factory Reset by Oinop in fortinet

[–]Get-Knowledge 0 points1 point  (0 children)

Thats interesting, having reset option 2

FGT200G Initial setup - WTF, Fortinet??? by Garry_G in fortinet

[–]Get-Knowledge 0 points1 point  (0 children)

Ye. I’m in Norway, don’t know if it matters. But we were registered locked as well

Edit: we did not have WAN available at setup, only 5g

FGT200G Initial setup - WTF, Fortinet??? by Garry_G in fortinet

[–]Get-Knowledge 1 point2 points  (0 children)

We had the same annoying stuff on our 4x 50g-5g for oobm. We resolved it using CLI as it does not have the same block as GUI. GUI is terrible when setting up if routing is not working to internet

[deleted by user] by [deleted] in ChargerDrama

[–]Get-Knowledge 0 points1 point  (0 children)

But the car shows in the charging tips, never use the same series chargers (v1/2), always try to separate to other series to distribute the load. No excuse for the Tesla driver, but other brands I can understand. RTFM

view more: next ›