- CheckMates
- :
- Products
- :
- General Topics
- :
- Re: CoreXL and Loopback
Options
- 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?
×
Sign in with your Check Point UserCenter/PartnerMap account to access more great content and get a chance to win some Apple AirPods! If you don't have an account, create one now for free!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
CoreXL and Loopback
Hi There,
For lab test I should assign a Loopback interface into the only one CPU using CoreXL. I've created loopback interface loop00 and I have 4 CPU. I've enabled all 4 CPU using cpconfig and coreXL, but when i trying to assign CPU 3 to loopback interface I'm getting the error "Interface is invalid. Check that the interface loop00 is active physical interface". I've run the following CLI "fw ctl affinity -s -i loop00 CPU_ID 3". What's wrong I do or I can only assign CPU for a physical interface?
3 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Pretty sure you cannot assign a core to a loopback interface, only physical ones.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Logical you correct but I didn't find any clear documentation or line that it says only for physical interfaces. Maybe somebody can send me a link?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The error message pretty clearly says only active, physical interfaces are supported.
A loopback interface is NOT a physical interface.
The Secure Network Distributor only handles traffic entering network interface cards (NICs), as noted in the ATRG: https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...
It still begs the question: why you want to assign a core to a loopback interface?
A loopback interface is NOT a physical interface.
The Secure Network Distributor only handles traffic entering network interface cards (NICs), as noted in the ATRG: https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solut...
It still begs the question: why you want to assign a core to a loopback interface?
