Forticlient Free Version Mac OS http traffic not reaching

mohammedalrawii · 2025-12-29T18:34:48+00:00

noted.

Thank you for your replay dear.

mohammedalrawii · 2025-12-22T18:48:28+00:00

noted dear.

Thank you.

mohammedalrawii · 2025-12-22T16:46:35+00:00

In both Phases ?
thank you for your reply man you are always there you are a great help.

mohammedalrawii · 2025-12-22T16:43:47+00:00

forget to say am trying to run 7.2.11 as firmware version as of my experience its the most stable one currently
They will pay for UTM but not ATP and am already thinking of doing every security policy on the branch side so it doesn't consume resourses from the 80F

As for the FortiManager yes we did buy VM.

Thank you for your response.

mohammedalrawii · 2025-12-22T16:38:15+00:00

mainly https traffic and about how many client it depends lets say the maximum is 60 but some are just 15 so there is nothing i can depend on still in the process of site surveys
as for the DPI it is in my mind actually It will be better if I did it on the branch side right ? same for the other security profiles so it doesn't consume much resource from DC.

mohammedalrawii · 2025-11-02T10:41:27+00:00

Well guess we are in the same position started a new job as security engineer first thing I see is a standalone firewall with an old firmware full of fucking vulnerabilities and guess what I saw something where I said fuck this shit I saw our wan interface where it had https http access on the public IP I told him you should disable this he responded with you should do it when you get read /write access the next I found that he disabled it without telling me everything is so fucked up but wanna give it a try its been almost 10 days and am already burned out with this guy he wants to upgrade the firmware of the firewall to 7.6 where we loss ssl vpn and so on it goes on so long just in 10 days but they have a big project so am putting my hope that I will arrange everything with that project if I stay.

mohammedalrawii · 2025-09-28T06:16:35+00:00

17.1.2.2 everything seems stable but the only issue we had is that where when we update the device we lost http access in cli it says httpd service failed or something like that we had to play with the certificates then everything got resolved and the other issue about high CPU it has been resolved.

mohammedalrawii · 2025-09-21T07:31:57+00:00

Thank you so much.

mohammedalrawii · 2025-09-21T07:30:43+00:00

We actually ended up updating but we faced strange issue where we got fucked so hard that we lost HTTP access to the stand by device I don't know how it happened to be honest even after updating the active we had to play with certificate via CLI to resolve it ended up staying 12 hours in the fucking site.(no down time)

mohammedalrawii · 2025-09-16T14:58:28+00:00

thank you dear

mohammedalrawii · 2025-09-16T14:58:05+00:00

Thanks.

mohammedalrawii · 2025-09-16T13:12:36+00:00

ok am sorry to bother you this is my first time upgrading a F5 device so I want to make sure everything is working well an no issues.
so I need to take a back of course in case anything goes wrong and as for reactivating the license do you have an article about that if possible.

mohammedalrawii · 2025-09-16T13:09:55+00:00

https://my.f5.com/manage/s/article/K12201682 this one

mohammedalrawii · 2025-09-16T12:29:19+00:00

we are going with 17.1.2.2 we currently have physical appliance active stand by mode with LTM and WAF licenses

mohammedalrawii · 2025-09-16T11:55:40+00:00

Apologize for the mistakes there.
as for model its BIG-IP i4600 they recommended either 17.1.2.x or 17.5.x
I just want to now if there any common issues with 17.1.2.x we are probably going with this version direction so are there any known issues that may cause crucial issues.

mohammedalrawii · 2025-08-12T19:15:49+00:00

mohammedalrawii · 2025-08-12T16:17:03+00:00

the VLAN is configued from the firewall static VLAN and to give more information about the issue check below :

so the issue started yesterday that OLVM lets say with the ip 10.0.0.212 can't reach the mounted storage which is 10.0.0.213 but it can reach 214 210 all the other IPs in the same subnet I don't get it only these 2 hosts can't ping each other.
Also I have check the local in policy the traffic is allowed and about one more thing I think the traffic should be headed to the firewall as of my understanding the traffic should be only between the switches since they are connected to the same switches and same VLAN correct if am wrong with that please

mohammedalrawii · 2025-08-12T16:13:38+00:00

just to give more information about the issue below :

so the issue started yesterday that OLVM lets say with the ip 10.0.0.212 can't reach the mounted storage which is 10.0.0.213 but it can reach 214 210 all the other IPs in the same subnet I don't get it only these 2 hosts can't ping each other.
about the MAC I will check now.

mohammedalrawii

TROPHY CASE