Hi Max,

For these kind of devices that don’t have a browser, (ie smart tvs, printers, 
Alexa’s, etc) to register through the captive portal, we have our system set up 
to allow people to register their own devices at  a web page: 
http://<pf-server-ip>/status<http://%3cpf-server-ip%3e/status>

They log in with their username and password. They can then see all of their 
registered devices. On the page is a button marked, register a device. They 
click that, and enter the MAC address of the device that doesn’t have a 
browser. The device then gets the same role as the user, and is able to access 
the network without hitting the captive portal.

The way you registered them, sound like it would work too, just more work on 
your end. You should see a radius attempt and accept in the radius.log file for 
that mac address. Maybe there is something to turn on the wifi on the Google 
mini? Also, you can run a radius debug to see exactly what is happening when 
you try to connect.

Peter Truax
Network Administrator
(360) 688-2240
Saint Martin’s University
5000 Abbey Way E
Lacey, WA 98503

[cid:[email protected]]

From: Max McGrath via PacketFence-users 
<[email protected]>
Sent: Wednesday, January 9, 2019 11:27 AM
To: ML PF <[email protected]>
Cc: Max McGrath <[email protected]>
Subject: [External] [PacketFence-users] Connecting Google Home mini to my open 
network

CAUTION: This email is from an outside sender. Do not click on links or open 
attachments unless you recognize the sender and know the content is safe.



Hello -

I'm having some issues with students connecting their Google Home minis to our 
open (unencrypted) network.  We currently have two examples of this, but fear 
there could be hundreds more when our next semester starts.

Long story short, it appears that Google Homes do not currently support 
connections with captive portals, not great, but at least we know.

So I had the student find the MAC address of their Google Home.  It seems this 
is not very straightforward either.  It is not printed on the box or anywhere 
to be found -- so they worked with Google, got a network analyzer, ran a 
capture and found the MAC address.  I have since confirmed the MAC address they 
found is correct (see below):

[image.png]
Because they can't connect to the network themselves, I went ahead and created 
a node with the given MAC address, registered it and gave it a proper role.  I 
then went through the Google Home setup routine and it still cannot connect.  I 
was hoping because it was registered, it wouldn't run into the captive portal 
and it would just work!  That doesn't seem to be the case.  In fact, I've 
looked in packetfence.log in all three of my PF nodes, and I don't see any 
evidence of the Google Mini trying to connect.

Any ideas on how to get these things connected?

Thanks!

Max
--
Max McGrath 
[https://static.licdn.com/scds/common/u/img/webpromo/btn_profile_greytxt_80x15.png]
 <http://www.linkedin.com/in/max-mcgrath-a299124b>
Infrastructure and Security Manager
Carthage College
262-551-6666
[email protected]<mailto:[email protected]>
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to