- Products
- Learn
- Local User Groups
- Partners
- More
MVP 2026: Submissions
Are Now Open!
What's New in R82.10?
Watch NowOverlap in Security Validation
Help us to understand your needs better
CheckMates Go:
Maestro Madness
Hello, Mates.
Is there a way to configure in the “Bridge Mode” interface of a FW CP, the option to allow all VLANS?
I have 1 box with 2 interfaces in bridge mode.
This box is in the middle of 2 Routers, which currently have configured on the ports that connects them, multiple VLANs.
So, I want the br1 interface that has my 2 physical interfaces to “allow all these VLANs without any exception”.
The routers currently pass more than 30 VLANs, and manually making 1 bridge group for each VLAN is not very productive.
Is there a way to make the br1 interface that has the 2 physical interfaces as such, “allow” all VLANs?
Greetings.
From what I remember, if you just create a bridge with just the physical interfaces, it will pass all the VLANs.
That's basically what this SK does while telling you to also disable bridge anti-spoofing (needed in this case): https://support.checkpoint.com/results/sk/sk34312
Hello.
If I apply the SK, how can you validate that the change has actually been made and has the value recommended in the document?
To disable Anti-Spoofing, set the global parameter fw_bridge_antispoofing to 0.
[Expert@Hostname] # fw ctl set int fw_bridge_antispoofing 0
Note: This configuration will be lost after the reboot. To set it to be permanent, run:
[Expert@Hostname]# echo "fw_bridge_antispoofing=0">> $FWDIR/modules/fwkern.conf
Thanks.
To confirm the setting
[Expert@Hostname] # fw ctl get int fw_bridge_antispoofing
Hello,
The option to validate the current antispoofing status does not seem to work.
Is the command you shared correct?
[Expert@FW-WF:0]#
[Expert@FW-WF:0]# fw ctl get int fw_bridge_antispoofing
Get operation failed: failed to get parameter fw_bridge_antispoofing
get: Operation failed
Killed
Cheers.
The only reason you get that is the kernel variable referenced doesn't exist.
Which means this SK is not correct, at least on current versions.
However, I think you should be ok if you disable anti-sppofing on the relevant bridge interface in SmartConsole.
So it should be enough if I remove the Antispoofing on the 2 interfaces that form the br1?
Because in the topology of the GW from the SmartConsole, there is no “br1” interface, but the 2 interfaces that make the “br1” appear.
I believe you are correct: disable anti-spoofing on the two interfaces that make up br1.
If traffic originating from the gateway itself flows over the bridge, you will have to make other adjustments to account for "local interface anti-spoofing."
For that, see: https://support.checkpoint.com/results/sk/sk105899
If I'm understanding this correctly these steps disable anti-spoofing globally (not just on the bridge interface), among other things.
Leaderboard
Epsum factorial non deposit quid pro quo hic escorol.
| User | Count |
|---|---|
| 20 | |
| 19 | |
| 18 | |
| 8 | |
| 7 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 3 |
Tue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsTue 16 Dec 2025 @ 05:00 PM (CET)
Under the Hood: CloudGuard Network Security for Oracle Cloud - Config and Autoscaling!Thu 18 Dec 2025 @ 10:00 AM (CET)
Cloud Architect Series - Building a Hybrid Mesh Security Strategy across cloudsAbout CheckMates
Learn Check Point
Advanced Learning
YOU DESERVE THE BEST SECURITY