Unable to Send Radius Request Across the VPN from Dedicated Interfaces

Description

Issue- Not able to send Radius Request across the VPN from dedicated interfaces

Cause

Binding effect of inbuilt Feature "SEND THROUGH VPN TUNNEL"

Resolution

 

 

Image

 

 

We configured the Radius Server on Site A’s SonicWall and enabled “SEND THROUGH VPN TUNNEL”:

 

Image

After setting up the Radius Server on Site A and Site to Site VPN, we tried to test a User and found that the request was going through X0 interface instead of X1:V10 interface:

 

Image

 

 

After running a couple of tests we were unable to redirect the traffic via X1:V10 interface as X0 interface was always taking precedence. So for testing purpose we UNCHECKED the “SEND THROUGH VPN TUNNEL” check box and traffic started redirecting through X1:V10 interface.

 

So the conclusion to the above discussed issue is, if you want to redirect traffic to send Radius requests via a dedicated interface of your choice then “SEND THROUGH VPN TUNNEL” must be unchecked.

 

Example, we have the option to redirect traffic for SYSLOGS via dedicated interface:

 

 

Similarly, we can do the same for Radius server but by unchecking the “SEND THROUGH VPN TUNNEL” check box.

Related Articles

  • Supported Storage Modules on SonicWall Firewalls running SonicOS/X 7 and above
    Read More
  • TZ シリーズのエラー メッセージ:「 高可用性は無線と一緒に使用できません」
    Read More
  • Supported SonicWall and 3rd party SFP and SFP+ modules that can be used with SonicWall NSA series
    Read More
not finding your answers?