Looking like this:
>
> What do you have in /usr/local/fingerbank/logs/fingerbank.log?
> Feb 11 10:43:08 pfqueue(19418) INFO: [mac:2c:41:38:91:62:6f] Found
> combination ID '762488' in schema 'Upstream'
> (fingerbank::Source::LocalDB::_getCombinationID)
> Feb 11 10:43:08 pfqueue(19415) INFO:
Hi Louis!
I'll try that, but I suppose I will also have to restart radiusd, else the
auth-request from the new switches will be refused
Cheers,
- Mail original -
> De: "Louis Munro"
> À: packetfence-users@lists.sourceforge.net
> Envoyé: Mercredi 10 Février 2016
> On Feb 11, 2016, at 4:36 , Frederic Hermann wrote:
>
>
> Hi Louis!
>
> I'll try that, but I suppose I will also have to restart radiusd, else the
> auth-request from the new switches will be refused
>
You should not have to.
What would be the point of
Hello Reeyon,
under wireless do you have machine and user auth ?
Also it should work but you can change the connection_type filter by a
ssid filter.
Something like that:
[ssidsecure]
filter = ssid
operator = is
value = ssidsecure
Regards
Fabrice
Le 2016-02-10 23:33, Reeyon Lim a écrit :
>
> On Feb 11, 2016, at 4:45 , mj wrote:
>
>
> Not sure if "unable to fullfil" is fingerbank-speak for: "your search
> generated no results"?
Not really.
It means we did not get an “exact” match in the local db, so we query the API
for which you have a key.
That’s what
Hello,
I've just upgraded from 4.7 to 5.6.1 and worked through all the upgrade
doc, fixed all my violation syntax, upgraded the db schema incrementally
from 4.7 to 5.0 to 5.1 to 5.2 blah blah all the way to 5.6, added the db
credentials to pfconf.conf, and generally gotten the thing working
Hello Reeyon,
really happy that it's working for you.
In my opinion it's better to use the ssid because it's more specific
than the connection_type (in the case of multiples ssid), but do as you
want.
Regards
Fabrice
Le 2016-02-11 21:30, Reeyon Lim a écrit :
Hello Fabrice,
It is perfect
Hello Fabrice,
It is perfect now :-)
Just realized that supplicant's server CA was causing the problem.
Btw, still stick with connection_type filter Wireless-802.11-EAP and it is
working.
Thank you.
Regards,
Reeyon
On Thu, Feb 11, 2016 at 9:48 PM, Fabrice DURAND wrote:
>