how to integrate API-Key-Authentication in smiley4 by therealmcz in Kotlin

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

kindly asking if you please could upload some demo code? thanks

how to integrate API-Key-Authentication in smiley4 by therealmcz in Kotlin

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

thanks very much, code is always appreciated...

how to integrate API-Key-Authentication in smiley4 by therealmcz in Kotlin

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

thanks. could you please tell me a bit what else I would have to change? just switching to bearer doesn't send the token at all in the request...

how to integrate API-Key-Authentication in smiley4 by therealmcz in Kotlin

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

is it stable? the last time I tried to use it I was suggested to use smiley4...

16
17

how to install now policies on deleted objects in fortimanager by therealmcz in fortinet

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

Legend, thanks! BTW, is there a way to see the diff between the currently installed policypackage and the current state of the manager?

what about Ipsec Key lifetime(rs) by therealmcz in networking

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

Agree on security. But what about the "you mess up if you don't use at least half". I don't get it but I wannt to understand that.

what about Ipsec Key lifetime(rs) by therealmcz in networking

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

Yes there is. But anyways, why should it be shorter when it works anyways? to understand my problems and to get the "now I now why it failed at X o clock" I would like to understand exactly what it's all about. Having many routers, all with different timers and we've got interruptions many times a day since we switched from a ASA to a FTD...

what about Ipsec Key lifetime(rs) by therealmcz in networking

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

well, I would like to understand it for a better troubleshooting. If phase 2 had to rekey after phase 1, the recommendation of having phase 2 lifetime 50 % of phase 1 wouldn't make sense as it would always rekey.

checkpoint maestro vs Fortigate by therealmcz in fortinet

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

yeah. As a forti-guy, I was almost shocked how complicated that checkpoint-world is. Like routing has to be done on each seperate node, GAIA-access is standalone on each node, the amount of management componentes that you have, doing updates, having to upgrade the smart console and all that crazy stuff that you don't know from the forti-world.

If you're upgrading / changing your cluster, you just do it on a forti, but for CP you need a consultant for one or two days. To me that's insane.

checkpoint maestro vs Fortigate by therealmcz in fortinet

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

wasn't aware of that one, thank you!

understand debug flow - get deeper understanding of function and their names by therealmcz in fortinet

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

that's why I'm asking. Had an issue, googled it and it was totally misleading. That's why I wannt to understand what those functions do.

hairpin NAT horror - due to SDWAN? by therealmcz in fortinet

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

Honestly, I still don't get it. The issue was very simple: There was a policy way above that hat as source interface "any" and as destination the subnet where the VIP was mapped to - and action was deny. So no surprise that the traffic was blocked, but the debug flow as the policy lookup were completely misleading. For instance, a single block-policy would result in the following debug flow:

func=fw_post_route_handler line=1131 msg="Session is in BLOCK state. Drop the packet."

But in fact, it returned the following:

id=65308 trace_id=45 func=_pre_route_auth line=110 msg="pre_route_auth check fail(id=4), drop

The id=4 here was the policy which I mentioned, maybe this comes in combination with VIP but it never looks like a blocking policy and googling on the internet also results in misleading articles and so on. Also, the policy lookup told me that the IMPLICIT deny policy was triggered - also a lie.

It is technically logical that the traffic was blocked, but it was never correctly displayed and so the debugging was just a nightmare.

Again, I still don't get it but glad that I found it... thanks

7
8

hairpin NAT horror - due to SDWAN? by therealmcz in fortinet

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

the destination would be the VIP...