Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
well yes it will due to the arp/ipv4 protocolls ;)
So yes you might not be able to make per device policies depending on the mac.
What you could do is dhcp reservations to have somewhat fixed ips and do ip based policies.
That's what we do here since we only need policies for complete subnets or if we do need one for one device we do dhcp reservation or even static ips (e.g. servers have static internal ips).
But this will happen even if you do inter-vlan-routing on the core switch at least for packets that leave the core switch to somewhere not on this switch ;)
--
"It is a mistake to think you can solve any major problems just with potatoes." - Douglas Adams
hello,
i posted a thread yesterday with this same question. The only problem that i have with this is that traffic comming from other vlans will capture the core switch mac address, so you won't be able to do policies based on devices from other vlans.
i.e: core routes vlan1,2 and 3. FG is on vlan3. devices from 1 and 2 do not show up in fortigate.
On a costumer, what i did in the past was to implement FSSO and i use policies based on Active Directory groups. The costumer is happy.
But I'm considering to do it different this time:
One of the vlans has only fixed ip servers, the other vlan has the dhcp clients. I'm thinking of putting the FG on devices vlan - it will see all of of them, so I can say that device1-mac can go to google, and device2-mac can not. Since devices on the other vlan are fixed ip, you can actually list them manually in fortigate and do policies based on their ip, and overcome core switch the mac-address issue.
[Sorry for double post but this is obviously a bug in this forum - I clicked the right posting I wanted to reply to but even though if you click the big "Reply" button above it always takes the wrong one :( - also there is no way to delete your own wrong posting]
well yes it will due to the arp/ipv4 protocolls ;) So yes you might not be able to make per device policies depending on the mac. What you could do is dhcp reservations to have somewhat fixed ips and do ip based policies. That's what we do here since we only need policies for complete subnets or if we do need one for one device we do dhcp reservation or even static ips (e.g. servers have static internal ips). But this will happen even if you do inter-vlan-routing on the core switch at least for packets that leave the core switch to somewhere not on this switch ;)
--
"It is a mistake to think you can solve any major problems just with potatoes." - Douglas Adams
Right, I believe this is where i'm going. I'm narrowing it down to 2 vlans.
I'm told that FSSO is working pretty good, i will still consider user based policies as a long run, but for now, at least, with this arp/ipv4 protocol, i have it covered.
Thanks a lot for the input ;)
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1688 | |
1087 | |
752 | |
446 | |
228 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.