|
From: Ian M. <im...@ne...> - 2018-02-22 17:58:45
|
Further to my last post, A big thanks to William McLeod; His response instantly fixed our issue with Android 7.x clients. The fix is simple to implement directly through the GUI. It sounds like a small tweak to packetfence might be prudent, as I am sure Android 7 is well within the scope of a large number of end users. cheers, Ian On Thu, Feb 22, 2018 at 7:36 AM, William McLeod <wm...@nv...> wrote: > Hi Guys, > > > > Sorry for sending this direct. I am not on the PacketFence mailing list > yet and my colleague sent your post through to me. > > > > We had the same issue and I spent some time doing diagnostics on this. > > > > All Android 7.x phones I tested including my own Samsung S8 got the > ‘Internet may not be available’ message. It seems to happen during initial > connection when they carry out a DNS query for ‘www.google.com’, > PacketFence sends back a CNAME=*captiveportal.fqdn* A= > *registration.ipaddress*. For whatever reason Android 7.x doesn’t like > this. > > > > To fix it I added ‘www.google.com’ to the DNS filter with an A record of > 127.0.0.1 and the Android 7.x phones automatically load the captive portal, > for reference here’s how: > > > > From Packetfence administration console, browse to 'Configuration' > > 'Advanced Access Configuration' > 'Filter Engines' > 'DNS Filters', add the > following lines of config at the bottom: > > > > *[www_google_com]* > > *filter = qname* > > *operator = regex* > > *value = www.google.com <http://www.google.com>* > > > > *[1:www_google_com]* > > *scope = registration* > > *answer = $qname 30 IN A 127.0.0.1* > > *rcode = NOERROR* > > > > Then click 'SAVE' > > > > Regards, > > > > > > William McLeod > Future Technology Group Director > |