<?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: WatchGuard SSLVPN with Radius in Managing Users</title>
    <link>https://community.cisco.com/t5/managing-users/watchguard-sslvpn-with-radius/m-p/4883565#M998</link>
    <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;It looks like you solved this by updating the port in this thread: &lt;A href="https://community.duo.com/t/watchguard-sslvpn-with-radius/10847" class="inline-onebox"&gt;WatchGuard SSLVPN with Radius&lt;/A&gt;.&lt;/P&gt;&lt;/DIV&gt;</description>
    <pubDate>Mon, 15 Nov 2021 13:57:30 GMT</pubDate>
    <dc:creator>DuoKristina</dc:creator>
    <dc:date>2021-11-15T13:57:30Z</dc:date>
    <item>
      <title>WatchGuard SSLVPN with Radius</title>
      <link>https://community.cisco.com/t5/managing-users/watchguard-sslvpn-with-radius/m-p/4883564#M997</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;So setup WatchGuard Radius per Duo documentation.&lt;BR /&gt;
Setup AD User group VPN and added to NPS and also added to VPN group for SSLVPN on Firebox.&lt;BR /&gt;
When I go to authenticate with user get an error on Server “A RADIUS message was received from the invalid RADIUS client IP address 192.168.0.1.” (192.168.0.1 is WatchGuard)&lt;BR /&gt;
Proxy Config&lt;BR /&gt;
[radius_client]&lt;BR /&gt;
host=127.0.0.1&lt;BR /&gt;
secret=XXXXXXXXXXXXXXXX&lt;BR /&gt;
pass_through_all=true&lt;BR /&gt;
[radius_server_auto]&lt;BR /&gt;
ikey=XXXXXXXXXXXXXXXXXXXX&lt;BR /&gt;
■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■&lt;BR /&gt;
api_host=&lt;A href="http://api-XXXXXXXXXX.duosecurity.com" rel="noopener nofollow ugc"&gt;■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■&lt;/A&gt;&lt;BR /&gt;
radius_ip_1=192.168.0.1&lt;BR /&gt;
radius_secret_1=radiuspassword&lt;BR /&gt;
client=radius_client&lt;BR /&gt;
port=1645&lt;BR /&gt;
failmode=safe&lt;BR /&gt;
pass_through_all=true&lt;/P&gt;
&lt;P&gt;NPS is on the same server as proxy, Also tried using port 1812.&lt;BR /&gt;
Both running on Windows Server 2019&lt;/P&gt;
&lt;P&gt;Have a Case open with Duo but it’s been a 24hrs and still sitting as pending.&lt;BR /&gt;
Thanks,&lt;BR /&gt;
Tom&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 11 Nov 2021 15:07:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/managing-users/watchguard-sslvpn-with-radius/m-p/4883564#M997</guid>
      <dc:creator>tshemon</dc:creator>
      <dc:date>2021-11-11T15:07:14Z</dc:date>
    </item>
    <item>
      <title>Re: WatchGuard SSLVPN with Radius</title>
      <link>https://community.cisco.com/t5/managing-users/watchguard-sslvpn-with-radius/m-p/4883565#M998</link>
      <description>&lt;DIV class="duo-migrated-content"&gt;&lt;P&gt;It looks like you solved this by updating the port in this thread: &lt;A href="https://community.duo.com/t/watchguard-sslvpn-with-radius/10847" class="inline-onebox"&gt;WatchGuard SSLVPN with Radius&lt;/A&gt;.&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 15 Nov 2021 13:57:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/managing-users/watchguard-sslvpn-with-radius/m-p/4883565#M998</guid>
      <dc:creator>DuoKristina</dc:creator>
      <dc:date>2021-11-15T13:57:30Z</dc:date>
    </item>
  </channel>
</rss>

