freeradius / eap-tls / Android 13

mcury

@johnpoz said in freeradius / eap-tls / Android 13:

Not having any issues.. I do not have a U6-lite, and furom has a uap-ac-lite, which I also have.. I am not seeing any issues with connecting on any of my ap, the lite, the pro or the lr - all just uap-ac, no U6...
I do have a flex HD I could test with, but its currently inactive..

I did have issues with the default values..

At that time, I decided to perform a packet capture and noticed a lot of EAP packets, when it shouldn't have that amount.

After some research, found that changing that value to 1344 fixed all the issues.

https://lists.freeradius.org/pipermail/freeradius-users/2012-January/058297.html

furom

@mcury said in freeradius / eap-tls / Android 13:

@furom Perhaps a fragmentation problem ?
Try to edit eap.conf and set fragment_size = 1344

A nanoHD and a unifi6-lite only worked with wpa2-enterprise after doing this change.

It would be interesting to test... Where do I find "eap" in freeRadius on pfSense?

johnpoz

@furom the eap file would be here

/usr/local/etc/raddb/mods-enabled

@mcury the way I read what you linked seems too says to lower it ;) hehe

"The simplest thing to try is to see eap.conf, and change fragment_size
to something smaller."

furom

@johnpoz said in freeradius / eap-tls / Android 13:

@furom the eap file would be here

/usr/local/etc/raddb/mods-enabled

@mcury the way I read what you linked seems too says to lower it ;) hehe

"The simplest thing to try is to see eap.conf, and change fragment_size
to something smaller."

Well, I set it through the gui and restarted in debug mode. Now verified the value in the file file indeed reads "1344", but same error unfortunately.

It was a good try, thanks for that

mcury

@johnpoz said in freeradius / eap-tls / Android 13:

@mcury the way I read what you linked seems too says to lower it ;) hehe
"The simplest thing to try is to see eap.conf, and change fragment_size
to something smaller.

Indeed, but that pointed me to the right direction, from there I decided to perform a packet capture.
Once I set it to 1344, it worked, no more fragmentation.

I suppose it was here that I got the suggestion for this value from:
https://community.ui.com/questions/Issue-with-WPA2-Enterprise-Across-sites/7070e262-c2c6-403b-a61d-a98ad3b3db53

johnpoz

@mcury that seems to be talking about

"Framed-MTU and set it to 1344 and issue was resolved."

That is different than the fragment size.. Pretty sure that framed -mtu is calculated, I see different values when in debug mode

(3) Framed-MTU = 1400

Different one

(5) User-Name = "tablet.home.arpa"
(5) Framed-MTU += 994

Could you post your full output when you run in debug mode @furom attach as a .txt file.

furom

Could this be of relevance?

No EAP Start, assuming it's an on-going EAP conversation

Just prior to that it tries to match an email (containing a "@") and fails. So perhaps a username must be an email? Worth a try I suppose

johnpoz

@furom said in freeradius / eap-tls / Android 13:

So perhaps a username must be an email? Worth a try I suppose

I see the same notices.. And not having any issue..

(4) # Executing section authorize from file /usr/local/etc/raddb/sites-enabled/default
(4)   authorize {
(4)     [preprocess] = ok
(4)     [chap] = noop
(4)     [mschap] = noop
(4)     [digest] = noop
(4) suffix: Checking for suffix after "@"
(4) suffix: No '@' in User-Name = "tablet.home.arpa", skipping NULL due to config.
(4)     [suffix] = noop
(4) ntdomain: Checking for prefix before "\"
(4) ntdomain: No '\' in User-Name = "tablet.home.arpa", skipping NULL due to config.
(4)     [ntdomain] = noop
(4) eap: Peer sent EAP Response (code 2) ID 192 length 82
(4) eap: No EAP Start, assuming it's an on-going EAP conversation
(4)     [eap] = updated
(4) files: users: Matched entry tablet.home.arpa at line 17
(4)     [files] = ok

mcury

@johnpoz said in freeradius / eap-tls / Android 13:

(3) Framed-MTU = 1400

This value is set in eap.conf, inside: tls-config tls-common {
# fragment_size = 1024
fragment_size = 1344

johnpoz

@mcury Your 2nd link talked about editing the framed-mtu, not the fragment size.. But I believe the framed mtu is normally calculated I thought, I sure don't have a framed-mtu in my eap file, and its seems to be calculating the different framed mtu size based on what size its seeing.

I don't really think its related to that - but something with his android version, seems their are a lot of discussion about android 11 or above and wpa enterprise.. What I have seen seems to be should have a problem in 12 as well. But I think some of these things are handled by the maker changes to their release for their devices.

I am using a lenovo with 12, and @furom is using a samsung with 13.. etc..

What versions of android are you using @mcury and your using eap-tls?

furom

@johnpoz said in freeradius / eap-tls / Android 13:

Could you post your full output when you run in debug mode @furom attach as a .txt file.

Sure, just trying to figure what to mask...

Edit:
This is the output from the run; out.txt

mcury

@johnpoz said in freeradius / eap-tls / Android 13:

What versions of android are you using @mcury and your using eap-tls?

Tested with Android 11, 12, Macbook air M1, Iphone 11 pro (I'm almost sure it is an iphone 11) and Windows 10 and 11 22H1.

Yes, using EAP-TLS (lets encrypt certificate), I just renew it within a 90 day period and upload it to freeradius server.

Let me enable the server here in my lab so I can post the debug for you.

johnpoz

@mcury Yeah not having any issues with iphone (13), ipad (air 5th gen) both running ios 16.5, windows 10 pro 22H2, acer chromebook running whatever latest os is as of day or two ago, and android lenovo p11+ tablet running 12.

Not sure what the issue is with his.. He got his android 7 working with wpa2 enterprise..

@furom did you get your windows test box working? Did you say you found an issue on your switch? So I assume you got your linux and windows and old tablet all working with wpa2-ent

I don't use amce for my certs for eap-tls, all certs via cert manger in pfsense (23.01) using ECDSA with prime256v1 for both the CA and the server and client certs.

Running unifi controller 7.4.156 and uap-ac-pro, lite and lr AP all on 6.5.54 firmware.

edit: here is output of rad -X and my tablet connecting.

debug.txt

Looks like this time it authed connecting to my LR - so have seen valid connections on all 3 of my different APs.

furom

@johnpoz said in freeradius / eap-tls / Android 13:

@mcury Yeah not having any issues with iphone (13), ipad (air 5th gen) both running ios 16.5, windows 10 pro 22H2, acer chromebook running whatever latest os is, and android lenovo p11+ tablet running 12.

Not sure what the issue is with his.. He got his android 7 working with wpa2 enterprise..

@furom did you get your windows test box working? Did you say you found an issue on your switch? So I assume you got your linux and windows and old tablet all working with wpa2-ent

I gave up on the windows client. Issue I had with the Netgate switch was not assigning the correct lan, so when corrected old tablet started working (issue then was it did not get an IP), which is the only client so far

johnpoz

@furom well maybe you want to try the amce certs, there shouldn't be anyway the tablet doesn't trust those.. Not exactly sure how you get a client cert, would assume just need to be able to validate your fqdn via dns would get you the client cert, just like your server cert, etc.

furom

@johnpoz said in freeradius / eap-tls / Android 13:

@furom well maybe you want to try the amce certs, there shouldn't be anyway the tablet doesn't trust those.. Not exactly sure how you get a client cert, would assume just need to be able to validate your fqdn via dns would get you the client cert, just like your server cert, etc.

I have though of it before, but that would require a domain and public DNS, which I don't have.
I really do appreciate you guys trying to find some sense in this. There is a beta of Android 14, not sure if I could load that on my tablet, but could be something. Hopefully this would be fixed in 14, but will hold my breath just a little while longer... :)

But as said earlier, 13 is a lot pickier with trusting the CA's. So I would not be surprised if 'let's encrypt' would work right away, as it is trusted by browsers by default

mcury

I took so long due because this VM wasn't powered on in six months..
My administrator account password expired, users account passwords expired, certificates expired...
More than 160 packages to update in Ubuntu..
Then I got my user stuck in SQL database since simultaneous use is set to one.
What a mess to get this lab working again..

With EAP details, ldap and SQL working.. (Android 12 Galaxy S10 connecting to a nandoHD).
full_test.txt

furom

So found some info last night that said the only way to make Android >11/12 accept a self-signed CA is now to use an MDM (Mobile Device Manager) or a secure app such as Knox to handle the certs.

Edit: Well... put it this way... It was yet another rabbit-hole... A pure nightmare for an average person like myself. Why would I want a full scale mobile deployment environment just to use decent security using certificates - for ONE lousy tablet?? :(

I even tried to get a secure folder working, it would possibly make it work too, but that is not available any longer... bummer...

furom

@furom but isn't this line a bit interersting...

Sat May 27 09:36:29 2023 : ERROR: (4) eap_tls: (TLS) Failed reading from OpenSSL: /var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBSD-src-plus-RELENG_23_01/crypto/openssl/ssl/record/rec_layer_s3.c[1621]:error:14094438:SSL routines:ssl3_read_bytes:tlsv1 alert internal error

It is clearly a path from building pfSense 23.01, or looks that way at least... Perhaps if I try using same certs but with a separate radius server... after all this it could not cause more grief (hopefully)

johnpoz

@furom said in freeradius / eap-tls / Android 13:

Perhaps if I try using same certs but with a separate radius server.

Why would that work? Its the client that has to trust the CA.