Hi I am using freeradius version 2.1.4 and I want to set up config to eap TTLS using users and clients file but didnt work.Please help me.Thanks. ***************OUTPUT************************************Finished request 18.Going to the next requestWaking up in 2.0 seconds.Cleaning up request 17 ID 18 with timestamp +75Waking up in 2.9 seconds.rad_recv: Access-Request packet from host 10.1.1.252 port 1206, id=20, length=183 User-Name = "deneme" NAS-IP-Address = 10.1.1.252 NAS-Port = 0 Called-Station-Id = "00-30-4F-44-3D-C1" Calling-Station-Id = "00-18-DE-88-62-77" NAS-Identifier = "WirelessAccessPoint" Framed-MTU = 1380 NAS-Port-Type = Wireless-802.11 EAP-Message = 0x0211002219001703010017a5491ed47f0de82246939132f8766cf3c1a85f8c211be5 State = 0x56c2eb4850d3f233efbb27b16d1adb57 Message-Authenticator = 0x1ea576935b901d2c1f156615504ed0da+- entering group authorize {...}++[preprocess] returns ok++[chap] returns noop++[mschap] returns noop[suffix] No '@' in User-Name = "deneme", looking up realm NULL[suffix] No such realm "NULL"++[suffix] returns noop[eap] EAP packet type response id 17 length 34[eap] Continuing tunnel setu! p.++[eap] returns okFound Auth-Type = EAP+- entering group authenticate {...}[eap] Request found, released from the list[eap] EAP/peap[eap] processing type peap[peap] processing EAP-TLS[peap] eaptls_verify returned 7 [peap] Done initial handshake[peap] eaptls_process returned 7 [peap] EAPTLS_OK[peap] Session established. Decoding tunneled attributes.[peap] Identity - deneme[peap] Got tunneled request EAP-Message = 0x0211000b0164656e656d65server { PEAP: Got tunneled identity of deneme PEAP: Setting default EAP type for tunneled EAP session. PEAP: Setting User-Name to denemeSending tunneled request EAP-Message = 0x0211000b0164656e656d65 FreeRADIUS-Proxied-To = 127.0.0.1 User-Name = "deneme"server inner-tunnel {No authenticate method (Auth-Type) configuration found for the request: Rejecting the userFailed to authenticate the user.} # server inner-tunnel[peap] Got tunneled reply code 3[peap] Got tunneled reply RADIUS code 3[peap] Tunneled authentication was rejected.[peap! ] FAILURE++[eap] returns handledSending Access-Challenge of id 20 to 1 0.1.1.252 port 1206 EAP-Message = 0x011200261900170301001b3f825aee84e1fd23b0089c976f25f2f4054e5c93627e072882688f Message-Authenticator = 0x00000000000000000000000000000000 State = 0x56c2eb4851d0f233efbb27b16d1adb57Finished request 19.Going to the next requestWaking up in 1.9 seconds.Cleaning up request 18 ID 19 with timestamp +78Waking up in 2.9 seconds.rad_recv: Access-Request packet from host 10.1.1.252 port 1206, id=21, length=187 User-Name = "deneme" NAS-IP-Address = 10.1.1.252 NAS-Port = 0 Called-Station-Id = "00-30-4F-44-3D-C1" Calling-Station-Id = "00-18-DE-88-62-77" NAS-Identifier = "WirelessAccessPoint" Framed-MTU = 1380 NAS-Port-Type = Wireless-802.11 EAP-Message = 0x021200261900170301001bd0f786fe5ec27d325f117cb1c6314a2fc09664e18d31038aaa2a5f State = 0x56c2eb4851d0f233efbb27b16d1adb57 Message-Authenticator = 0xe4dd7f51a3fd9548338084267728d316+- entering group authorize {...}++[preprocess] returns ok++[chap] returns noop++[mschap] returns noop[suffix] No '@' in User! -Name = "deneme", looking up realm NULL[suffix] No such realm "NULL"++[suffix] returns noop[eap] EAP packet type response id 18 length 38[eap] Continuing tunnel setup.++[eap] returns okFound Auth-Type = EAP+- entering group authenticate {...}[eap] Request found, released from the list[eap] EAP/peap[eap] processing type peap[peap] processing EAP-TLS[peap] eaptls_verify returned 7 [peap] Done initial handshake[peap] eaptls_process returned 7 [peap] EAPTLS_OK[peap] Session established. Decoding tunneled attributes.[peap] Received EAP-TLV response.[peap] Had sent TLV failure. User was rejected earlier in this session.[eap] Handler failed in EAP/peap[eap] Failed in EAP select++[eap] returns invalidFailed to authenticate the user.Using Post-Auth-Type Reject+- entering group REJECT {...}[attr_filter.access_reject] expand: %{User-Name} -> deneme attr_filter: Matched entry DEFAULT at line 11++[attr_filter.access_reject] returns updatedDelaying reject of request 20 for 1 secondsG! oing to the next requestWaking up in 0.9 seconds.Sending delayed rejec t for request 20Sending Access-Reject of id 21 to 10.1.1.252 port 1206 EAP-Message = 0x04120004 Message-Authenticator = 0x00000000000000000000000000000000Waking up in 0.9 seconds.Cleaning up request 19 ID 20 with timestamp +81Waking up in 3.9 seconds. ************EAP.conf********************# -*- text -*-#### eap.conf -- Configuration for EAP types (PEAP, TTLS, etc.)#### $Id$ ######################################################################## eap { # default_eap_type = ttls # A list is maintained to correlate EAP-Response # packets with EAP-Request packets. After a # configurable length of time, entries in the list # expire, and are deleted. # timer_expire = 60 ignore_unknown_eap_types = no # Cisco AP1230B firmware 12.2(13)JA1 has a bug. When given # a User-Name attribute in an Access-Accept, it copies one # more byte than it should. # # We can work around it by configurably adding an extra # zero byte. cisco_accounting_username_bug = no # # Help prevent DoS attacks by limiting the number of # sessions that the server is tracking. Most systems # can handle ~30 EAP sessions/s, so the default limit # of 2048 is more than enough. max_sessions = 2048 # Supported EAP-types # # We do NOT recommend using EAP-MD5 authentication # for wireless connections. It is insecure, and does # not provide for dynamic WEP keys. # md5 { } # Cisco LEAP # leap { } # Generic Token Card. gtc { # The default challenge, which many clients # ignore.. #challenge = "Password: " auth_type = PAP } ## EAP-TLS # # See raddb/certs/README for additional comments # on certificates. # http://www.dslreports.com/forum/remark,9286052~mode=flat # tls { # # These is used to simplify later configurations. # certdir = ${confdir}/certs cadir = ${confdir}/certs private_key_password = 123456 private_key_file = ${certdir}/server.pem certificate_file = ${certdir}/server.pem CA_file = ${cadir}/ca.pem dh_file = ${certdir}/dh random_file = ${certdir}/random # fragment_size = 1024 # include_length = yes # check_crl = yes # # check_cert_issuer = "/C=GB/ST=Berkshire/L=Newbury/O=My Company Ltd" # check_cert_cn = %{User-Name} # cipher_list = "DEFAULT" # make_cert_command = "${certdir}/bootstrap" cache { # # Enable it. The default is "no". # Deleting the entire "cache" subsection # Also disables caching. # # You can disallow resumption for a # particular user by adding the following # attribute to the control item list: # # Allow-Session-Resumption = No # # If "enable = no" below, you CANNOT # enable resumption for just one user # by setting the above attribute to "yes". # enable = no # # Lifetime of the cached entries, in hours. # The sessions will be deleted after this # time. # lifetime = 24 # hours # # The maximum number of entries in the # cache. Set to "0" for "infinite". # # This could be set to the number of users # who are logged in... which can be a LOT. # max_entries = 255 } } ttls { # The tunneled EAP session needs a default # EAP type which is separate from the one for # the non-tunneled EAP module. Inside of the # TTLS tunnel, we recommend using EAP-MD5. # If the request does not contain an EAP # conversation, then this configuration entry # is ignored. default_eap_type = md5 # allowed values: {no, yes} copy_request_to_tunnel = no # allowed values: {no, yes} use_tunneled_reply = no virtual_server = "inner-tunnel" } peap { # The tunneled EAP session needs a default # EAP type which is separate from the one for # the non-tunneled EAP module. Inside of the # PEAP tunnel, we recommend using MS-CHAPv2, # as that is the default type supported by # Windows clients. default_eap_type = mschapv2 # the PEAP module also has these configuration # items, which are the same as for TTLS. copy_request_to_tunnel = no use_tunneled_reply = no # When the tunneled session is proxied, the # home server may not understand EAP-MSCHAP-V2. # Set this entry to "no" to proxy the tunneled # EAP-MSCHAP-V2 as normal MSCHAPv2. # proxy_tunneled_request_as_eap = yes virtual_server = "inner-tunnel" } mschapv2 { } } ***************** inner-tunnel ***********# -*- text -*-######################################################################## This is a virtual server that handles *only* inner tunnel# requests for EAP-TTLS and PEAP types.## $Id$####################################################################### server inner-tunnel {authorize { suffix unix update control { Proxy-To-Realm := LOCAL } eap { ok = return } files pap chap mschap# IPASS # ntdomain # See "Authorization Queries" in sql.conf# sql # # If you are using /etc/smbpasswd, and are also doing # mschap authentication, the un-comment this line, and # configure the 'etc_smbpasswd' module, above.# etc_smbpasswd # # The ldap module will set Auth-Type to LDAP if it has not # already been set# ldap # # Enforce daily limits on time spent logged in.# daily # # Use the checkval module# checkval expiration logintime} # Authentication.authenticate { # # PAP authentication, when a back-end database listed # in the 'authorize' section supplies a password. The # password can be clear-text, or encrypted. Auth-Type PAP { pap } # # Most people want CHAP authentication # A back-end database listed in the 'authorize' section # MUST supply a CLEAR TEXT password. Encrypted passwords # won't work. Auth-Type CHAP { chap } # # MSCHAP authentication. Auth-Type MS-CHAP { mschap } # # Pluggable Authentication Modules.# pam # # See 'man getpwent' for information on how the 'unix' # module checks the users password. Note that packets # containing CHAP-Password attributes CANNOT be authenticated # against /etc/passwd! See the FAQ for details. # #unix # Uncomment it if you want to use ldap for authentication # # Note that this means "check plain-text password against # the ldap database", which means that EAP won't work, # as it does not supply a plain-text password.# Auth-Type LDAP {# ldap# } # # Allow EAP authentication. eap} ######################################################################## There are no accounting requests inside of EAP-TTLS or PEAP# tunnels.####################################################################### # Session database, used for checking Simultaneous-Use. Either the radutmp # or rlm_sql module can handle this.# The rlm_sql module is *much* fastersession { radutmp # # See "Simultaneous Use Checking Queries" in sql.conf# sql} # Post-Authentication# Once we KNOW that the user has been authenticated, there are# additional steps we can take.post-auth { # Note that we do NOT assign IP addresses here. # If you try to assign IP addresses for EAP authentication types, # it WILL NOT WORK. You MUST use DHCP. # # If you want to have a log of authentication replies, # un-comment the following line, and the 'detail reply_log' # section, above. reply_log # # After authenticating the user, do another SQL query. # # See "Authentication Logging Queries" in sql.conf# sql # # Instead of sending the query to the SQL server, # write it into a log file. ## sql_log # # Un-comment the following if you have set # 'edir_account_policy_check = yes' in the ldap module sub-section of # the 'modules' section. ## ldap # # Access-Reject packets are sent through the REJECT sub-section of the # post-auth section. # # Add the ldap module name (or instance) if you have set # 'edir_account_policy_check = yes' in the ldap module configuration # Post-Auth-Type REJECT { attr_filter.access_reject } } ## When the server decides to proxy a request to a home server,# the proxied request is first passed through the pre-proxy# stage. This stage can re-write the request, or decide to# cancel the proxy.## Only a few modules currently have this method.#pre-proxy {# attr_rewrite # Uncomment the following line if you want to change attributes # as defined in the preproxy_users file.# files # Uncomment the following line if you want to filter requests # sent to remote servers based on the rules defined in the # 'attrs.pre-proxy' file.# attr_filter.pre-proxy # If you want to have a log of packets proxied to a home # server, un-comment the following line, and the # 'detail pre_proxy_log' section, above. pre_proxy_log} ## When the server receives a reply to a request it proxied# to a home server, the request may be massaged here, in the# post-proxy stage.#post-proxy { # If you want to have a log of replies from a home server, # un-comment the following line, and the 'detail post_proxy_log' # section, above. post_proxy_log # attr_rewrite # Uncomment the following line if you want to filter replies from # remote proxies based on the rules defined in the 'attrs' file.# attr_filter.post-proxy # # If you are proxying LEAP, you MUST configure the EAP # module, and you MUST list it here, in the post-proxy # stage. # # You MUST also use the 'nostrip' option in the 'realm' # configuration. Otherwise, the User-Name attribute # in the proxied request will not match the user name # hidden inside of the EAP packet, and the end server will # reject the EAP request. # eap ## Post-Proxy-Type Fail {# detail# } } } # inner-tunnel server block _________________________________________________________________ Windows Live Hotmail: Arkadaşlarınız Facebook'taki güncellemelerinizi doğrudan Hotmail®'den alır. http://www.microsoft.com/windows/windowslive/see-it-in-action/social-network...
Aziz YÜCELEN wrote:
I am using freeradius version 2.1.4 and I want to set up config to eap TTLS using users and clients file but didnt work.Please help me.Thanks.
The FAQ says to post the debug output, *not* a heavily edited version. The FAQ does *not* say to post the configuration. Follow the instructions on http://deployingradius.com/. TTLS *will* work. Alan DeKok.
Hi Sorry for my carelessness. Debug output is here and I am using eap TTLS but login not success.Please help me thanks. rad_recv: Access-Request packet from host 10.1.1.252 port 1206, id=20, length=183 User-Name = "deneme" NAS-IP-Address = 10.1.1.252 NAS-Port = 0 Called-Station-Id = "00-30-4F-44-3D-C1" Calling-Station-Id = "00-18-DE-88-62-77" NAS-Identifier = "WirelessAccessPoint" Framed-MTU = 1380 NAS-Port-Type = Wireless-802.11 EAP-Message = 0x0211002219001703010017a5491ed47f0de82246939132f8766cf3c1a85f8c211be5 State = 0x56c2eb4850d3f233efbb27b16d1adb57 Message-Authenticator = 0x1ea576935b901d2c1f156615504ed0da+- entering group authorize {...}++[preprocess] returns ok++[chap] returns noop++[mschap] returns noop[suffix] No '@' in User-Name = "deneme", looking up realm NULL[suffix] No such realm "NULL"++[suffix] returns noop[eap] EAP packet type response id 17 length 34[eap] Continuing tunnel setup.++[eap] returns okFound Auth-Type = EAP+- entering group authenticate {...}[eap] Request found, released from the list[eap] EAP/peap[eap] processing type peap[peap] processing EAP-TLS[peap] eaptls_! verify returned 7 [peap] Done initial handshake[peap] eaptls_process returned 7 [peap] EAPTLS_OK[peap] Session established. Decoding tunneled attributes.[peap] Identity - deneme[peap] Got tunneled request EAP-Message = 0x0211000b0164656e656d65server { PEAP: Got tunneled identity of deneme PEAP: Setting default EAP type for tunneled EAP session. PEAP: Setting User-Name to denemeSending tunneled request EAP-Message = 0x0211000b0164656e656d65 FreeRADIUS-Proxied-To = 127.0.0.1 User-Name = "deneme"server inner-tunnel {No authenticate method (Auth-Type) configuration found for the request: Rejecting the userFailed to authenticate the user.} # server inner-tunnel[peap] Got tunneled reply code 3[peap] Got tunneled reply RADIUS code 3[peap] Tunneled authentication was rejected.[peap] FAILURE++[eap] returns handledSending Access-Challenge of id 20 to 10.1.1.252 port 1206 EAP-Message = 0x011200261900170301001b3f825aee84e1fd23b0089c976f25f2f4054e5c93627e072882688f Message-Authenti! cator = 0x00000000000000000000000000000000 State = 0x56c2eb4851d0f233e fbb27b16d1adb57Finished request 19.Going to the next requestWaking up in 1.9 seconds.Cleaning up request 18 ID 19 with timestamp +78Waking up in 2.9 seconds.rad_recv: Access-Request packet from host 10.1.1.252 port 1206, id=21, length=187 User-Name = "deneme" NAS-IP-Address = 10.1.1.252 NAS-Port = 0 Called-Station-Id = "00-30-4F-44-3D-C1" Calling-Station-Id = "00-18-DE-88-62-77" NAS-Identifier = "WirelessAccessPoint" Framed-MTU = 1380 NAS-Port-Type = Wireless-802.11 EAP-Message = 0x021200261900170301001bd0f786fe5ec27d325f117cb1c6314a2fc09664e18d31038aaa2a5f State = 0x56c2eb4851d0f233efbb27b16d1adb57 Message-Authenticator = 0xe4dd7f51a3fd9548338084267728d316+- entering group authorize {...}++[preprocess] returns ok++[chap] returns noop++[mschap] returns noop[suffix] No '@' in User-Name = "deneme", looking up realm NULL[suffix] No such realm "NULL"++[suffix] returns noop[eap] EAP packet type response id 18 length 38[eap] Continuing tunnel setup.++[eap] returns okFound Auth-Typ! e = EAP+- entering group authenticate {...}[eap] Request found, released from the list[eap] EAP/peap[eap] processing type peap[peap] processing EAP-TLS[peap] eaptls_verify returned 7 [peap] Done initial handshake[peap] eaptls_process returned 7 [peap] EAPTLS_OK[peap] Session established. Decoding tunneled attributes.[peap] Received EAP-TLV response.[peap] Had sent TLV failure. User was rejected earlier in this session.[eap] Handler failed in EAP/peap[eap] Failed in EAP select++[eap] returns invalidFailed to authenticate the user.Using Post-Auth-Type Reject+- entering group REJECT {...}[attr_filter.access_reject] expand: %{User-Name} -> deneme attr_filter: Matched entry DEFAULT at line 11++[attr_filter.access_reject] returns updatedDelaying reject of request 20 for 1 secondsGoing to the next requestWaking up in 0.9 seconds.Sending delayed reject for request 20Sending Access-Reject of id 21 to 10.1.1.252 port 1206 EAP-Message = 0x04120004 Message-Authenticator = 0x0000000! 0000000000000000000000000Waking up in 0.9 seconds.Cleaning up request 19 ID 20 with timestamp +81 _________________________________________________________________ Windows Live: Arkadaşlarınız size e-posta gönderdiklerinde Flickr, Twitter ve Digg'deki hareketlerinizi görürler. http://www.microsoft.com/windows/windowslive/see-it-in-action/social-network...
Aziz YÜCELEN wrote:
Hi
Sorry for my carelessness. Debug output is here and I am using eap TTLS but login not success.Please help me thanks. ... server inner-tunnel { No authenticate method (Auth-Type) configuration found for the request: Rejecting the user Failed to authenticate the user. } # server inner-tunnel
You have edited the default configuration and broken it. Don't do that. You need the "inner-tunnel" virtual server for TTLS to work. Alan DeKok.
server inner-tunnel { No authenticate method (Auth-Type) configuration found for the request: Rejecting the user Failed to authenticate the user. } # server inner-tunnel
You have edited the default configuration and broken it. Don't do that.
You need the "inner-tunnel" virtual server for TTLS to work.
I am setup freeradius again and not edit default configuration, I am trying configure inner-tunnel but result didn't change. How to configure inner-tunnel file for ttls thanks. _________________________________________________________________ Yeni Windows 7: Size en uygun bilgisayarı bulun. Daha fazla bilgi edinin. http://windows.microsoft.com/shop
Aziz YÜCELEN wrote:
I am setup freeradius again and not edit default configuration, I am trying configure inner-tunnel but result didn't change. How to configure inner-tunnel file for ttls thanks.
You don't configure it. The default installation of the server configures it. The debug log shows that it's loading and using the inner-tunnel virtual server. It also shows that the inner-tunnel virtual server is *empty*. The *only* way for it to be empty is if you deleted the contents. Alan DeKok.
Aziz YÜCELEN wrote:
I am setup freeradius again and not edit default configuration, I am trying configure inner-tunnel but result didn't change. How to configure inner-tunnel file for ttls thanks.
You don't configure it. The default installation of the server configures it.
The debug log shows that it's loading and using the inner-tunnel virtual server. It also shows that the inner-tunnel virtual server is *empty*.
The *only* way for it to be empty is if you deleted the contents.
Hi I am setup again and dont configure defaullts.Run radiusd -X and receive user reject, output is below. Thanks for all. Waking up in 3.4 seconds. rad_recv: Access-Request packet from host 10.1.1.252 port 1206, id=228, length=229 User-Name = "deneme" NAS-IP-Address = 10.1.1.252 NAS-Port = 0 Called-Station-Id = "00-30-4F-44-3D-C1" Calling-Station-Id = "00-18-DE-88-62-77" NAS-Identifier = "WirelessAccessPoint" Framed-MTU = 1380 NAS-Port-Type = Wireless-802.11 EAP-Message = 0x020c005019800000004616030100410100003d03014c3589c63051541afb7d63785038b2b416e66676504baf594c8d48c83b74954500001600040005000a000900640062000300060013001200630100 State = 0xeccff048edc3e9d4d10018a42bd2d5e3 Message-Authenticator = 0x243675fbd3453868f365dda2997fab4f +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "deneme", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 12 length 80 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS TLS Length 70 [peap] Length Included [peap] eaptls_verify returned 11 [peap] (other): before/accept initialization [peap] TLS_accept: before/accept initialization [peap] <<< TLS 1.0 Handshake [length 0041], ClientHello [peap] TLS_accept: SSLv3 read client hello A [peap] >>> TLS 1.0 Handshake [length 002a], ServerHello [peap] TLS_accept: SSLv3 write server hello A [peap] >>> TLS 1.0 Handshake [length 0945], Certificate [peap] TLS_accept: SSLv3 write certificate A [peap] >>> TLS 1.0 Handshake [length 0004], ServerHelloDone [peap] TLS_accept: SSLv3 write server done A [peap] TLS_accept: SSLv3 flush data [peap] TLS_accept: Need to read more data: SSLv3 read client certificate A In SSL Handshake Phase In SSL Accept mode [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] returns handled Sending Access-Challenge of id 228 to 10.1.1.252 port 1206 EAP-Message = 0x010d040019c000000982160301002a0200002603014c35dfc4d9740a73263b408e02b48d53e6b878dbcb3e572e71e8eb29269972fd0000040016030109450b00094100093e0003fe308203fa308202e2a003020102020101300d06092a864886f70d01010405003081c2310b3009060355040613025452311330110603550408130a446979617262616b697231193017060355040713104469636c6520556e69766572736974793121301f060355040a1318417a697a20595543454c454e2042696c67692049736c656d311f301d06092a864886f70d010901161061797563656c656e406d736e2e636f6d313f303d06035504031436617a697a5f7975 EAP-Message = 0x63656c656e20556e6976657273697479206f66204469636c652043657274696669636174655f417574686f72697479301e170d3130303631363139333834355a170d3133303631353139333834355a3081a4310b3009060355040613025452311330110603550408130a446979617262616b69723121301f060355040a1318417a697a20595543454c454e2042696c67692049736c656d313c303a06035504031433417a697a5f597563656c656e20556e6976657273697479206f66204469636c6520536572766572204365727469666963617465311f301d06092a864886f70d010901161061797563656c656e406d736e2e636f6d30820122300d06 EAP-Message = 0x092a864886f70d01010105000382010f003082010a0282010100c63199d29c527300be3f6ec9f11d5aaf01239eaeb9ad9226307110ab54d8c705b9a8e43c3ef7c2dfcef7a2d27cc1a0a4022e6ca2af557ae7607e164460829c9683d0ff8dc4b143c01d8fb2d58f118ca6e5076fc69294732ad932a033fd9e572780590234ab0325219e671b088ea3bd634ebacba09a38adf1348c748846d74cebf3a8e83e3668c6a81ff06da756974e3716a97bb98f610a7ea34c514e4949f343522fef0e0041fd67c0f2b349353d30e7def4d479251d654c16ea8934f9af6443b28d1469e81136e326f8eb18f06bdeed031eb37877c8eba0537690edc78b7a79a0260c EAP-Message = 0x94ecee826b7aa51ec23669bcd1204fe4af7415c5ac53b8819658b9de330203010001a317301530130603551d25040c300a06082b06010505070301300d06092a864886f70d0101040500038201010082a4c652c54459e8401c492909980d70aea665fa3aa6fff95d411ec44c0635275a3a4e949405671dc9c910212f55820ccb1ecc67676a4945ac073b02c00971036905a098c27bf7de0e269e8dde5a8edfeb139f0c3cb3f2600b521c677d2eb6e39ceaddcb851a0520824bb5c2ab878c0c48e6a990dc8d130790df56cd6aa4b2f8b441e4bbd71ab38056a812b57dcd90b52b27d7d5bcda44f0b18bd80bca7d2b7cbca476b9692e89f0848d288f0ef1 EAP-Message = 0xb020c38e936b9e9a04df30ee Message-Authenticator = 0x00000000000000000000000000000000 State = 0xeccff048eec2e9d4d10018a42bd2d5e3 Finished request 11. Going to the next request Waking up in 2.8 seconds. rad_recv: Access-Request packet from host 10.1.1.252 port 1206, id=229, length=155 User-Name = "deneme" NAS-IP-Address = 10.1.1.252 NAS-Port = 0 Called-Station-Id = "00-30-4F-44-3D-C1" Calling-Station-Id = "00-18-DE-88-62-77" NAS-Identifier = "WirelessAccessPoint" Framed-MTU = 1380 NAS-Port-Type = Wireless-802.11 EAP-Message = 0x020d00061900 State = 0xeccff048eec2e9d4d10018a42bd2d5e3 Message-Authenticator = 0x49ed19f32e533c2e2e6212cbefba06ea +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "deneme", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 13 length 6 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS [peap] Received TLS ACK [peap] ACK handshake fragment handler [peap] eaptls_verify returned 1 [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] returns handled Sending Access-Challenge of id 229 to 10.1.1.252 port 1206 EAP-Message = 0x010e03fc194061a785cb5c25ebe63f7a160d2c1f092bdcd3a8cdaa0d644290f03ca51affcf791f63d7cc966f95e234a7ba2c3210db60169c3df1079788e7bc2c46e2d66c1000c04372e8e0ee00053a308205363082041ea003020102020900a1eb2dd9c0f33a6f300d06092a864886f70d01010505003081c2310b3009060355040613025452311330110603550408130a446979617262616b697231193017060355040713104469636c6520556e69766572736974793121301f060355040a1318417a697a20595543454c454e2042696c67692049736c656d311f301d06092a864886f70d010901161061797563656c656e406d736e2e636f6d313f30 EAP-Message = 0x3d06035504031436617a697a5f797563656c656e20556e6976657273697479206f66204469636c652043657274696669636174655f417574686f72697479301e170d3130303631363139333834355a170d3130303731363139333834355a3081c2310b3009060355040613025452311330110603550408130a446979617262616b697231193017060355040713104469636c6520556e69766572736974793121301f060355040a1318417a697a20595543454c454e2042696c67692049736c656d311f301d06092a864886f70d010901161061797563656c656e406d736e2e636f6d313f303d06035504031436617a697a5f797563656c656e20556e69 EAP-Message = 0x76657273697479206f66204469636c652043657274696669636174655f417574686f7269747930820122300d06092a864886f70d01010105000382010f003082010a0282010100d77da96a17a6149943cb99cfcf69462800160a68bfacfa0db9f7db970ea7f31c837f97271d9ed68bbb009eb51e4cafc21cf088e50778d141b190deb43d75b7e01e9dc29bd77a647570a308e1c0ab13c2970fed26b5687eb7038725626ddf2e242abd9b3991a2b7853ff86189d8cbe13ed1a2ba351baa5f30236f09653a83c69ab3e3c86a9374853e9e1587065eac334345888405705ff11515c9dbb079e57cd1b661c75f2cb6fec8e44f63f3568507a5d8f58b6e4af7 EAP-Message = 0x34e53975224d0785bb81094c2386919ebb4346de7fbfc60a2d2e76aec8d99fb1c3336eb5a4d57934bbec1dc044f25bc5727700f85484689547d1ce79d0db49a3837e893584eb8d4886870203010001a382012b30820127301d0603551d0e04160414d7e039b49da64df4a94fbc3cd32dc97ccbfb64bd3081f70603551d230481ef3081ec8014d7e039b49da64df4a94fbc3cd32dc97ccbfb64bda181c8a481c53081c2310b3009060355040613025452311330110603550408130a446979617262616b697231193017060355040713104469636c6520556e69766572736974793121301f060355040a1318417a697a20595543454c454e2042696c6769 EAP-Message = 0x2049736c656d311f Message-Authenticator = 0x00000000000000000000000000000000 State = 0xeccff048efc1e9d4d10018a42bd2d5e3 Finished request 12. Going to the next request Waking up in 0.8 seconds. Cleaning up request 9 ID 226 with timestamp +38 Cleaning up request 10 ID 227 with timestamp +38 Waking up in 2.1 seconds. rad_recv: Access-Request packet from host 10.1.1.252 port 1206, id=230, length=155 User-Name = "deneme" NAS-IP-Address = 10.1.1.252 NAS-Port = 0 Called-Station-Id = "00-30-4F-44-3D-C1" Calling-Station-Id = "00-18-DE-88-62-77" NAS-Identifier = "WirelessAccessPoint" Framed-MTU = 1380 NAS-Port-Type = Wireless-802.11 EAP-Message = 0x020e00061900 State = 0xeccff048efc1e9d4d10018a42bd2d5e3 Message-Authenticator = 0x2a1aed16f39db7a2c6ff51380ae5b702 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "deneme", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 14 length 6 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS [peap] Received TLS ACK [peap] ACK handshake fragment handler [peap] eaptls_verify returned 1 [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] returns handled Sending Access-Challenge of id 230 to 10.1.1.252 port 1206 EAP-Message = 0x010f019c1900301d06092a864886f70d010901161061797563656c656e406d736e2e636f6d313f303d06035504031436617a697a5f797563656c656e20556e6976657273697479206f66204469636c652043657274696669636174655f417574686f72697479820900a1eb2dd9c0f33a6f300c0603551d13040530030101ff300d06092a864886f70d0101050500038201010026039182daa55c02d75276bf762638625d94dd28090044a68f044c15a874dc73f9d95bb1f417317d020c7ca3e031601a6272bc41ecdc09e5f627d60e2ef0e855b2ef55e89ebe1de07f89e649c6d27e75154551cfcb6649070ade14372cf017543847b51142182cbb7686 EAP-Message = 0x70c350ca71cd31a2cb47886bd8cb17551ed454271f457402946307396ac5d2bcc0ae40f920447cd8b7fd06d90118e3f64110cadabd454dfea392b75ebeb229719b4f3f344b2aa44a8694c8140de515a8aa11c80befb98b7f3992094520e5c91cde62ddc42a466d5e3761e2153d6ea34d061eef597e0584d29870b35488e7f9f2a17f00c70e641d2b4aaf0202e07225eea1c8b9fbe65416030100040e000000 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xeccff048e8c0e9d4d10018a42bd2d5e3 Finished request 13. Going to the next request Waking up in 1.0 seconds. Cleaning up request 11 ID 228 with timestamp +40 Waking up in 1.9 seconds. rad_recv: Access-Request packet from host 10.1.1.252 port 1206, id=231, length=471 User-Name = "deneme" NAS-IP-Address = 10.1.1.252 NAS-Port = 0 Called-Station-Id = "00-30-4F-44-3D-C1" Calling-Station-Id = "00-18-DE-88-62-77" NAS-Identifier = "WirelessAccessPoint" Framed-MTU = 1380 NAS-Port-Type = Wireless-802.11 EAP-Message = 0x020f0140198000000136160301010610000102010058e134ee813c5df2c7aec907357c4d11170d5592531bf2e5d142b27648f54c720588d2b17831ee0d8b163c500245c9ca58ab0a18177d0289ba51af9ae442ae4f824f06a624970d9beeea7691826c11eb41741375eaabd72b0f023c45c3433056fb4adfbded6bbf18278e0f670f52eb1a793849d1e0b0f5de6dfd5f2417fec5f6d3b4b6390693bf3bb75f29de46d24b0ec882174b6fbbdf8bc3c842d9fb452addcb616cc1b38e8208adf8e02f487e15a641bdebd1b87823aff1f872fc7d41678ea6d727a6400493b1d6da55cef0cafc29cfee74a6e38f81ef295a04529afe66ca79ecb0f754d90960 EAP-Message = 0xf0afc29d9bb8b7d1ec48f850e8300dcad9c77b1d47498ebb1403010001011603010020ac341fafef579e9fbb39c8442996ebcd927065bcd3cee79a61d41a9d87cc9c6f State = 0xeccff048e8c0e9d4d10018a42bd2d5e3 Message-Authenticator = 0xd1383f8c741d2eee900c243621c0f38c +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "deneme", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 15 length 253 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS TLS Length 310 [peap] Length Included [peap] eaptls_verify returned 11 [peap] <<< TLS 1.0 Handshake [length 0106], ClientKeyExchange [peap] TLS_accept: SSLv3 read client key exchange A [peap] <<< TLS 1.0 ChangeCipherSpec [length 0001] [peap] <<< TLS 1.0 Handshake [length 0010], Finished [peap] TLS_accept: SSLv3 read finished A [peap] >>> TLS 1.0 ChangeCipherSpec [length 0001] [peap] TLS_accept: SSLv3 write change cipher spec A [peap] >>> TLS 1.0 Handshake [length 0010], Finished [peap] TLS_accept: SSLv3 write finished A [peap] TLS_accept: SSLv3 flush data [peap] (other): SSL negotiation finished successfully SSL Connection Established [peap] eaptls_process returned 13 [peap] EAPTLS_HANDLED ++[eap] returns handled Sending Access-Challenge of id 231 to 10.1.1.252 port 1206 EAP-Message = 0x0110003119001403010001011603010020946ea9a56d5a8869d64c550c5ec39e505de969b8abcdb94ef288f5981910b1b5 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xeccff048e9dfe9d4d10018a42bd2d5e3 Finished request 14. Going to the next request Waking up in 1.0 seconds. Cleaning up request 12 ID 229 with timestamp +42 Waking up in 1.9 seconds. rad_recv: Access-Request packet from host 10.1.1.252 port 1206, id=232, length=155 User-Name = "deneme" NAS-IP-Address = 10.1.1.252 NAS-Port = 0 Called-Station-Id = "00-30-4F-44-3D-C1" Calling-Station-Id = "00-18-DE-88-62-77" NAS-Identifier = "WirelessAccessPoint" Framed-MTU = 1380 NAS-Port-Type = Wireless-802.11 EAP-Message = 0x021000061900 State = 0xeccff048e9dfe9d4d10018a42bd2d5e3 Message-Authenticator = 0x1e040ebf6b6f48cb08b525fac4f2f46c +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "deneme", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 16 length 6 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS [peap] Received TLS ACK [peap] ACK handshake is finished [peap] eaptls_verify returned 3 [peap] eaptls_process returned 3 [peap] EAPTLS_SUCCESS ++[eap] returns handled Sending Access-Challenge of id 232 to 10.1.1.252 port 1206 EAP-Message = 0x01110020190017030100157296c0b71e3823192738b1788c4fe0467dec236310 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xeccff048eadee9d4d10018a42bd2d5e3 Finished request 15. Going to the next request Waking up in 1.0 seconds. Cleaning up request 13 ID 230 with timestamp +44 Waking up in 2.0 seconds. rad_recv: Access-Request packet from host 10.1.1.252 port 1206, id=233, length=183 User-Name = "deneme" NAS-IP-Address = 10.1.1.252 NAS-Port = 0 Called-Station-Id = "00-30-4F-44-3D-C1" Calling-Station-Id = "00-18-DE-88-62-77" NAS-Identifier = "WirelessAccessPoint" Framed-MTU = 1380 NAS-Port-Type = Wireless-802.11 EAP-Message = 0x0211002219001703010017e6bc773d8860f3b0fbab0544be27f962e06f2e53070cf6 State = 0xeccff048eadee9d4d10018a42bd2d5e3 Message-Authenticator = 0xb6519fa20a989d07f8aef6ebf8f8c0c1 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "deneme", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 17 length 34 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS [peap] eaptls_verify returned 7 [peap] Done initial handshake [peap] eaptls_process returned 7 [peap] EAPTLS_OK [peap] Session established. Decoding tunneled attributes. [peap] Identity - deneme [peap] Got tunneled request EAP-Message = 0x0211000b0164656e656d65 server { PEAP: Got tunneled identity of deneme PEAP: Setting default EAP type for tunneled EAP session. PEAP: Setting User-Name to deneme Sending tunneled request EAP-Message = 0x0211000b0164656e656d65 FreeRADIUS-Proxied-To = 127.0.0.1 User-Name = "deneme" server inner-tunnel { No authenticate method (Auth-Type) configuration found for the request: Rejecting the user Failed to authenticate the user. } # server inner-tunnel [peap] Got tunneled reply code 3 [peap] Got tunneled reply RADIUS code 3 [peap] Tunneled authentication was rejected. [peap] FAILURE ++[eap] returns handled Sending Access-Challenge of id 233 to 10.1.1.252 port 1206 EAP-Message = 0x011200261900170301001be3df65e7ef7891a373fd7d2794b88bd42ad9d6e7f59c7b1a517a52 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xeccff048ebdde9d4d10018a42bd2d5e3 Finished request 16. Going to the next request Waking up in 1.0 seconds. Cleaning up request 14 ID 231 with timestamp +46 Waking up in 1.9 seconds. rad_recv: Access-Request packet from host 10.1.1.252 port 1206, id=234, length=187 User-Name = "deneme" NAS-IP-Address = 10.1.1.252 NAS-Port = 0 Called-Station-Id = "00-30-4F-44-3D-C1" Calling-Station-Id = "00-18-DE-88-62-77" NAS-Identifier = "WirelessAccessPoint" Framed-MTU = 1380 NAS-Port-Type = Wireless-802.11 EAP-Message = 0x021200261900170301001b93c4b2b3423ed61a39a34d66343fdf250f095be821d8f8286720c3 State = 0xeccff048ebdde9d4d10018a42bd2d5e3 Message-Authenticator = 0x899e7167d55a08b8fe446be283c442b3 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "deneme", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 18 length 38 [eap] Continuing tunnel setup. ++[eap] returns ok Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP/peap [eap] processing type peap [peap] processing EAP-TLS [peap] eaptls_verify returned 7 [peap] Done initial handshake [peap] eaptls_process returned 7 [peap] EAPTLS_OK [peap] Session established. Decoding tunneled attributes. [peap] Received EAP-TLV response. [peap] Had sent TLV failure. User was rejected earlier in this session. [eap] Handler failed in EAP/peap [eap] Failed in EAP select ++[eap] returns invalid Failed to authenticate the user. Using Post-Auth-Type Reject +- entering group REJECT {...} [attr_filter.access_reject] expand: %{User-Name} -> deneme attr_filter: Matched entry DEFAULT at line 11 ++[attr_filter.access_reject] returns updated Delaying reject of request 17 for 1 seconds Going to the next request Waking up in 0.9 seconds. Sending delayed reject for request 17 Sending Access-Reject of id 234 to 10.1.1.252 port 1206 EAP-Message = 0x04120004 Message-Authenticator = 0x00000000000000000000000000000000 Cleaning up request 15 ID 232 with timestamp +48 Waking up in 2.0 seconds. Cleaning up request 16 ID 233 with timestamp +50 Waking up in 2.9 seconds. rad_recv: Access-Request packet from host 10.1.1.252 port 1206, id=235, length=142 User-Name = "deneme" NAS-IP-Address = 10.1.1.252 NAS-Port = 0 Called-Station-Id = "00-30-4F-44-3D-C1" Calling-Station-Id = "00-18-DE-88-62-77" NAS-Identifier = "WirelessAccessPoint" Framed-MTU = 1380 NAS-Port-Type = Wireless-802.11 EAP-Message = 0x0213000b0164656e656d65 Message-Authenticator = 0xa423f6547bd5227868a4c6c352b61371 +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "deneme", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 19 length 11 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated ++[unix] returns notfound [files] users: Matched entry deneme at line 1 [files] expand: MERHABA DOSTUM , %{User-Name} -> MERHABA DOSTUM , deneme ++[files] returns ok ++[expiration] returns noop ++[logintime] returns noop [pap] Found existing Auth-Type, not changing it. ++[pap] returns noop Found Auth-Type = EAP +- entering group authenticate {...} [eap] EAP Identity [eap] processing type md5 rlm_eap_md5: Issuing Challenge ++[eap] returns handled Sending Access-Challenge of id 235 to 10.1.1.252 port 1206 Reply-Message = "MERHABA DOSTUM , deneme" EAP-Message = 0x011400160410af2b28a6d3df0c45072b82f0a142941b Message-Authenticator = 0x00000000000000000000000000000000 State = 0xf4615f8cf4755bc39cf766e7435b4d60 Finished request 18. Going to the next request Waking up in 1.0 seconds. rad_recv: Access-Request packet from host 10.1.1.252 port 1206, id=236, length=155 User-Name = "deneme" NAS-IP-Address = 10.1.1.252 NAS-Port = 0 Called-Station-Id = "00-30-4F-44-3D-C1" Calling-Station-Id = "00-18-DE-88-62-77" NAS-Identifier = "WirelessAccessPoint" Framed-MTU = 1380 NAS-Port-Type = Wireless-802.11 EAP-Message = 0x021400060319 State = 0xf4615f8cf4755bc39cf766e7435b4d60 Message-Authenticator = 0x0376988d55b546c2ce24d98616953f3d +- entering group authorize {...} ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop [suffix] No '@' in User-Name = "deneme", looking up realm NULL [suffix] No such realm "NULL" ++[suffix] returns noop [eap] EAP packet type response id 20 length 6 [eap] No EAP Start, assuming it's an on-going EAP conversation ++[eap] returns updated ++[unix] returns notfound [files] users: Matched entry deneme at line 1 [files] expand: MERHABA DOSTUM , %{User-Name} -> MERHABA DOSTUM , deneme ++[files] returns ok ++[expiration] returns noop ++[logintime] returns noop [pap] Found existing Auth-Type, not changing it. ++[pap] returns noop Found Auth-Type = EAP +- entering group authenticate {...} [eap] Request found, released from the list [eap] EAP NAK [eap] EAP-NAK asked for EAP-Type/peap [eap] processing type tls [tls] Initiate [tls] Start returned 1 ++[eap] returns handled Sending Access-Challenge of id 236 to 10.1.1.252 port 1206 Reply-Message = "MERHABA DOSTUM , deneme" EAP-Message = 0x011500061920 Message-Authenticator = 0x00000000000000000000000000000000 State = 0xf4615f8cf57446c39cf766e7435b4d60 Finished request 19. Going to the next request _________________________________________________________________ Yeni Windows 7: Size en uygun bilgisayarı bulun. Daha fazla bilgi edinin. http://windows.microsoft.com/shop
Aziz YÜCELEN wrote:
I am setup again and dont configure defaullts.Run radiusd -X and receive user reject, output is below. Thanks for all. ... Sending tunneled request EAP-Message = 0x0211000b0164656e656d65 FreeRADIUS-Proxied-To = 127.0.0.1 User-Name = "deneme" server inner-tunnel { No authenticate method (Auth-Type) configuration found for the request: Rejecting the user
Did you read the debug output to see if the problem had *changed*? Because it hasn't. You're still using the broken configuration that you created. You need to delete *everything* from the current installation. Binaries, libraries, configuration files, the whole raddb/ directory. Then re-install, and don't mangle the configuration again. It's really not that hard. The documentation and web pages give *explicit* instructions for getting TTLS and PEAP to work. You have ignored those instructions, and done something else. Alan DeKok.
You need to delete *everything* from the current installation. Binaries, libraries, configuration files, the whole raddb/ directory. Then re-install, and don't mangle the configuration again.
Alan DeKok.
hi radtest is ok and output below but pc is not ; maybe pc 8021x configration is incorrect. How do I configure correctly it Thanks rad_recv: Access-Request packet from host 10.1.1.97 port 43367, id=43, length=58 User-Name = "deneme" User-Password = "1" NAS-IP-Address = 127.0.1.1 NAS-Port = 123 +- entering group authorize ++[preprocess] returns ok ++[chap] returns noop ++[mschap] returns noop rlm_realm: No '@' in User-Name = "deneme", looking up realm NULL rlm_realm: No such realm "NULL" ++[suffix] returns noop rlm_eap: No EAP-Message, not doing EAP ++[eap] returns noop ++[unix] returns notfound users: Matched entry deneme at line 90 expand: Hello, %{User-Name} -> Hello, deneme ++[files] returns ok ++[expiration] returns noop ++[logintime] returns noop ++[pap] returns updated rad_check_password: Found Auth-Type auth: type "PAP" +- entering group PAP rlm_pap: login attempt with password "1" rlm_pap: Using clear text password "1" rlm_pap: User authenticated successfully ++[pap] returns ok Login OK: [deneme/1] (from client BIMAP port 123) +- entering group post-auth ++[exec] returns noop Sending Access-Accept of id 43 to 10.1.1.97 port 43367 Reply-Message = "Hello, deneme" Finished request 0. Going to the next request Waking up in 4.9 seconds. Cleaning up request 0 ID 43 with timestamp +3 _________________________________________________________________ Yeni Windows 7: Size en uygun bilgisayarı bulun. Daha fazla bilgi edinin. http://windows.microsoft.com/shop
Aziz YÜCELEN wrote:
radtest is ok and output below but pc is not ; maybe pc 8021x configration is incorrect. How do I configure correctly it Thanks
If you are not going to follow the instructions on this list, there is no point in asking questions. You have been told multiple times what you need to do. Follow the instructions, and the problem will be solved. Or, you can argue and be ignored. Alan DeKok.
participants (2)
-
Alan DeKok -
Aziz YÜCELEN