So, I'd put in a support ticket for this against the 6.4.x firmware
because it definitely behaves there's a bug where VIPs are being applied
to everything and were likely ignoring the src-filters, and just got
back around to poking at it on the newer...
Scope: At least all Fortinet-101F units running 6.4.11, and I have no
doubt it applies to basically any unit capable of running a DHCP server
or relay (and didn't notice any mention of it being fixed in newer
versions).Severity: CVSS < 1 (Let's not g...
Product: Fortimanager-VM64Version: v7.0.4 build0306So, this is just
super fun. Upgrading a Fortigate from 6.4.x to 7.x requires using a 7.x
ADOM, but once you do that if you have any VIP range definitions, they
break and you can no longer push policy...
Let me make this absolutely crystal clear. Go away. Your gaslighting is
not needed. I have figured the problem out. Breaking down complex
problems into successively smaller pieces and then testing and analyzing
those pieces until I have identified an...
More or less. It's something that really commonly throws people, but
VLAN 1 is not actually tagged. Once you're doing VLANs typically the
most sensible thing to do is start making all the ports on your switch
bind to a specific VLAN and only allow 1 ...
You also don't have a pair of Fortigate 601E in HA mode, or any
Fortigate 101F's, or any experience in actually running these things at
an enterprise level, nor apparently do you have a device running the
matching minor release firmware, or the abili...
@gfleming wrote:Oh you're the guy who wanted to put tab-delimiters
everywhere in the DHCP cli lease output. Right, makes sense now! Your
response and attitude sounded familiar.....Yeah my "attitude" is one
that is developed after spending hours caref...
That's going to be a hard no. While I understand your bosses have you
guys under orders to respond to every post within 24 hours, I'm pretty
sure when they came up with that what they had in mind was not
low-effort garbage posts. The only "effort" yo...
