Support Center > Search Results > SecureKnowledge Details
Remote Access VPN clients are not assigned their static IP addresses configured in $FWDIR/conf/ipassignment.conf file
Symptoms
  • Remote Access VPN clients are not assigned their static IP addresses configured in $FWDIR/conf/ipassignment.conf file, but from a general Office Mode IP Pool.
  • The following cosmetic issue might occur in R77.30, or after installing the hotfix from this solution on R77 / R77.10 / R77.20 versions:

    The "vpn ipafile_check" command and "vpn ipafile_users_capacity get" command incorrectly state 1024 users as the capacity when the capacity had successfully been changed:

    1. Output of "vpn ipafile_check $FWDIR/conf/ipassignment.conf detail" command returns:

      Warning: line XXX User="USERNAME" will not be added because there is no capacity to store There were XXX users that could not be added because there was no capacity to store them. Users configured is XXX out of 1024, consider increasing capacity through 'vpn ipafile_users_capacity'

    2. Output of "vpn ipafile_users_capacity get" command returns:

      The gateway can currently read 1024 users from the ipassignment.conf file
      At next policy install, the capacity will be 2048


    3. After policy installation the same issue persists. However, the involved user gets IP address from ipassignment.conf.
Cause
  • (Issue ID 01474694, Issue ID 01463675) Remote Access VPN clients are not assigned their static IP addresses configured in $FWDIR/conf/ipassignment.conf file

    Usernames read from the $FWDIR/conf/ipassignment.conf file may become corrupted after this file reaches a certain size. As a result, users will be assigned an IP address from the general Office Mode IP Pool, rather than their configured IP addresses.

  • (Issue ID 01646308) The "vpn ipafile_check" command and "vpn ipafile_users_capacity get" command incorrectly state 1024 users as the capacity.

    This is a cosmetic issue only.

Solution
Note: To view this solution you need to Sign In .