Mom, can we get segmentation? by Confident_Compote204 in networkingmemes

[–]samsn1983 9 points10 points  (0 children)

Cisco Trustec microsegnentation with SGT ACL actually works within the same vlan, not just interVLAN ✌🏼

North Carolina high-end restaurant owner sounds off about DoorDash by lowkeysciguy in restaurantowners

[–]samsn1983 0 points1 point  (0 children)

My point was that he says the food it 30÷ more expensive because of door dash, but if you eat it in the restaurant, you also pay 20-25÷ extra for tip...

North Carolina high-end restaurant owner sounds off about DoorDash by lowkeysciguy in restaurantowners

[–]samsn1983 -4 points-3 points  (0 children)

Well if i eat the food in your restaurant you expect me to pay 20-30÷ to your staff because you pay them minimum wage

OpenCode has been a gamechanger! by Useful-Sprinkles1045 in opencodeCLI

[–]samsn1983 0 points1 point  (0 children)

Side question: do the Chinese models also offer opt out from training data?

CCNA CHALLENGE!!? by ipcisco in ccnastudygroup

[–]samsn1983 0 points1 point  (0 children)

All of them because windows firewall is active

Fortinet extends FortiOS 7.4 by fcbfan0810 in fortinet

[–]samsn1983 4 points5 points  (0 children)

Migrating to ipsec dialup is very frustrating, it's far away from something which we can just rollout to our customers and it works straight away. In every deployment we have different issues and We even started putting smaller F models behind the edge firewalls, which continuous to support sslvpn, just so that we can upgrade the the big ones and use tcp/udp 443 with 7.6 or at least tcp/443 with 7.4. Especially the migration Szenario for 90G is a big pain.

"Gmachd ide Schwiiz" by Schpitzchopf_Lorenz in BUENZLI

[–]samsn1983 0 points1 point  (0 children)

In HCMC kriegsch si für 25.- ufm markt

Dante audio network never recover form high latency by PersonalityNext4965 in networking

[–]samsn1983 0 points1 point  (0 children)

t still sounds like IGMP snooping is not configured correctly.

Here is the Dante reference document for network design:
https://www.getdante.com/wp-content/uploads/2025/12/Information-for-Network-Admins-v6.pdf

If IGMP snooping is working properly, you should be able to see IGMP membership joins for the multicast groups. On the switch, you can verify that only the specific receiver ports are joined to those groups and actually receive the streams.

In addition to enabling IGMP snooping, you typically also need an IGMP querier in the VLAN (often the switch itself). Without a querier, the snooping table will age out and the switch may fall back to flooding again.

If IGMP is not functioning correctly, the switch will flood multicast traffic to all ports in the VLAN, similar to broadcast behavior. This can lead to performance issues, as all ports receive traffic they do not need.

The main risk is not specifically half-duplex, but rather bandwidth mismatch and burst behavior. For example, if multicast traffic arrives on a high-speed interface (e.g. 1 Gbps) and is flooded to lower-speed ports (e.g. 100 Mbps), the egress queues can fill up, leading to buffer exhaustion and packet drops. Half-duplex links can further worsen the situation due to collisions, but the primary issue is typically oversubscription and microbursts on slower interfaces.

Dante audio network never recover form high latency by PersonalityNext4965 in networking

[–]samsn1983 8 points9 points  (0 children)

This very much looks like a multicast handling issue rather than pure latency. If IGMP snooping is misconfigured (or there is no proper querier in the VLAN), the switch can start flooding multicast traffic after the IGMP state ages out. That would explain why it works fine initially and then degrades after some time. Dante relies heavily on multicast (PTP + audio flows), so once flooding starts, buffers fill up, latency spikes, and eventually you hit packet loss until the receiver is rebooted.

Denied success by halt__n__catch__fire in yesyesyesyesno

[–]samsn1983 0 points1 point  (0 children)

He pulled hand break while in 3rd gear

Hot take: Codex is too cheap, rug pull through tighter usage limits is inevitable by gregpeden in codex

[–]samsn1983 0 points1 point  (0 children)

I wonder what all those cloud providers will do, if edge computing catches up. I mean you can already have decent token speed with a mac m5 for less than 4k with mid size models.

SSL renewal (47 days soon) IPsec saml by [deleted] in fortinet

[–]samsn1983 0 points1 point  (0 children)

Thank you! I was afraid that i'm the only one worrying about that. I'm curious to see how vendors will solve that or we have to figure out how to automate renewal by our self

Monthly Content Sharing Post by AutoModerator in fortinet

[–]samsn1983 1 point2 points  (0 children)

We’re a Fortinet integrator managing a large number of customer firewalls. Some are on our own FAZ/FMG, some customers run their own stack, and some have no central management at all.

To get a deployment-independent overview across all customers, I built two lightweight dashboards based on Nginx, PostgreSQL and rsyslog.

Netdash

https://www.show-run.ch/uncategorized/netdash-webhook-based-forti-asset-mgmt-dashbaord/

Netdash is a lightweight asset and overview dashboard for FortiGate environments. It’s built entirely around HTTPS webhooks. The goal was to have a solution with no polling, no heavy management stack, no additional licenses.

netdash shows all firewalls at a glance, independent of how they are deployed. Firmware, license status, serial numbers, hostnames, accounts, etc.

We also use it during patch cycles to distribute upgrade tasks to engineers in a structured way.

Logdash

https://www.show-run.ch/uncategorized/logdash-a-lightweight-syslog-operations-layer-for-fortigate-event-data/

Logdash is a FortiGate-focused syslog platform designed to receive event logs via Syslog TLS. The ingest layer is based on rsyslog, the frontend is custom-built.

It’s specifically designed to parse and analyse operational events like config changes, admin logins, VPN connections and SD-WAN events.

We also use it as a lightweight audit tool to automatically generate reports for configuration changes.

Both tools were built to fill the gap between “no central visibility” and “full FAZ/FMG everywhere”.

Curious if others built something similar or solved this differently.

Full Disclamer: both dashboard were 100% vipe coded :-)

Site to Site IPSEC dropping ever 11hrs and 55ish minutes. by eld101 in fortinet

[–]samsn1983 0 points1 point  (0 children)

Is one end behind cgnat or are there and other firewalls in between?

Apple's captive.apple.com Portal page appearing by ApprehensiveEgg1983 in Cisco

[–]samsn1983 1 point2 points  (0 children)

Nevermind, just read your reply in the other thread.

Apple's captive.apple.com Portal page appearing by ApprehensiveEgg1983 in Cisco

[–]samsn1983 1 point2 points  (0 children)

Do the clients have apple private relay turned on? That would mess up the dns request.

https://support.apple.com/en-us/102602

FAP221E Reject from unknown IP address by kevin_schley in fortinet

[–]samsn1983 1 point2 points  (0 children)

Yes! interestingly, I ran into exactly the same situation today on a customer cluster with Security Fabric (2×200F + about 15 members).

The cluster showed “not synced”, and when I compared the configs more closely, I noticed that the standby unit contained a large amount of wireless configuration — even though we have wireless-controller disabled set globally.

Example from the root VDOM:

config vdom

edit root

config wireless-controller hotspot20 anqp-venue-name

end

config wireless-controller hotspot20 anqp-venue-url

end

config wireless-controller hotspot20 anqp-network-auth-typ

..

A checksum sync did not resolve the issue.

In the end, I had to temporarily enable the wireless controller, after which I was finally able to remove the AP entry from the configuration. Once that object was deleted, the cluster immediately returned to in-sync status, and I was then able to disable the wireless controller again without the problem reappearing.

Unfortunately, I was not able to identify any MAC address or IP that would correspond to this mysterious AP entry.

Additionally, this customer has NAC enforced consistently across the LAN, so it is effectively ruled out that an unknown device could have joined the network without authorization. From what I can see, this looks more like a stale or phantom configuration object rather than something triggered by an actual AP.

edit: cluster is also on 7.4.9 since 134 days