<?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 Re: Office Mode IP assignment by client type in Mobile</title>
    <link>https://community.checkpoint.com/t5/Mobile/Office-Mode-IP-assignment-by-client-type/m-p/214856#M1147</link>
    <description>&lt;P&gt;The others are correct. &amp;nbsp;If you're looking to differentiate traffic by client type, then Access Roles are your answer here. &amp;nbsp;You can define an Access Role object by client type, and use those in your policy.&lt;/P&gt;
&lt;P&gt;For best results, you can also define an access role for your regular users and again use that in your policy. &amp;nbsp;With this, you can remove the "legacy user access" rule for "Vpn_users@any" in the source column AND you can remove the RemoteAccess community from the VPN column. &amp;nbsp;You will use the access roles to control VPN user traffic; either by your client type roles, or your user-identity roles, or both. &amp;nbsp;Your user identity roles can refer to internal/local user, AD/LDAP users, LDAP OUs, AD security groups.... whatever you need.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 20 May 2024 18:32:53 GMT</pubDate>
    <dc:creator>Duane_Toler</dc:creator>
    <dc:date>2024-05-20T18:32:53Z</dc:date>
    <item>
      <title>Office Mode IP assignment by client type</title>
      <link>https://community.checkpoint.com/t5/Mobile/Office-Mode-IP-assignment-by-client-type/m-p/214818#M1144</link>
      <description>&lt;P&gt;Hi CheckMates!&lt;BR /&gt;&lt;BR /&gt;Is it possible to assign office mode IP addresses by client type?&lt;BR /&gt;&lt;BR /&gt;For example, Capsule VPN Android users get IP address from one OM pool, SSL Network Extender user from another OM pool, Check Point Mobile users from yet another OM pool, etc.&lt;BR /&gt;&lt;SPAN&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;/SPAN&gt;rooKing&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2024 08:33:01 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Mobile/Office-Mode-IP-assignment-by-client-type/m-p/214818#M1144</guid>
      <dc:creator>rooKing</dc:creator>
      <dc:date>2024-05-20T08:33:01Z</dc:date>
    </item>
    <item>
      <title>Re: Office Mode IP assignment by client type</title>
      <link>https://community.checkpoint.com/t5/Mobile/Office-Mode-IP-assignment-by-client-type/m-p/214844#M1145</link>
      <description>&lt;P&gt;Not aware of a way to do this at current.&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2024 14:39:55 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Mobile/Office-Mode-IP-assignment-by-client-type/m-p/214844#M1145</guid>
      <dc:creator>PhoneBoy</dc:creator>
      <dc:date>2024-05-20T14:39:55Z</dc:date>
    </item>
    <item>
      <title>Re: Office Mode IP assignment by client type</title>
      <link>https://community.checkpoint.com/t5/Mobile/Office-Mode-IP-assignment-by-client-type/m-p/214854#M1146</link>
      <description>&lt;P&gt;Im 100% positive you canNOT do that.&lt;/P&gt;
&lt;P&gt;Andy&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2024 18:11:06 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Mobile/Office-Mode-IP-assignment-by-client-type/m-p/214854#M1146</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-05-20T18:11:06Z</dc:date>
    </item>
    <item>
      <title>Re: Office Mode IP assignment by client type</title>
      <link>https://community.checkpoint.com/t5/Mobile/Office-Mode-IP-assignment-by-client-type/m-p/214856#M1147</link>
      <description>&lt;P&gt;The others are correct. &amp;nbsp;If you're looking to differentiate traffic by client type, then Access Roles are your answer here. &amp;nbsp;You can define an Access Role object by client type, and use those in your policy.&lt;/P&gt;
&lt;P&gt;For best results, you can also define an access role for your regular users and again use that in your policy. &amp;nbsp;With this, you can remove the "legacy user access" rule for "Vpn_users@any" in the source column AND you can remove the RemoteAccess community from the VPN column. &amp;nbsp;You will use the access roles to control VPN user traffic; either by your client type roles, or your user-identity roles, or both. &amp;nbsp;Your user identity roles can refer to internal/local user, AD/LDAP users, LDAP OUs, AD security groups.... whatever you need.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2024 18:32:53 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Mobile/Office-Mode-IP-assignment-by-client-type/m-p/214856#M1147</guid>
      <dc:creator>Duane_Toler</dc:creator>
      <dc:date>2024-05-20T18:32:53Z</dc:date>
    </item>
    <item>
      <title>Re: Office Mode IP assignment by client type</title>
      <link>https://community.checkpoint.com/t5/Mobile/Office-Mode-IP-assignment-by-client-type/m-p/214872#M1148</link>
      <description>&lt;P&gt;excellent point!&lt;/P&gt;</description>
      <pubDate>Tue, 21 May 2024 07:48:24 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Mobile/Office-Mode-IP-assignment-by-client-type/m-p/214872#M1148</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2024-05-21T07:48:24Z</dc:date>
    </item>
  </channel>
</rss>

