مشکل احراز هویت یوزرمنیجر میکروتیک و چند لاگ

سلام وقت بخیر

برای اتصال سمت کلاینت ها از anyconnect یا open connect استفاده میشه

radcli بدو tls هست

روی سروری که ocserv نصب شده اگر منظورتون باشه - در فایل کانفیگ یعنی radiusclient.conf دو مورد زیر فقط هست بصورت پیش فرض در اینجا

که این دو مورد رو اعدادش رو بالا یا پایین ترم گذاشتم اما چیزی تغییر نکرد ظاهرا

# time to wait for a reply from the RADIUS server
radius_timeout  3

# resend request this many times before trying the next server
radius_retries  1

داخل میکروتیک  مستقیم رفتم توی یوزرمنیجر و اونجا سرور ocserver رو اضاف کردم -هیچ چیز اضافه ای تنظیم نکردم

لطفا خروجی دستور زیر رو ارسال کنید :

sudo journalctl -eu ocserv

محتویات فایل etc/ocserv/ocserv.conf/ رو هم ارسال کنید.

لطفا برای ارسال خروجی از قسمت پاراگراف -> بلوک ها -> کد استفاده کنید. لطفا و ممنونم.

حالا برسی میکنم بببینم چی میشه نتیجه .

--

راستی سشن های بیکار در یوزر منیجر میکروتیک اصلا بسته نمیشن ؟  کلا سشن ها فعال میمونن حتی  اگه طرف گوشیش خاموش بشه  یا اینترنت قطع بشه اما بازم سشن بسته نمیشه داخل یوزمنیجر میکروتیک(حتی علامت اکتیو کنار سشن باقی میمونه تا ... )

آیا این مورد قابل برطرف کردن هست ؟ من میکروتیک 7.7 و حتی جدید ترین ورژن هم تست کردم همینجوری هست

ایا اسکریپتی یا دستوری برای رفعش وجود داره ؟

سلام

ممنون مهندس

این فیچرهای مختلف توی همین خط دستور tls  باعث قطع شدن برخی از  یوزرها نمیشه ؟ مثلا tls3 فقط باشه منظورم هست- من فعلا روی سرور تست جایگزین کردم و مورد لاگ tls رو ندیدم فعلا .

-------------

در واقع مشکل اصلی که من دنبال رفعش هستم اینکه وقتی یک یوزر با گوشی لاگین میکنه تا زمانیکه کارمیکنه همه چی براش اوکی هست - اما زمانیکه گوشی رو میبنده و در حالت اسکرین لاک میره و بعد مدتی برمیگره میخواد با گوشی کار کنه یا اون یوزر قطع شده یا اون یوزر متصله اما دیتا نداره در خیلی از تایم ها این مشکل وجود داره (در صورتیکه این مشکل اصلا در ویندوز وجود نداره و حتی توی لاگ یوزری که با ویندوز لاگین میکنه اون خط اخر لاگ هیچوقت رخ نمیده و یوزر اصلا قطع نمیشه)

نمونه ای از لاگ یکی از یوزرها مثل زیر هست خط اخر گفته user disconnected  دقیقا بلافاصله بعد از اتصال و یا برخی اوقات هم دیرتر این خط لاگ رو میندازه -ایا این رو میشه حل کرد ؟

باتشکر

Nov 20 14:50:29 S200.TAKDOR.PW ocserv[121169]: main:127.0.0.1:37236 user disconnected (reason: unspecified, rx: 0, tx: 0)
Nov 20 14:52:00 S200.TAKDOR.PW ocserv[121180]: sec-mod: using 'radius' authentication to authenticate user (session: 5FdH8B)
Nov 20 14:52:04 S200.TAKDOR.PW ocserv[121180]: radius-auth: communicating username (meysam-mob) and password
Nov 20 14:52:04 S200.TAKDOR.PW ocserv[121180]: [40B blob data]
Nov 20 14:52:04 S200.TAKDOR.PW ocserv[121180]: radius-auth: ignoring server's value 80 of type 0
Nov 20 14:52:05 S200.TAKDOR.PW ocserv[121169]: main:127.0.0.1:37252 user disconnected (reason: unspecified, rx: 0, tx: 0)
Nov 20 14:52:06 S200.TAKDOR.PW ocserv[121169]: main:127.0.0.1:37256 user disconnected (reason: unspecified, rx: 0, tx: 0)
Nov 20 14:52:07 S200.TAKDOR.PW ocserv[121180]: radius-auth: opening session 5FdH8B5M5GbmIUIeObzufuQ5574=
Nov 20 14:52:07 S200.TAKDOR.PW ocserv[121169]: main[meysam-mob]:127.0.0.1:37260 new user session
Nov 20 14:52:07 S200.TAKDOR.PW ocserv[121180]: sec-mod: initiating session for user 'meysam-mob' (session: 5FdH8B)
Nov 20 14:52:07 S200.TAKDOR.PW ocserv[121169]: main[meysam-mob]:127.0.0.1:37260 user logged in
Nov 20 14:52:07 S200.TAKDOR.PW ocserv[122168]: worker[meysam-mob]: 127.0.0.1 suggesting DPD of 8192 secs
Nov 20 14:52:07 S200.TAKDOR.PW ocserv[122168]: worker[meysam-mob]: 127.0.0.1 configured link MTU is 1500
Nov 20 14:52:07 S200.TAKDOR.PW ocserv[122168]: worker[meysam-mob]: 127.0.0.1 peer's link MTU is 1500
Nov 20 14:52:07 S200.TAKDOR.PW ocserv[122168]: worker[meysam-mob]: 127.0.0.1 sending IPv4 10.10.10.43
Nov 20 14:52:07 S200.TAKDOR.PW ocserv[122168]: worker[meysam-mob]: 127.0.0.1 adding DNS 8.8.8.8
Nov 20 14:52:07 S200.TAKDOR.PW ocserv[122168]: worker[meysam-mob]: 127.0.0.1 adding DNS 1.1.1.1
Nov 20 14:52:07 S200.TAKDOR.PW ocserv[122168]: worker[meysam-mob]: 127.0.0.1 Link MTU is 1500 bytes
Nov 20 14:52:08 S200.TAKDOR.PW ocserv[121169]: main:127.0.0.1:37248 user disconnected (reason: unspecified, rx: 0, tx: 0)

پارامتر های mobile-idle-timeout و idle-timeout رو هم از حالت comment خارج کنید و براش مقدار مناسبی بزارید. اینجور پارامتر ها منطقا باید فعال باشن. خط زیر رو هم تکراری نوشتید که حذفش کنید :

#max-clients = 1024

و بزارید اون یکی بمونه که comment نیستش :

max-clients = 0

مقدار auth-timeout رو هم تغییر بدید. این پارامتر تعیین می کنه که یوزر تا چه زمانی (به ثانیه ، نه قرن!) میتونه متصل بمونه به VPN Server ، قبل از اینکه احرازهویت بشه. البته از لحاظ امنیتی باید اول احرازهویت کنه یوزر رو ولی خوب به هر حال ... مقدار پیش فرضش که 240 هست بزارید باشه.

دوست عزیز مشکل تون برطرف شد ؟ لطفا اطلاع بدید. ممنونم

مقدار keepalive رو که تغییر دادید درست شد مشکل قطعی اتصال ؟ الان فقط همین لاگ ها رو دارید ؟

"این لاگ ها باعث میشه که ادرس سرور از دسترسس خارج بشه"

لطفا در این مورد بیشتر توضیح بدید.

لاگ های زیر خدمت شما:

root@cisco:/etc/radcli# sudo journalctl -eu ocserv
Nov 19 11:51:30 cisco.mikrotik.com ocserv[40968]: worker[meysam-mob]: 127.0.0.1 adding DNS 1.1.1.1
Nov 19 11:51:30 cisco.mikrotik.com ocserv[40968]: worker[meysam-mob]: 127.0.0.1 Link MTU is 1500 bytes
Nov 19 11:51:30 cisco.mikrotik.com ocserv[40968]: worker[meysam-mob]: 127.0.0.1 selected DTLS compression method lzs
Nov 19 11:51:30 cisco.mikrotik.com ocserv[40968]: worker[meysam-mob]: 127.0.0.1 selected CSTP compression method lzs
Nov 19 11:51:30 cisco.mikrotik.com ocserv[32307]: main:127.0.0.1:37968 user disconnected (reason: unspecified, rx: 0, tx: 0)
Nov 19 12:04:13 cisco.mikrotik.com ocserv[40968]: worker[meysam-mob]: 127.0.0.1 received BYE packet; exiting
Nov 19 12:04:13 cisco.mikrotik.com ocserv[32308]: radius-auth: sending session interim update
Nov 19 12:04:14 cisco.mikrotik.com ocserv[40968]: worker[meysam-mob]: 127.0.0.1 sent periodic stats (in: 240090, out: 712157) to sec-mod
Nov 19 12:04:14 cisco.mikrotik.com ocserv[32308]: sec-mod: invalidating session of user 'meysam-mob' (session: 5RVCqa)
Nov 19 12:04:14 cisco.mikrotik.com ocserv[32308]: radius-auth: closing session
Nov 19 12:04:14 cisco.mikrotik.com ocserv[32307]: main[meysam-mob]:127.0.0.1:37980 user disconnected (reason: user disconnected, rx: 240090, tx: 712157)
Nov 19 12:06:46 cisco.mikrotik.com ocserv[32308]: sec-mod: using 'radius' authentication to authenticate user (session: zlIRjD)
Nov 19 12:06:47 cisco.mikrotik.com ocserv[32308]: radius-auth: communicating username (wolf) and password
Nov 19 12:06:50 cisco.mikrotik.com ocserv[32307]: main:127.0.0.1:37996 user disconnected (reason: unspecified, rx: 0, tx: 0)
Nov 19 12:10:45 cisco.mikrotik.com ocserv[32307]: main:127.0.0.1:38000 user disconnected (reason: unspecified, rx: 0, tx: 0)
Nov 19 12:11:10 cisco.mikrotik.com ocserv[32308]: sec-mod: using 'radius' authentication to authenticate user (session: ibGjp+)
Nov 19 12:11:11 cisco.mikrotik.com ocserv[32308]: radius-auth: communicating username (wolf) and password
Nov 19 12:11:11 cisco.mikrotik.com ocserv[32308]: [40B blob data]
Nov 19 12:11:11 cisco.mikrotik.com ocserv[32308]: radius-auth: ignoring server's value 80 of type 0
Nov 19 12:11:11 cisco.mikrotik.com ocserv[32308]: radius-auth: opening session ibGjp+Ycnd9GtexmnYx9zLfeKU4=
Nov 19 12:11:11 cisco.mikrotik.com ocserv[32308]: sec-mod: initiating session for user 'wolf' (session: ibGjp+)
Nov 19 12:11:11 cisco.mikrotik.com ocserv[32307]: main[wolf]:127.0.0.1:38004 new user session
Nov 19 12:11:11 cisco.mikrotik.com ocserv[32307]: main[wolf]:127.0.0.1:38004 user logged in
Nov 19 12:11:11 cisco.mikrotik.com ocserv[47923]: worker[wolf]: 127.0.0.1 suggesting DPD of 8192 secs
Nov 19 12:11:11 cisco.mikrotik.com ocserv[47923]: worker[wolf]: 127.0.0.1 configured link MTU is 1500
Nov 19 12:11:11 cisco.mikrotik.com ocserv[47923]: worker[wolf]: 127.0.0.1 peer's link MTU is 1500
Nov 19 12:11:11 cisco.mikrotik.com ocserv[47923]: worker[wolf]: 127.0.0.1 sending IPv4 10.10.10.4
Nov 19 12:11:11 cisco.mikrotik.com ocserv[47923]: worker[wolf]: 127.0.0.1 adding DNS 8.8.8.8
Nov 19 12:11:11 cisco.mikrotik.com ocserv[47923]: worker[wolf]: 127.0.0.1 adding DNS 1.1.1.1
Nov 19 12:11:11 cisco.mikrotik.com ocserv[47923]: worker[wolf]: 127.0.0.1 Link MTU is 1500 bytes
Nov 19 12:11:11 cisco.mikrotik.com ocserv[47923]: worker[wolf]: 127.0.0.1 selected DTLS compression method oc-lz4
Nov 19 12:11:11 cisco.mikrotik.com ocserv[47923]: worker[wolf]: 127.0.0.1 selected CSTP compression method oc-lz4
Nov 19 12:11:21 cisco.mikrotik.com ocserv[32307]: main:127.0.0.1:38012 user disconnected (reason: unspecified, rx: 0, tx: 0)
Nov 19 12:26:15 cisco.mikrotik.com ocserv[32308]: radius-auth: closing session
Nov 19 12:26:21 cisco.mikrotik.com ocserv[32308]: radcli: rc_send_server_ctx: rc_send_server: no reply from RADIUS acct server "ip-server-ocserv":1813
Nov 19 12:26:21 cisco.mikrotik.com ocserv[32308]: radius-auth: radius_close_session: 1
Nov 19 12:26:21 cisco.mikrotik.com ocserv[32308]: radius-auth: closing session
Nov 19 12:26:27 cisco.mikrotik.com ocserv[32308]: radcli: rc_send_server_ctx: rc_send_server: no reply from RADIUS acct server "ip-server-ocserv":1813
Nov 19 12:26:27 cisco.mikrotik.com ocserv[32308]: radius-auth: radius_close_session: 1
Nov 19 12:26:27 cisco.mikrotik.com ocserv[32308]: radius-auth: closing session
Nov 19 12:26:33 cisco.mikrotik.com ocserv[32308]: radcli: rc_send_server_ctx: rc_send_server: no reply from RADIUS acct server "ip-server-ocserv":1813
Nov 19 12:26:33 cisco.mikrotik.com ocserv[32308]: radius-auth: radius_close_session: 1
Nov 19 12:59:37 cisco.mikrotik.com ocserv[32307]: main:127.0.0.1:38048 user disconnected (reason: unspecified, rx: 0, tx: 0)
Nov 19 13:00:21 cisco.mikrotik.com ocserv[32307]: main:127.0.0.1:38052 user disconnected (reason: unspecified, rx: 0, tx: 0)
Nov 19 13:01:59 cisco.mikrotik.com ocserv[32307]: main:127.0.0.1:38056 user disconnected (reason: unspecified, rx: 0, tx: 0)
lines 765-809/809 (END)

محتویات فایل کانفیگ ocserv هم مطابق زیر هست:

root@cisco:/etc/ocserv# cat ocserv.conf
# User authentication method. Could be set multiple times and in
# that case all should succeed. To enable multiple methods use
# multiple auth directives. Available options: certificate,
# plain, pam, radius, gssapi.
#
# Note that authentication methods cannot be changed with reload.

# certificate:
#  This indicates that all connecting users must present a certificate.
#
# pam[gid-min=1000]:
#  This enabled PAM authentication of the user. The gid-min option is used
# by auto-select-group option, in order to select the minimum valid group ID.
#
# plain[passwd=/etc/ocserv/ocpasswd,otp=/etc/ocserv/users.otp]
#  The plain option requires specifying a password file which contains
# entries of the following format.
# "username:groupname1,groupname2:encoded-password"
# One entry must be listed per line, and 'ocpasswd' should be used
# to generate password entries. The 'otp' suboption allows to specify
# an oath password file to be used for one time passwords; the format of
# the file is described in https://github.com/archiecobbs/mod-authn-otp/wiki/UsersFile
#
# radius[config=/etc/radiusclient/radiusclient.conf,groupconfig=true,nas-identifier=name]:
#  The radius option requires specifying freeradius-client configuration
# file. If the groupconfig option is set, then config-per-user/group will be overriden,
# and all configuration will be read from radius. That also includes the
# Acct-Interim-Interval, and Session-Timeout values.
#
# See doc/README-radius.md for the supported radius configuration atributes.
#
# gssapi[keytab=/etc/key.tab,require-local-user-map=true,tgt-freshness-time=900]
#  The gssapi option allows to use authentication methods supported by GSSAPI,
# such as Kerberos tickets with ocserv. It should be best used as an alternative
# to PAM (i.e., have pam in auth and gssapi in enable-auth), to allow users with
# tickets and without tickets to login. The default value for require-local-user-map
# is true. The 'tgt-freshness-time' if set, it would require the TGT tickets presented
# to have been issued within the provided number of seconds. That option is used to
# restrict logins even if the KDC provides long time TGT tickets.

#auth = "pam"
#auth = "pam[gid-min=1000]"
#auth = "plain[passwd=./sample.passwd,otp=./sample.otp]"
#auth = "plain[passwd=./sample.passwd]"
#auth = "plain[passwd=/etc/ocserv/ocpasswd]"
#auth = "certificate"
auth = "radius[config=/etc/radcli/radiusclient.conf,groupconfig=true]"
acct = "radius[config=/etc/radcli/radiusclient.conf,groupconfig=true]"

# Specify alternative authentication methods that are sufficient
# for authentication. That is, if set, any of the methods enabled
# will be sufficient to login.
#enable-auth = "certificate"
#enable-auth = "gssapi"
#enable-auth = "gssapi[keytab=/etc/key.tab,require-local-user-map=true,tgt-freshness-time=900]"

# Accounting methods available:
# radius: can be combined with any authentication method, it provides
#      radius accounting to available users (see also stats-report-time).
#
# pam: can be combined with any authentication method, it provides
#      a validation of the connecting user's name using PAM. It is
#      superfluous to use this method when authentication is already
#      PAM.
#
# Only one accounting method can be specified.
#acct = "radius[config=/etc/radiusclient/radiusclient.conf]"

# Use listen-host to limit to specific IPs or to the IPs of a provided
# hostname.
#listen-host = [IP|HOSTNAME]

# Use udp-listen-host to limit udp to specific IPs or to the IPs of a provided
# hostname. if not set, listen-host will be used
#udp-listen-host = [IP|HOSTNAME]

# When the server has a dynamic DNS address (that may change),
# should set that to true to ask the client to resolve again on
# reconnects.
#listen-host-is-dyndns = true

# TCP and UDP port number
# Note: These options are controlled by ocserv.socket if socket-activated
# version of systemd configuration is used
tcp-port = 9735
#udp-port = 443

# Accept connections using a socket file. It accepts HTTP
# connections (i.e., without SSL/TLS unlike its TCP counterpart),
# and uses it as the primary channel. That option cannot be
# combined with certificate authentication.
#listen-clear-file = /run/ocserv-conn.socket

# The user the worker processes will be run as. It should be
# unique (no other services run as this user).
run-as-user = nobody
run-as-group = daemon

# socket file used for IPC with occtl. You only need to set that,
# if you use more than a single servers.
#occtl-socket-file = /run/occtl.socket

# socket file used for server IPC (worker-main), will be appended with .PID
# It must be accessible within the chroot environment (if any), so it is best
# specified relatively to the chroot directory.
socket-file = /run/ocserv.socket

# The default server directory. Does not require any devices present.
#chroot-dir = /var/lib/ocserv

# The key and the certificates of the server
# The key may be a file, or any URL supported by GnuTLS (e.g.,
# tpmkey:uuid=xxxxxxx-xxxx-xxxx-xxxx-xxxxxxxx;storage=user
# or pkcs11:object=my-vpn-key;object-type=private)
#
# The server-cert file may contain a single certificate, or
# a sorted certificate chain.
#
# There may be multiple server-cert and server-key directives,
# but each key should correspond to the preceding certificate.
# The certificate files will be reloaded when changed allowing for in-place
# certificate renewal (they are checked and reloaded periodically;
# a SIGHUP signal to main server will force reload).

server-cert = /etc/ssl/certs/ssl-cert-ss500.pem
server-key = /etc/ssl/private/ssl-cert-ss500.key


server-cert = /etc/ssl/certs/ssl-cert-ss600.pem
server-key = /etc/ssl/private/ssl-cert-ss600.key


server-cert = /etc/ssl/certs/ssl-cert-snakeoil.pem
server-key = /etc/ssl/private/ssl-cert-snakeoil.key

# Diffie-Hellman parameters. Only needed if for old (pre 3.6.0
# versions of GnuTLS for supporting DHE ciphersuites.
# Can be generated using:
# certtool --generate-dh-params --outfile /etc/ocserv/dh.pem
#dh-params = /etc/ocserv/dh.pem

# In case PKCS #11, TPM or encrypted keys are used the PINs should be available
# in files. The srk-pin-file is applicable to TPM keys only, and is the
# storage root key.
#pin-file = /etc/ocserv/pin.txt
#srk-pin-file = /etc/ocserv/srkpin.txt

# The password or PIN needed to unlock the key in server-key file.
# Only needed if the file is encrypted or a PKCS #11 object. This
# is an alternative method to pin-file.
#key-pin = 1234

# The SRK PIN for TPM.
# This is an alternative method to srk-pin-file.
#srk-pin = 1234

# The Certificate Authority that will be used to verify
# client certificates (public keys) if certificate authentication
# is set.
ca-cert = /etc/ssl/certs/ssl-cert-snakeoil.pem


### All configuration options below this line are reloaded on a SIGHUP.
### The options above, will remain unchanged. Note however, that the
### server-cert, server-key, dh-params and ca-cert options will be reloaded
### if the provided file changes, on server reload. That allows certificate
### rotation, but requires the server key to remain the same for seamless
### operation. If the server key changes on reload, there may be connection
### failures during the reloading time.


# Whether to enable seccomp/Linux namespaces worker isolation. That restricts the number of
# system calls allowed to a worker process, in order to reduce damage from a
# bug in the worker process. It is available on Linux systems at a performance cost.
# The performance cost is roughly 2% overhead at transfer time (tested on a Linux 3.17.8).
# Note however, that process isolation is restricted to the specific libc versions
# the isolation was tested at. If you get random failures on worker processes, try
# disabling that option and report the failures you, along with system and debugging
# information at: https://gitlab.com/ocserv/ocserv/issues
isolate-workers = true

# A banner to be displayed on clients
#banner = "Welcome"

# Limit the number of clients. Unset or set to zero for unlimited.
#max-clients = 1024
max-clients = 0

# Limit the number of identical clients (i.e., users connecting
# multiple times). Unset or set to zero for unlimited.
max-same-clients = 2

# When the server receives connections from a proxy, like haproxy
# which supports the proxy protocol, set this to obtain the correct
# client addresses. The proxy protocol (v2) would then be expected in
# the TCP or UNIX socket (not the UDP one).
#listen-proxy-proto = true

# Limit the number of client connections to one every X milliseconds
# (X is the provided value). Set to zero for no limit.
#rate-limit-ms = 100

# Stats report time. The number of seconds after which each
# worker process will report its usage statistics (number of
# bytes transferred etc). This is useful when accounting like
# radius is in use.
#stats-report-time = 360

# Stats reset time. The period of time statistics kept by main/sec-mod
# processes will be reset. These are the statistics shown by cmd
# 'occtl show stats'. For daily: 86400, weekly: 604800
# This is unrelated to stats-report-time.
server-stats-reset-time = 604800

# Keepalive in seconds
keepalive = 1

# Dead peer detection in seconds.
# Note that when the client is behind a NAT this value
# needs to be short enough to prevent the NAT disassociating
# his UDP session from the port number. Otherwise the client
# could have his UDP connection stalled, for several minutes.
dpd = 8192

# Dead peer detection for mobile clients. That needs to
# be higher to prevent such clients being awaken too
# often by the DPD messages, and save battery.
# The mobile clients are distinguished from the header
# 'X-AnyConnect-Identifier-Platform'.
mobile-dpd = 8192

# If using DTLS, and no UDP traffic is received for this
# many seconds, attempt to send future traffic over the TCP
# connection instead, in an attempt to wake up the client
# in the case that there is a NAT and the UDP translation
# was deleted. If this is unset, do not attempt to use this
# recovery mechanism.
#switch-to-tcp-timeout = 25

# MTU discovery (DPD must be enabled)
try-mtu-discovery = true

# If you have a certificate from a CA that provides an OCSP
# service you may provide a fresh OCSP status response within
# the TLS handshake. That will prevent the client from connecting
# independently on the OCSP server.
# You can update this response periodically using:
# ocsptool --ask --load-cert=your_cert --load-issuer=your_ca --outfile response
# Make sure that you replace the following file in an atomic way.
#ocsp-response = /etc/ocserv/ocsp.der

# The object identifier that will be used to read the user ID in the client
# certificate. The object identifier should be part of the certificate's DN
# Useful OIDs are:
#  CN = 2.5.4.3, UID = 0.9.2342.19200300.100.1.1
cert-user-oid = 0.9.2342.19200300.100.1.1

# The object identifier that will be used to read the user group in the
# client certificate. The object identifier should be part of the certificate's
# DN. If the user may belong to multiple groups, then use multiple such fields
# in the certificate's DN. Useful OIDs are:
#  OU (organizational unit) = 2.5.4.11
#cert-group-oid = 2.5.4.11

# The revocation list of the certificates issued by the 'ca-cert' above.
# See the manual to generate an empty CRL initially. The CRL will be reloaded
# periodically when ocserv detects a change in the file. To force a reload use
# SIGHUP.
#crl = /etc/ocserv/crl.pem

# Uncomment this to enable compression negotiation (LZS, LZ4).
compression = true

# Set the minimum size under which a packet will not be compressed.
# That is to allow low-latency for VoIP packets. The default size
# is 256 bytes. Modify it if the clients typically use compression
# as well of VoIP with codecs that exceed the default value.
no-compress-limit = 256

# GnuTLS priority string; note that SSL 3.0 is disabled by default
# as there are no openconnect (and possibly anyconnect clients) using
# that protocol. The string below does not enforce perfect forward
# secrecy, in order to be compatible with legacy clients.
#
# Note that the most performant ciphersuites are the moment are the ones
# involving AES-GCM. These are very fast in x86 and x86-64 hardware, and
# in addition require no padding, thus taking full advantage of the MTU.
# For that to be taken advantage of, the openconnect client must be
# used, and the server must be compiled against GnuTLS 3.2.7 or later.
# Use "gnutls-cli --benchmark-tls-ciphers", to see the performance
# difference with AES_128_CBC_SHA1 (the default for anyconnect clients)
# in your system.

# More combinations in priority strings are available, check
# http://gnutls.org/manual/html_node/Priority-Strings.html
# E.g., the string below enforces perfect forward secrecy (PFS)
# on the main channel.
#tls-priorities = "NORMAL:%SERVER_PRECEDENCE:%COMPAT:-RSA:-VERS-SSL3.0:-ARCFOUR-128"
tls-priorities = "NORMAL:%SERVER_PRECEDENCE:%COMPAT:-RSA:-VERS-SSL3.0:-ARCFOUR-128:-VERS-TLS1.0:-VERS-TLS1.1"

# That option requires the established DTLS channel to use the same
# cipher as the primary TLS channel. This cannot be combined with
# listen-clear-file since the ciphersuite information is not available
# in that configuration. Note also, that this option implies that
# dtls-legacy option is false; this option cannot be enforced
# in the legacy/compat protocol.
#match-tls-dtls-ciphers = true

# The time (in seconds) that a client is allowed to stay connected prior
# to authentication
auth-timeout = 99999999999999

# The time (in seconds) that a client is allowed to stay idle (no traffic)
# before being disconnected. Unset to disable.
#idle-timeout = 1200

# The time (in seconds) that a mobile client is allowed to stay idle (no
# traffic) before being disconnected. Unset to disable.
#mobile-idle-timeout = 1800

# The time (in seconds) that a client is not allowed to reconnect after
# a failed authentication attempt.
min-reauth-time = 3000

# Banning clients in ocserv works with a point system. IP addresses
# that get a score over that configured number are banned for
# min-reauth-time seconds. By default a wrong password attempt is 10 points,
# a KKDCP POST is 1 point, and a connection is 1 point. Note that
# due to difference processes being involved the count of points
# will not be real-time precise.
#
# Score banning cannot be reliably used when receiving proxied connections
# locally from an HTTP server (i.e., when listen-clear-file is used).
#
# Set to zero to disable.
max-ban-score = 0

# The time (in seconds) that all score kept for a client is reset.
ban-reset-time = 3000

# In case you'd like to change the default points.
#ban-points-wrong-password = 10
#ban-points-connection = 1
#ban-points-kkdcp = 1

# Cookie timeout (in seconds)
# Once a client is authenticated he's provided a cookie with
# which he can reconnect. That cookie will be invalidated if not
# used within this timeout value. This cookie remains valid, during
# the user's connected time, and after user disconnection it
# remains active for this amount of time. That setting should allow a
# reasonable amount of time for roaming between different networks.
cookie-timeout = 3000

# If this is enabled (not recommended) the cookies will stay
# valid even after a user manually disconnects, and until they
# expire. This may improve roaming with some broken clients.
#persistent-cookies = true

# Whether roaming is allowed, i.e., if true a cookie is
# restricted to a single IP address and cannot be re-used
# from a different IP.
deny-roaming = false

# ReKey time (in seconds)
# ocserv will ask the client to refresh keys periodically once
# this amount of seconds is elapsed. Set to zero to disable (note
# that, some clients fail if rekey is disabled).
rekey-time = 172800

# ReKey method
# Valid options: ssl, new-tunnel
#  ssl: Will perform an efficient rehandshake on the channel allowing
#       a seamless connection during rekey.
#  new-tunnel: Will instruct the client to discard and re-establish the channel.
#       Use this option only if the connecting clients have issues with the ssl
#       option.
rekey-method = ssl

# Script to call when a client connects and obtains an IP.
# The following parameters are passed on the environment.
# REASON, USERNAME, GROUPNAME, DEVICE, IP_REAL (the real IP of the client),
# IP_REAL_LOCAL (the local interface IP the client connected), IP_LOCAL
# (the local IP in the P-t-P connection), IP_REMOTE (the VPN IP of the client),
# IPV6_LOCAL (the IPv6 local address if there are both IPv4 and IPv6
# assigned), IPV6_REMOTE (the IPv6 remote address), IPV6_PREFIX, and
# ID (a unique numeric ID); REASON may be "connect" or "disconnect".
# In addition the following variables OCSERV_ROUTES (the applied routes for this
# client), OCSERV_NO_ROUTES, OCSERV_DNS (the DNS servers for this client),
# will contain a space separated list of routes or DNS servers. A version
# of these variables with the 4 or 6 suffix will contain only the IPv4 or
# IPv6 values. The connect script must return zero as exit code, or the
# client connection will be refused.

# The disconnect script will receive the additional values: STATS_BYTES_IN,
# STATS_BYTES_OUT, STATS_DURATION that contain a 64-bit counter of the bytes
# output from the tun device, and the duration of the session in seconds.

#connect-script = /usr/bin/myscript
#disconnect-script = /usr/bin/myscript

# UTMP
# Register the connected clients to utmp. This will allow viewing
# the connected clients using the command 'who'.
#use-utmp = true

# Whether to enable support for the occtl tool (i.e., either through D-BUS,
# or via a unix socket).
use-occtl = true

# PID file. It can be overriden in the command line.
pid-file = /run/ocserv.pid

# Set the protocol-defined priority (SO_PRIORITY) for packets to
# be sent. That is a number from 0 to 6 with 0 being the lowest
# priority. Alternatively this can be used to set the IP Type-
# Of-Service, by setting it to a hexadecimal number (e.g., 0x20).
# This can be set per user/group or globally.
#net-priority = 3

# Set the VPN worker process into a specific cgroup. This is Linux
# specific and can be set per user/group or globally.
#cgroup = "cpuset,cpu:test"

#
# Network settings
#

# The name to use for the tun device
device = vpns

# Whether the generated IPs will be predictable, i.e., IP stays the
# same for the same user when possible.
predictable-ips = true

# The default domain to be advertised
default-domain = takdor.pw

# The pool of addresses that leases will be given from. If the leases
# are given via Radius, or via the explicit-ip? per-user config option then
# these network values should contain a network with at least a single
# address that will remain under the full control of ocserv (that is
# to be able to assign the local part of the tun device address).
# Note that, you could use addresses from a subnet of your LAN network if you
# enable proxy arp in the LAN interface (see http://ocserv.gitlab.io/www/recipes-ocserv-pseudo-bridge.html);
# in that case it is recommended to set ping-leases to true.
ipv4-network = 10.10.10.0
ipv4-netmask = 255.255.255.0

# An alternative way of specifying the network:
#ipv4-network = 192.168.1.0/24

# The IPv6 subnet that leases will be given from.
#ipv6-network = fda9:4efe:7e3b:03ea::/48

# Specify the size of the network to provide to clients. It is
# generally recommended to provide clients with a /64 network in
# IPv6, but any subnet may be specified. To provide clients only
# with a single IP use the prefix 128.
#ipv6-subnet-prefix = 128
#ipv6-subnet-prefix = 64

# Whether to tunnel all DNS queries via the VPN. This is the default
# when a default route is set.
tunnel-all-dns = true

# The advertized DNS server. Use multiple lines for
# multiple servers.
# dns = fc00::4be0
dns = 8.8.8.8
dns = 1.1.1.1

# The NBNS server (if any)
#nbns = 192.168.1.3

# The domains over which the provided DNS should be used. Use
# multiple lines for multiple domains.
#split-dns = example.com

# Prior to leasing any IP from the pool ping it to verify that
# it is not in use by another (unrelated to this server) host.
# Only set to true, if there can be occupied addresses in the
# IP range for leases.
ping-leases = false

# Use this option to set a link MTU value to the incoming
# connections. Unset to use the default MTU of the TUN device.
# Note that the MTU is negotiated using the value set and the
# value sent by the peer.
#mtu = 1420

# Unset to enable bandwidth restrictions (in bytes/sec). The
# setting here is global, but can also be set per user or per group.
#rx-data-per-sec = 40000
#tx-data-per-sec = 40000

# The number of packets (of MTU size) that are available in
# the output buffer. The default is low to improve latency.
# Setting it higher will improve throughput.
#output-buffer = 10

# Routes to be forwarded to the client. If you need the
# client to forward routes to the server, you may use the
# config-per-user/group or even connect and disconnect scripts.
#
# To set the server as the default gateway for the client just
# comment out all routes from the server, or use the special keyword
# 'default'.

#route = 10.0.0.0/8
#route = 172.16.0.0/12
#route = 192.168.0.0/16
#route = fd00::/8
#route = default

# Subsets of the routes above that will not be routed by
# the server.

#no-route = 192.168.5.0/255.255.255.0

# Note the that following two firewalling options currently are available
# in Linux systems with iptables software.

# If set, the script /usr/bin/ocserv-fw will be called to restrict
# the user to its allowed routes and prevent him from accessing
# any other routes. In case of defaultroute, the no-routes are restricted.
# All the routes applied by ocserv can be reverted using /usr/bin/ocserv-fw
# --removeall. This option can be set globally or in the per-user configuration.
#restrict-user-to-routes = true

# This option implies restrict-user-to-routes set to true. If set, the
# script /usr/bin/ocserv-fw will be called to restrict the user to
# access specific ports in the network. This option can be set globally
# or in the per-user configuration.
#restrict-user-to-ports = "tcp(443), tcp(80), udp(443), sctp(99), tcp(583), icmp(), icmpv6()"

# You could also use negation, i.e., block the user from accessing these ports only.
#restrict-user-to-ports = "!(tcp(443), tcp(80))"

# When set to true, all client's iroutes are made visible to all
# connecting clients except for the ones offering them. This option
# only makes sense if config-per-user is set.
#expose-iroutes = true

# Groups that a client is allowed to select from.
# A client may belong in multiple groups, and in certain use-cases
# it is needed to switch between them. For these cases the client can
# select prior to authentication. Add multiple entries for multiple groups.
# The group may be followed by a user-friendly name in brackets.
#select-group = group1
#select-group = group2[My special group]

# The name of the (virtual) group that if selected it would assign the user
# to its default group.
#default-select-group = DEFAULT

# Instead of specifying manually all the allowed groups, you may instruct
# ocserv to scan all available groups and include the full list.
#auto-select-group = true

# Configuration files that will be applied per user connection or
# per group. Each file name on these directories must match the username
# or the groupname.
# The options allowed in the configuration files are dns, nbns,
#  ipv?-network, ipv4-netmask, rx/tx-per-sec, iroute, route, no-route,
#  explicit-ipv4, explicit-ipv6, net-priority, deny-roaming, no-udp,
#  keepalive, dpd, mobile-dpd, max-same-clients, tunnel-all-dns,
#  restrict-user-to-routes, user-profile, cgroup, stats-report-time,
#  mtu, idle-timeout, mobile-idle-timeout, restrict-user-to-ports,
#  split-dns and session-timeout.
#
# Note that the 'iroute' option allows to add routes on the server
# based on a user or group. The syntax depends on the input accepted
# by the commands route-add-cmd and route-del-cmd (see below). The no-udp
# is a boolean option (e.g., no-udp = true), and will prevent a UDP session
# for that specific user or group. The hostname option will set a
# hostname to override any proposed by the user. Note also, that, any
# routes, no-routes, DNS or NBNS servers present will overwrite the global ones.

#config-per-user = /etc/ocserv/config-per-user/
#config-per-group = /etc/ocserv/config-per-group/

# When config-per-xxx is specified and there is no group or user that
# matches, then utilize the following configuration.
#default-user-config = /etc/ocserv/defaults/user.conf
#default-group-config = /etc/ocserv/defaults/group.conf

# The system command to use to setup a route. %{R} will be replaced with the
# route/mask, %{RI} with the route in CIDR format, and %{D} with the (tun) device.
#
# The following example is from linux systems. %{R} should be something
# like 192.168.2.0/255.255.255.0 and %{RI} 192.168.2.0/24 (the argument of iroute).

#route-add-cmd = "ip route add %{R} dev %{D}"
#route-del-cmd = "ip route delete %{R} dev %{D}"

# This option allows to forward a proxy. The special keywords '%{U}'
# and '%{G}', if present will be replaced by the username and group name.
#proxy-url = http://example.com/
#proxy-url = http://example.com/%{U}/

# This option allows you to specify a URL location where a client can
# post using MS-KKDCP, and the message will be forwarded to the provided
# KDC server. That is a translation URL between HTTP and Kerberos.
# In MIT kerberos you'll need to add in realms:
#   EXAMPLE.COM = {
#     kdc = https://ocserv.example.com/KdcProxy
#     http_anchors = FILE:/etc/ocserv-ca.pem
#   }
# In some distributions the krb5-k5tls plugin of kinit is required.
#
# The following option is available in ocserv, when compiled with GSSAPI support.

#kkdcp = "SERVER-PATH KERBEROS-REALM PROTOCOL@SERVER:PORT"
#kkdcp = "/KdcProxy KERBEROS.REALM udp@127.0.0.1:88"
#kkdcp = "/KdcProxy KERBEROS.REALM tcp@127.0.0.1:88"
#kkdcp = "/KdcProxy KERBEROS.REALM tcp@[::1]:88"

#
# The following options are for (experimental) AnyConnect client
# compatibility.

# This option will enable the pre-draft-DTLS version of DTLS, and
# will not require clients to present their certificate on every TLS
# connection. It must be set to true to support legacy CISCO clients
# and openconnect clients < 7.08. When set to true, it implies dtls-legacy = true.
cisco-client-compat = false

# This option allows to disable the DTLS-PSK negotiation (enabled by default).
# The DTLS-PSK negotiation was introduced in ocserv 0.11.5 to deprecate
# the pre-draft-DTLS negotiation inherited from AnyConnect. It allows the
# DTLS channel to negotiate its ciphers and the DTLS protocol version.
#dtls-psk = false

# This option allows to disable the legacy DTLS negotiation (enabled by default,
# but that may change in the future).
# The legacy DTLS uses a pre-draft version of the DTLS protocol and was
# from AnyConnect protocol. It has several limitations, that are addressed
# by the dtls-psk protocol supported by openconnect 7.08+.
dtls-legacy = false

# Client profile xml. A sample file exists in doc/profile.xml.
# It is required by some of the CISCO clients.
# This file must be accessible from inside the worker's chroot.
# Note that enabling this option is not recommended as it will allow
# the worker processes to open arbitrary files (when isolate-workers is
# set to true).
#user-profile = /path/to/file.xml

#Advanced options

# Option to allow sending arbitrary custom headers to the client after
# authentication and prior to VPN tunnel establishment. You shouldn't
# need to use this option normally; if you do and you think that
# this may help others, please send your settings and reason to
# the openconnect mailing list. The special keywords '%{U}'
# and '%{G}', if present will be replaced by the username and group name.
#custom-header = "X-My-Header: hi there"

# An example virtual host with different authentication methods serviced
# # by this server.
#
# [vhost:www.example.com]
# auth = "certificate"
#
# ca-cert = ../tests/certs/ca.pem
#
# # The certificate set here must include a 'dns_name' corresponding to
# # the virtual host name.
#
# server-cert = ../tests/certs/server-cert-secp521r1.pem
# server-key = ../tests/certs/server-key-secp521r1.pem
#
# ipv4-network = 192.168.2.0
# ipv4-netmask = 255.255.255.0
#
# cert-user-oid = 0.9.2342.19200300.100.1.1

الان مشکل شما یکی دو تا نیست که ! شما مقدار keepalive رو ست کردید روی یک ثانیه ! و انتظار دارید بلافاصله بعد اتصال قطع نشه ارتباط ؟ به زمان خط ۱۱ تا ۱۹ ام لاگ بالا خوب نگاه کنید ببینید متوجه میشید که درست یک ثانیه گذشته از زمان لاگین !

از طرفی ، مقدار dpd و mobile-dpd تون حدود ۲ ساعت و نیم هست که کاملا مناسبه و مشکلی نداره. یعنی بعد از این بازه زمانی (یا بعبارتی بعد از ارسال آخرین پکت) چه ویندوز چه اندروید و چه سایر سیستم عامل ها اگه پکتی به سمت VPN Server ارسال نکنن VPN Server میاد session رو بر اساس تنظیماتی که روش انجام شده یا قطعش می کنه یا در حالت idle قرار میده تا زمانی که پکتی به سمتش ارسال بشه. حالا اینکه گوشی بعد لاک اسکرین شدن پکت ارسال نمی کنه ربطی به VPN Server نداره بلکه ربطش به تنظیمات کارت شبکه و TCP/IP stack و تنظیمات جانبی سیستم عامل داره. در مورد ویندوز و بقیه OS ها هم صدق می کنه. 

سلام ، از چه VPN Client ای برای اتصال به VPN Server استفاده می کنید ؟

radcli ای که پیکربندی کردید TLS ای هست یا بدون TLS ؟

تو فایل پیکربندی تنظیمات RADIUS Client (همون radcli) ببینید محدودیت اتصالی چیزی تعریف نشده ؟ مثل  timeout ، IP whitelist و ...

تنظیمات سمت میکروتیک رو هم چک کنید. یوزر ها پروتکل های احرازهویت شون باید با چیزی که توی پروفایل RADIUS Server برای یوزر ها تعریف شده همخوانی داشته باشه.

ممنون حالا من یه سری موارد رو برسی کردم و دیدم قطعی به احراز هویت ارتباط داره طبق لاگ ها

این لاگ ها باعث میشه که ادرس سرور از دسترسس خارج بشه و نمیدونم چطور باید رفع بشه

فقط توی لاگ ها که چک میکردم هر وقت این لاگ ها میافته کلا یوزرها دیگه نمیتونن متصل بشن که بعد باید دستری ocserv رو ریست کرد

ایا در مورد این لاگ ها اطلاعی دارید ؟

(توی فایل کانفیگ دستورات ssl رو هم طبق اون پست بالا تغییر دادم اما همچنان این لاگ رو داریم)

Nov 21 14:40:34 cisco.mikrotik.com ocserv[935604]: common/common.c:653: recvmsg: Connection timed out
Nov 21 14:40:34 cisco.mikrotik.com ocserv[935604]: error receiving sec-mod reply: Connection timed out
Nov 21 14:40:34 cisco.mikrotik.com ocserv[935604]: GnuTLS error (at worker-vpn.c:795): GnuTLS internal error.

تو فایل etc/ocserv/ocserv.conf/ خط زیر رو comment کنید :

tls-priorities = "NORMAL:%SERVER_PRECEDENCE:%COMPAT:-RSA:-VERS-SSL3.0:-ARCFOUR-128:-VERS-TLS1.0:-VERS-TLS1.1"

و خط زیر رو ...

#tls-priorities = "NORMAL:%SERVER_PRECEDENCE:%COMPAT:-RSA:-VERS-SSL3.0:-ARCFOUR-128"

اینجوری بنویسید :

tls-priorities = "NORMAL:%SERVER_PRECEDENCE:%COMPAT:-VERS-SSL3.0"

لازم به ذکر هست در هر دو برنامه سمت کلاینت هم open connect و هم any connect تست کردم و شرایط یکسان هست

---

من تست کردمو مقدار radius_timeout رو که پیش فرض 10 بود افزایش دادم به 30 حتی ولی درنهایت ارور زیر میاد بازم(این ارورهرزگاهی میاد )

radcli: rc_send_server_ctx: rc_send_server: no reply from RADIUS acct server 1.1.1.1:1813

اگر مقدار radius_retries رو روی کامند کنیم کلا ocserv  از کار میافته و قطع میشه  و خطای زیر رو مینداره درstatus

config option radius_retries was not set

باید حتما یک مقدار داشته باشه تا ocserv فعال باشه ظاهرا.

---------------------

در داخل یوزرمنیجر میکروتیک هم بخش یوزر گروپ از گروه دیفالت استفاده کردم برای سوزر ها که تمامی ایتم های autsh تیکشون فعال هست - وهیچattributes هم استفاده نکردم