<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Split tunneling VPN for specific users in SASE and Remote Access</title>
    <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Split-tunneling-VPN-for-specific-users/m-p/209961#M3916</link>
    <description>&lt;P&gt;Attempting to create a split tunnel VPN for specific remote users. we followed SK&amp;nbsp;&lt;A href="https://support.checkpoint.com/results/sk/sk114882" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk114882&lt;/A&gt;&amp;nbsp;created a new user group with the "ttm" prefix we then copied, renamed, and modified the trac_client_1.ttm file following scenerio 1 of the SK posted. The test user is still unable to connect. We ran the vpn check_ttm command and the file passed the check. Looking through the logs on the client side its showing that the default trac file is being used and not the new modified one. We think it might be an identity awareness issue but are unsure of next steps.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 28 Mar 2024 15:14:18 GMT</pubDate>
    <dc:creator>mmbiggs</dc:creator>
    <dc:date>2024-03-28T15:14:18Z</dc:date>
    <item>
      <title>Split tunneling VPN for specific users</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Split-tunneling-VPN-for-specific-users/m-p/209961#M3916</link>
      <description>&lt;P&gt;Attempting to create a split tunnel VPN for specific remote users. we followed SK&amp;nbsp;&lt;A href="https://support.checkpoint.com/results/sk/sk114882" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk114882&lt;/A&gt;&amp;nbsp;created a new user group with the "ttm" prefix we then copied, renamed, and modified the trac_client_1.ttm file following scenerio 1 of the SK posted. The test user is still unable to connect. We ran the vpn check_ttm command and the file passed the check. Looking through the logs on the client side its showing that the default trac file is being used and not the new modified one. We think it might be an identity awareness issue but are unsure of next steps.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 28 Mar 2024 15:14:18 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Split-tunneling-VPN-for-specific-users/m-p/209961#M3916</guid>
      <dc:creator>mmbiggs</dc:creator>
      <dc:date>2024-03-28T15:14:18Z</dc:date>
    </item>
    <item>
      <title>Re: Split tunneling VPN for specific users</title>
      <link>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Split-tunneling-VPN-for-specific-users/m-p/210268#M3917</link>
      <description>&lt;P&gt;Please consult with TAC&lt;/P&gt;</description>
      <pubDate>Tue, 02 Apr 2024 12:32:31 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/SASE-and-Remote-Access/Split-tunneling-VPN-for-specific-users/m-p/210268#M3917</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2024-04-02T12:32:31Z</dc:date>
    </item>
  </channel>
</rss>

