- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Allow all VLANs on a Bridge Interface
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Allow all VLANs on a Bridge Interface
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
To confirm the setting
[Expert@Hostname] # fw ctl get int fw_bridge_antispoofing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
