Hi again, I think the Redirection delay value isn't working , when I change the value , the progress bar takes always the same time.
I can see the vlan chaning in the client, but the IP is assiged just as the same time when de red message appears , changing the redirection value has the same effect, Ip is assigned after the red message appears. and the redirection doesnt appears to change. El vie., 12 de abr. de 2019 a la(s) 17:38, Leandro Ude ([email protected]) escribió: > Hi, Yes it has all the default values, > > I can even see the request 192.95.20.194 in the laptop using wireshark : > https://i.imgur.com/PMLK1y3.png > > And I still get that error, > > I tried to change Redirection delay value to 40, and same result > > > PD: > > Should I worry about this error on packetfence.log? : > > Apr 12 16:33:45 packetfence pfqueue: pfqueue(3670) WARN: > [mac:c8:5b:76:e6:45:ef] Unable to match MAC address to IP '192.168.1.50' > (pf::ip4log::ip2mac) > > > > > El vie., 12 de abr. de 2019 a la(s) 17:00, Ludovic Zammit ( > [email protected]) escribió: > >> Hello Leandro, >> >> It looks like that your device is being placed into the production vlan >> 10 but the js script on your laptop is not able to reach >> http://192.95.20.194/common/network-access-detection.gif >> >> Check into your web browser console for error in the network section >> while it tries to fetch that gif file. >> >> Make sure to have the default settings. >> >> conf/pf.conf.defauts >> >> network_detection_ip = 192.95.20.194 >> >> image_path = /common/network-access-detection.gif >> >> Most of the time it’s because you need more than 20 secs for your device >> to get the IP and get access to internet. >> >> Increase it under Configuration > Advance Access config > Captive portal >> > Redirection delay >> >> Put 40 or 60 secs. >> >> Thanks, >> >> >> Ludovic [email protected] :: +1.514.447.4918 (x145) :: >> www.inverse.ca >> Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence >> (http://packetfence.org) >> >> >> >> >> >> On Apr 12, 2019, at 3:46 PM, Leandro Ude <[email protected]> wrote: >> >> Hi, thanks to all for the help, >> >> Right now I'm trying to solve this issue : >> >> https://i.imgur.com/JQorvaV.png >> >> After that the network works (I have internet access) but the message is >> always "unable to detect network" >> >> >> As requested I'll attach the logs (txt file) when logging in , >> /usr/local/pf/logs/radius-acct.log >> /usr/local/pf/logs/packetfence.log >> and >> /usr/local/pf/var/run/radiusd-acct.sock >> >> >> Thanks >> >> >> >> >> >> >> >> >> >> El vie., 12 de abr. de 2019 a la(s) 08:13, Nicolas Quiniou-Briand ( >> [email protected]) escribió: >> >>> Hello, >>> >>> On 2019-04-11 7:26 p.m., Leandro Ude via PacketFence-users wrote: >>> > I still can't get to work es network detection http message >>> > >>> > I still get the red message "unable to detect network" : >>> >>> Check packetfence.log for your MAC address to see if PF is able to >>> disconnect correctly your device through RADIUS. >>> -- >>> Nicolas Quiniou-Briand >>> [email protected] :: +1.514.447.4918 *140 :: https://inverse.ca >>> Inverse inc. :: Leaders behind SOGo (https://sogo.nu), PacketFence >>> (https://packetfence.org) and Fingerbank (http://fingerbank.org) >>> >> <logRadius.txt> >> >> >>
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
