Hello everyone! :)
With the specifications below, can we install the older version of packetfence
? Is there available older version of the tool?
- 2 Gb of RAM
- Intel 2.10 GHz
- 2 Network Card
- 150 Gb of disk space - Ubuntu 12.04 LTS
we already try to install the tool
We actually did exactly what is on the site, the same site that Fabrice Durand
gave. Is it because on the setup we have that we're having these problems?
Is there any chances to complete this project??
Thanks for all the response :)-Gie
On Tuesday, February 2, 2016 1:25 PM, Margie Carpio
Hello Fabrice,
Now i restarted the config from scratch.
0. wipe out existing parameters in vlan_filters.conf
1. Created AD-computer source, according to the Administration Guide.
2. Map this source to 802.1x portal profile.
3. run raddebug -f /usr/local/pf/var/run/radiusd.sock -t 3600
4. I
Hello Charles,
can you send me your enforcement.pm file ?
Regards
Fabrice
Le 2016-02-03 15:36, Rumford, Charles C a écrit :
>> On Jan 27, 2016, at 3:34 AM, Will Halsall wrote:
>>
>> Hi Fabrice,
>>
>> Yes that fixies it for me (see logs below) .
>>
>> Thank you
>>
>>
> On Jan 27, 2016, at 3:34 AM, Will Halsall wrote:
>
> Hi Fabrice,
>
> Yes that fixies it for me (see logs below) .
>
> Thank you
>
> Will Halsall
>
>
> pfmon.log:Jan 27 08:18:51 pfmon(9137) INFO: modified 00:24:2b:60:ff:79 from
> status 'reg' to 'unreg' based on
The one limitation that I have found with computer authentication with packet
fence and Active directory is that the computer name cannot exceed 14
characters or it breaks.
From: Reeyon Lim [mailto:reeyon...@gmail.com]
Sent: Tuesday, February 02, 2016 9:39 PM
To:
Fabrice,
I am not certain how you get it to work after 15 characters, but everything I
read and have experienced with AD and hostnames being longer than 14/15
characters is that they don't authenticate because AD will truncate them.
https://support.microsoft.com/en-us/kb/909264
There is no limit of 14 characters, i have machine auth with more than
30 characters and there is no issue.
Also did you checked that the client do machine auth ? (windows supplicant)
Regards
Fabrice
Le 2016-02-03 08:52, Tedder, Eric a écrit :
>
> The one limitation that I have found with
Hello Fabrice,
>From the windows supplicant, by default "user and computer authentication"
was chosen in 802.1x settings.
Does PF provides other better solution for 802.1x authentication for BYOD?
Regards,
Reeyon
On Wed, Feb 3, 2016 at 11:55 PM, Fabrice DURAND wrote:
>
You talked about netbios name, not dns name.
In PacketFence, freeradius validate the machine name
(host/FMCART310-15.domain.com) and in PacketFence side we have to create
another authentication source with the user attribute servicePrincipalName.
Check in your AD for a machine account
10 matches
Mail list logo