Dotaz: Freeradius - připojení

[detektiv]

Zdravím, potřeboval bych poradit. Mám nainstalován freeredius s podporou Mysql. Jako Localhost funguje, ověřuje. AP mám nastavěné v klientech.

Když dám na PC najít wifi síťě tak se snažím připojit, po ověřování mě windows napíše: certifikát pro přihlášení k síti nebyl nalezen. přitom mám u Eap natavený md5 a nepouživám certifikáty.

Kde jsem mohl udělat chybu?

Odpovědi

[detektiv]

Tak jsem zjistil že je to rlm_realm, když dám připojit tak freeradius vypíše:

rlm_realm: No '@' in User-Name = "Z214001\Administrator", looking up realm NULL rlm_realm: No such realm "NULL"

Jak nastavit ten realm? Moc ho nechápu, ale chtěl bych aby uživatel se přihlásil pomocí loginu a hesla. Tady se uvádí jinak uživatel s @.

Jedná se mě hlavně: mám server na kterém běží freeradius a pak v síti AP které bude ověřovat pomocí freeradiusu přístup uživatelů.

[NN]

Pripojis toho uzivatele jako do domeny.. tady

NET\User
heslo

To NET je ten realm, dokonce t oma nekde jeste specialni hack pro pripad toho / lomitka.

Realm se konfiguruje tusim v konfiguraci uctu AP u rad iusu. Jinak souvisi s spise s intergraci s AD a domenou, kterou mate v siti.

NN

[detektiv]

v user mám uživatele test a heslo. v proxy.conf mám realm example.com.

Když otesuji lokálně uživatele v shellu: tak se mě ověří.

echo "User-Name=test@example.com, User-Password=test" | radclient server  auth testing123 -xx
Sending Access-Request of id 216 to 10.1.0.16 port 1812
User-Name = "test@example.com"
User-Password = "test"
rad_recv: Access-Accept packet from host 10.1.0.16 port 1812, id=216, length=20
bart1:/etc/ssl#

Když se chci přihlásit pomocí wifi. tak se me zobrazi okno: kde zadám login: test@example.com heslo: test a doménu example.com

Radius napíše:

Ready to process requests.
rad_recv: Access-Request packet from host 10.1.0.31 port 1239, id=46, length=165
User-Name = "EXAMPLE.COM\\test@example.com"
NAS-IP-Address = 10.1.0.31
NAS-Port = 0
Called-Station-Id = "00-06-25-53-C4-44"
Calling-Station-Id = "00-17-3F-D4-13-AE"
NAS-Identifier = "DWL-900AP+"
Framed-MTU = 1380
NAS-Port-Type = Wireless-802.11
EAP-Message = 0x0201001b015a4d5653312e435a5c74657374407a6d7673312e637a
Message-Authenticator = 0x67e5f3af95e819c5e56f61c8ddec1a21
+- entering group authorize
++[preprocess] returns ok
++[chap] returns noop
++[mschap] returns noop
rlm_realm: Looking up realm "example.com" for User-Name = "EXAMPLE.COM\test@zmvs1.                                              cz"
rlm_realm: Found realm "example.com"
rlm_realm: Adding Stripped-User-Name = "EXAMPLE.COM\test"
rlm_realm: Adding Realm = "example.com"
rlm_realm: Proxying request from user EXAMPLE.COM\test to realm example.com
rlm_realm: Preparing to proxy authentication request to realm "example.com"
++[suffix] returns updated
rlm_eap: Request is supposed to be proxied to Realm example.com.  Not doing EAP.
++[eap] returns noop
++[unix] returns notfound
++[files] returns noop
++[expiration] returns noop
++[logintime] returns noop
++[pap] returns noop
Sending Access-Request of id 118 to 127.0.0.1 port 1812
User-Name = "EXAMPLE.COM\\test"
NAS-IP-Address = 10.1.0.31
NAS-Port = 0
Called-Station-Id = "00-06-25-53-C4-44"
Calling-Station-Id = "00-17-3F-D4-13-AE"
NAS-Identifier = "DWL-900AP+"
Framed-MTU = 1380
NAS-Port-Type = Wireless-802.11
EAP-Message = 0x0201001b015a4d5653312e435a5c74657374407a6d7673312e637a
Message-Authenticator = 0x00000000000000000000000000000000
Proxy-State = 0x3436
Proxying request 0 to home server 127.0.0.1 port 1812
Sending Access-Request of id 118 to 127.0.0.1 port 1812
User-Name = "EXAMPLE.COM\\test"
NAS-IP-Address = 10.1.0.31
NAS-Port = 0
Called-Station-Id = "00-06-25-53-C4-44"
Calling-Station-Id = "00-17-3F-D4-13-AE"
NAS-Identifier = "DWL-900AP+"
Framed-MTU = 1380
NAS-Port-Type = Wireless-802.11
EAP-Message = 0x0201001b015a4d5653312e435a5c74657374407a6d7673312e637a
Message-Authenticator = 0x00000000000000000000000000000000
Proxy-State = 0x3436
Going to the next request
Waking up in 0.9 seconds.
rad_recv: Access-Request packet from host 127.0.0.1 port 1814, id=118, length=16                                              0
User-Name = "EXAMPLE.COM\\test"
NAS-IP-Address = 10.1.0.31
NAS-Port = 0
Called-Station-Id = "00-06-25-53-C4-44"
Calling-Station-Id = "00-17-3F-D4-13-AE"
NAS-Identifier = "DWL-900AP+"
Framed-MTU = 1380
NAS-Port-Type = Wireless-802.11
EAP-Message = 0x0201001b015a4d5653312e435a5c74657374407a6d7673312e637a
Message-Authenticator = 0xba800dfc7642e7056d5790324755d5b2
Proxy-State = 0x3436
+- entering group authorize
++[preprocess] returns ok
++[chap] returns noop
++[mschap] returns noop
rlm_realm: No '@' in User-Name = "EXAMPLE.COM\test", looking up realm NULL
rlm_realm: No such realm "NULL"
++[suffix] returns noop
rlm_eap: EAP packet type response id 1 length 27
rlm_eap: No EAP Start, assuming it's an on-going EAP conversation
++[eap] returns updated
++[unix] returns notfound
++[files] returns noop
++[expiration] returns noop
++[logintime] returns noop
rlm_pap: WARNING! No "known good" password found for the user.  Authentication m                                              ay fail because of this.
++[pap] returns noop
rad_check_password:  Found Auth-Type EAP
auth: type "EAP"
+- entering group authenticate
rlm_eap: Identity does not match User-Name, setting from EAP Identity.
rlm_eap: Failed in handler
++[eap] returns invalid
auth: Failed to validate the user.
Login incorrect: [EXAMPLE.COM\\test/<via Auth-Type = EAP>] (from client localhost p                                              ort 0 cli 00-17-3F-D4-13-AE)
Found Post-Auth-Type Reject
+- entering group REJECT
expand: %{User-Name} -> EXAMPLE.COM\test
attr_filter: Matched entry DEFAULT at line 11
++[attr_filter.access_reject] returns updated
Delaying reject of request 1 for 1 seconds
Going to the next request
Waking up in 0.9 seconds.
Sending delayed reject for request 1
Sending Access-Reject of id 118 to 127.0.0.1 port 1814
Proxy-State = 0x3436
Waking up in 4.9 seconds.
rad_recv: Access-Reject packet from host 127.0.0.1 port 1812, id=118, length=24
Proxy-State = 0x3436
+- entering group post-proxy
rlm_eap: No pre-existing handler found
++[eap] returns noop
Login incorrect (Home Server says so): [EXAMPLE.COM\\test@example.com/<no User-Password attribute>]

(from client default port 0 cli 00-17-3F-D4-13-AE)
Found Post-Auth-Type Reject
+- entering group REJECT
expand: %{User-Name} -> EXAMPLE.COM\test@example.com
attr_filter: Matched entry DEFAULT at line 11
++[attr_filter.access_reject] returns updated
Sending Access-Reject of id 46 to 10.1.0.31 port 1239
Finished request 0.
Going to the next request
Waking up in 4.9 seconds.
Cleaning up request 1 ID 118 with timestamp +45
Cleaning up request 0 ID 46 with timestamp +45
Ready to process requests.

[NN]

A kdyz se prihlasis bez domeny ? Ktera se mu v usrname ocividne nelibi..

NN

[detektiv]

Tak jsem dal dva uzivatele test steve helslo mají stejný:

 

Ready to process requests.
rad_recv: Access-Request packet from host 10.1.0.31 port 1239, id=122, length=129
User-Name = "test"
NAS-IP-Address = 10.1.0.31
NAS-Port = 0
Called-Station-Id = "00-06-25-53-C4-44"
Calling-Station-Id = "00-15-AF-39-16-4C"
NAS-Identifier = "DWL-900AP+"
Framed-MTU = 1380
NAS-Port-Type = Wireless-802.11
EAP-Message = 0x020100090174657374
Message-Authenticator = 0xd278c274afa5aa724a28704593978c6a
+- entering group authorize
++[preprocess] returns ok
++[chap] returns noop
++[mschap] returns noop
rlm_realm: No '@' in User-Name = "test", looking up realm NULL
rlm_realm: No such realm "NULL"
++[suffix] returns noop
rlm_eap: EAP packet type response id 1 length 9
rlm_eap: No EAP Start, assuming it's an on-going EAP conversation
++[eap] returns updated
++[unix] returns notfound
users: Matched entry test at line 76
expand: Hello, %{User-Name} -> Hello, test
++[files] returns ok
++[expiration] returns noop
++[logintime] returns noop
rlm_pap: Found existing Auth-Type, not changing it.
++[pap] returns noop
rad_check_password:  Found Auth-Type EAP
auth: type "EAP"
+- entering group authenticate
rlm_eap: EAP Identity
rlm_eap: processing type md5
rlm_eap_md5: Issuing Challenge
++[eap] returns handled
Sending Access-Challenge of id 122 to 10.1.0.31 port 1239
Reply-Message = "Hello, test"
EAP-Message = 0x010200160410e04222730af0b163802bca6fc02604fd
Message-Authenticator = 0x00000000000000000000000000000000
State = 0x299dfeda299ffab745048b38aa0bd1dd
Finished request 0.
Going to the next request
Waking up in 4.9 seconds.
rad_recv: Access-Request packet from host 10.1.0.31 port 1239, id=123, length=144
User-Name = "test"
NAS-IP-Address = 10.1.0.31
NAS-Port = 0
Called-Station-Id = "00-06-25-53-C4-44"
Calling-Station-Id = "00-15-AF-39-16-4C"
NAS-Identifier = "DWL-900AP+"
Framed-MTU = 1380
NAS-Port-Type = Wireless-802.11
EAP-Message = 0x020200060319
State = 0x299dfeda299ffab745048b38aa0bd1dd
Message-Authenticator = 0x2d0efca9f4b9807f356bb080f9d160c4
+- entering group authorize
++[preprocess] returns ok
++[chap] returns noop
++[mschap] returns noop
rlm_realm: No '@' in User-Name = "test", looking up realm NULL
rlm_realm: No such realm "NULL"
++[suffix] returns noop
rlm_eap: EAP packet type response id 2 length 6
rlm_eap: No EAP Start, assuming it's an on-going EAP conversation
++[eap] returns updated
++[unix] returns notfound
users: Matched entry test at line 76
expand: Hello, %{User-Name} -> Hello, test
++[files] returns ok
++[expiration] returns noop
++[logintime] returns noop
rlm_pap: Found existing Auth-Type, not changing it.
++[pap] returns noop
rad_check_password:  Found Auth-Type EAP
auth: type "EAP"
+- entering group authenticate
rlm_eap: Request found, released from the list
rlm_eap: EAP NAK
rlm_eap: NAK asked for unsupported type 25
rlm_eap: No common EAP types found.
rlm_eap: Failed in EAP select
++[eap] returns invalid
auth: Failed to validate the user.
Login incorrect: [test/<via Auth-Type = EAP>] (from client default port 0 cli 00-15-AF-39-16-4C)
Found Post-Auth-Type Reject
+- entering group REJECT
expand: %{User-Name} -> test
attr_filter: Matched entry DEFAULT at line 11
++[attr_filter.access_reject] returns updated
Delaying reject of request 1 for 1 seconds
Going to the next request
Waking up in 0.9 seconds.
Sending delayed reject for request 1
Sending Access-Reject of id 123 to 10.1.0.31 port 1239
Reply-Message = "Hello, test"
EAP-Message = 0x04020004
Message-Authenticator = 0x00000000000000000000000000000000
Waking up in 3.4 seconds.
Cleaning up request 0 ID 122 with timestamp +19
Waking up in 1.5 seconds.
Cleaning up request 1 ID 123 with timestamp +20
Ready to process requests.
rad_recv: Access-Request packet from host 10.1.0.31 port 1239, id=124, length=131
User-Name = "steve"
NAS-IP-Address = 10.1.0.31
NAS-Port = 0
Called-Station-Id = "00-06-25-53-C4-44"
Calling-Station-Id = "00-15-AF-39-16-4C"
NAS-Identifier = "DWL-900AP+"
Framed-MTU = 1380
NAS-Port-Type = Wireless-802.11
EAP-Message = 0x0201000a017374657665
Message-Authenticator = 0xe75246ced5ba6ba7aecb341fa342f644
+- entering group authorize
++[preprocess] returns ok
++[chap] returns noop
++[mschap] returns noop
rlm_realm: No '@' in User-Name = "steve", looking up realm NULL
rlm_realm: No such realm "NULL"
++[suffix] returns noop
rlm_eap: EAP packet type response id 1 length 10
rlm_eap: No EAP Start, assuming it's an on-going EAP conversation
++[eap] returns updated
++[unix] returns notfound
users: Matched entry steve at line 80
++[files] returns ok
++[expiration] returns noop
++[logintime] returns noop
rlm_pap: Found existing Auth-Type, not changing it.
++[pap] returns noop
rad_check_password:  Found Auth-Type EAP
auth: type "EAP"
+- entering group authenticate
rlm_eap: EAP Identity
rlm_eap: processing type md5
rlm_eap_md5: Issuing Challenge
++[eap] returns handled
Sending Access-Challenge of id 124 to 10.1.0.31 port 1239
Service-Type = Framed-User
Framed-Protocol = PPP
Framed-IP-Address = 172.16.3.33
Framed-IP-Netmask = 255.255.255.0
Framed-Routing = Broadcast-Listen
Framed-Filter-Id = "std.ppp"
Framed-MTU = 1500
Framed-Compression = Van-Jacobson-TCP-IP
EAP-Message = 0x0102001604106bb6313333ce85b400f5b07dd94c5064
Message-Authenticator = 0x00000000000000000000000000000000
State = 0x0dc82af30dca2ea51c9bcf8d79d8dd5f
Finished request 2.
Going to the next request
Waking up in 4.9 seconds.
rad_recv: Access-Request packet from host 10.1.0.31 port 1239, id=125, length=145
User-Name = "steve"
NAS-IP-Address = 10.1.0.31
NAS-Port = 0
Called-Station-Id = "00-06-25-53-C4-44"
Calling-Station-Id = "00-15-AF-39-16-4C"
NAS-Identifier = "DWL-900AP+"
Framed-MTU = 1380
NAS-Port-Type = Wireless-802.11
EAP-Message = 0x020200060319
State = 0x0dc82af30dca2ea51c9bcf8d79d8dd5f
Message-Authenticator = 0x002a508ea8cbf68103797e227eef1496
+- entering group authorize
++[preprocess] returns ok
++[chap] returns noop
++[mschap] returns noop
rlm_realm: No '@' in User-Name = "steve", looking up realm NULL
rlm_realm: No such realm "NULL"
++[suffix] returns noop
rlm_eap: EAP packet type response id 2 length 6
rlm_eap: No EAP Start, assuming it's an on-going EAP conversation
++[eap] returns updated
++[unix] returns notfound
users: Matched entry steve at line 80
++[files] returns ok
++[expiration] returns noop
++[logintime] returns noop
rlm_pap: Found existing Auth-Type, not changing it.
++[pap] returns noop
rad_check_password:  Found Auth-Type EAP
auth: type "EAP"
+- entering group authenticate
rlm_eap: Request found, released from the list
rlm_eap: EAP NAK
rlm_eap: NAK asked for unsupported type 25
rlm_eap: No common EAP types found.
rlm_eap: Failed in EAP select
++[eap] returns invalid
auth: Failed to validate the user.
Login incorrect: [steve/<via Auth-Type = EAP>] (from client default port 0 cli 00-15-AF-39-16-4C)
Found Post-Auth-Type Reject
+- entering group REJECT
expand: %{User-Name} -> steve
attr_filter: Matched entry DEFAULT at line 11
++[attr_filter.access_reject] returns updated
Delaying reject of request 3 for 1 seconds
Going to the next request
Waking up in 0.9 seconds.
Sending delayed reject for request 3
Sending Access-Reject of id 125 to 10.1.0.31 port 1239
EAP-Message = 0x04020004
Message-Authenticator = 0x00000000000000000000000000000000
Waking up in 3.9 seconds.
Cleaning up request 2 ID 124 with timestamp +41
Waking up in 1.0 seconds.
Cleaning up request 3 ID 125 with timestamp +41
Ready to process requests.