- CheckMates
- :
- Products
- :
- Quantum
- :
- Security Gateways
- :
- Re: Implementing vlan interfaces on a physical int...
- 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
Implementing vlan interfaces on a physical interface that doesnt have a physical IP.
Hello Experts,
I want to migrate from Cisco Router to a Checkpoint Device.
My challenge; how do i interpret the following config from Cisco Router on the Checkpoint Network Management Interface;
interface GigabitEthernet0/0
no ip address
ip flow ingress
duplex auto
speed auto
!
interface GigabitEthernet0/0.1
encapsulation dot1Q 1 native
ip address 10.10.10.1 255.255.255.0
ip flow ingress
!
interface GigabitEthernet0/0.40
description ***-VOIP***
encapsulation dot1Q 40
ip address 172.31.125.1 255.255.255.0
ip flow ingress
ip nat inside
ip virtual-reassembly in
ip policy route-map VOIPEXCH
!
interface GigabitEthernet0/0.100
description ***f-staff***
encapsulation dot1Q 100
ip address 192.168.100.1 255.255.255.0
ip flow ingress
ip nat inside
ip virtual-reassembly in
ip policy route-map LAN
!
interface GigabitEthernet0/0.101
description ***staff-2***
encapsulation dot1Q 101
ip address 192.168.101.1 255.255.255.0
ip flow ingress
ip nat inside
ip virtual-reassembly in
ip policy route-map LAN
!
interface GigabitEthernet0/0.102
description ***Guest***
encapsulation dot1Q 102
ip address 192.168.102.1 255.255.255.0
ip access-group GUEST in
ip flow ingress
ip nat inside
ip virtual-reassembly in
ip policy route-map LAN
Please how can i implement this sort of vlan on Checkpoint??
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This can be configured on Gaia by assigning native VLAN IP to the physical interface and configuring VLANs with the respective IP. But this is not supported on a ClusterXL cluster!
So if you are implementing a cluster, you should migrate VLAN 1 to either a separate interface using access port or by changing VLAN id.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Norbert,
Thank you for your input.
So in my case; The physical ip i assign to the interface (assume eth2) will be 10.10.10.1 (native vlan ip on the config file i posted), then i add the other vlans to eth2??
Please confirm that my assumption is correct.
Thank you for your swift response.
Best Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please had a look at the discussion here:
It is not supported having an IP configured on the native interface if tagged VLANs used on that interface.
I know, it will work but you have problems if you need support from the vendor.
And in your Cisco configuration VLAN 1 (native VLAN) is tagged with VLAN ID 1, it is not supported to have a tagged VLAN with ID 1 ( sk110096 )
As Norbert suggest, it would be the best to have VLAN 1 on another physical interface without VLAN tag, not the one with the tagged VLANs.
Wolfgang
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you, Norbert and Wolfgang.
I will update you once I have implemented this.
Also, I assume that i will have to create static routes on the Firewall, informing the firewall that the nexthop to those vlans is the Switch!
Kind Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
