Hi Peter - Thanks for the reply. We are very familiar with the device registration page -- our users use it quite frequently.
For this specific scenario, the MAC address the user was entering was not being allowed to be registered on that page -- even though we have Google Home (and Google Home Mini) added under *Configuration --> Advanced Access Configuration --> Device Registration*. A Catch 22 really because the device is unable to connect to the network and Fingerbank can't classify it for me to see what I *should* be adding in the setting above (because clearly it's not being classified as a Google Home. Again, ultimately my issue is that we can't even get the device to connect to the network -- it's not a matter of registering it. I saw nothing in packetfence.log, but maybe I'll try a radius debug. Thanks again! Max -- Max McGrath <http://www.linkedin.com/in/max-mcgrath-a299124b> Infrastructure and Security Manager Carthage College 262-551-6666 [email protected] On Thu, Jan 10, 2019 at 4:56 PM Truax, Peter via PacketFence-users < [email protected]> wrote: > 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 > <https://urldefense.proofpoint.com/v2/url?u=http-3A__-253cpf-2Dserver-2Dip-253e_status&d=DwMGaQ&c=6woNz-MH7rT4h2NzwpOIrDoM44CA9bO_yzozu4WPyPQ&r=cz9bFTuo0gfmX0NZrLwiOdqnmojS2OEjy-Q_kIRFWXU&m=YpfvDO6TQ4fvdt2KX67UwyI93tTxXkeNaopGLNARyEY&s=iq3wsJiarazKvfdOesu2OMVjdUKiy9XqNPxVz4A2hoc&e=> > > > > > 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 > > > > > > *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: 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://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_in_max-2Dmcgrath-2Da299124b&d=DwMGaQ&c=6woNz-MH7rT4h2NzwpOIrDoM44CA9bO_yzozu4WPyPQ&r=cz9bFTuo0gfmX0NZrLwiOdqnmojS2OEjy-Q_kIRFWXU&m=YpfvDO6TQ4fvdt2KX67UwyI93tTxXkeNaopGLNARyEY&s=g7_5La7PRDzq062c6iT_FMesEbLXapLOoW0YsXoAofI&e=> > Infrastructure and Security Manager > Carthage College > 262-551-6666 > [email protected] > _______________________________________________ > PacketFence-users mailing list > [email protected] > > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.sourceforge.net_lists_listinfo_packetfence-2Dusers&d=DwICAg&c=6woNz-MH7rT4h2NzwpOIrDoM44CA9bO_yzozu4WPyPQ&r=cz9bFTuo0gfmX0NZrLwiOdqnmojS2OEjy-Q_kIRFWXU&m=YpfvDO6TQ4fvdt2KX67UwyI93tTxXkeNaopGLNARyEY&s=ph_X7o7g_aBoQhz3KAxJjPKZmfI_v5aHWg5-NvGtLqA&e= >
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
