Hi Derek,
found the problem, my Packetfence-VM migrated to an ESX-Host with faulty
network configuration which prevented the dhcp requests of the clients to
reach packetfence.
Now its working and violations are triggered as expected.
Thanks !
2015-05-07 16:01 GMT+02:00 Derek Wuelfrath <[email protected]>:
> Dennis,
>
> Can you share a bit more logs.
> I’m interested in pfdhcplistener.log and
> /usr/local/fingerbank/logs/fingerbank.log
>
> Cheers!
> dw.
>
> --
> Derek Wuelfrath
> [email protected] :: +1.514.447.4918 (x110) :: +1.866.353.6153 (x110)
> Inverse inc. (www.inverse.ca) :: Leaders behind SOGo (www.sogo.nu) and
> PacketFence (www.packetfence.org)
>
> On May 6, 2015 at 07:38:41, Dennis Bühring ([email protected]) wrote:
>
> Hi,
>
> i've created this violation to autoregister some notebooks, but it does
> not seem to work
>
> [1500002]
> priority=1
> trigger=mac_vendor::7932
> actions=autoreg,role
> desc=expertLenovo
> enabled=Y
> template=p2p
> auto_enable=N
> whitelisted_categories=
> target_category=mitarbeiter
>
> This is from the packetfence.log
>
> ==> packetfence.log <==
> May 06 11:47:42 httpd.aaa(2090) INFO: [00:1f:16:13:1e:3d] handling radius
> autz request: from switch_ip => (172.16.4.19), connection_type =>
> WIRED_MAC_AUTH,switch_mac => (14:58:d0:a5:85:3f), mac =>
> [00:1f:16:13:1e:3d], port => 1, username => "001f16131e3d"
> (pf::radius::authorize)
> May 06 11:47:42 httpd.aaa(2090) INFO: [00:1f:16:13:1e:3d] does not yet
> exist in database. Adding it now (pf::radius::authorize)
> May 06 11:47:42 httpd.aaa(2090) INFO: Could not find any IP phones through
> discovery protocols for ifIndex 1 (pf::Switch::getPhonesDPAtIfIndex)
> May 06 11:47:42 httpd.aaa(2090) INFO: [00:1f:16:13:1e:3d] is of status
> unreg; belongs into registration VLAN (pf::vlan::getRegistrationVlan)
> May 06 11:47:42 httpd.aaa(2090) INFO: [00:1f:16:13:1e:3d] (172.16.4.19)
> Returning ACCEPT with VLAN 127 and role
> (pf::Switch::returnRadiusAccessAccept)
> May 06 11:48:28 httpd.aaa(2090) INFO: Update of the locationlog based on
> accounting data is not supported on network device type
> pf::Switch::HP::Procurve_2920. (pf::Switch::supportsRoamingAccounting)
> May 06 11:55:25 httpd.aaa(2090) INFO: [00:20:6b:8d:86:85] handling radius
> autz request: from switch_ip => (172.16.4.19), connection_type =>
> WIRED_MAC_AUTH,switch_mac => (14:58:d0:a5:85:3b), mac =>
> [00:20:6b:8d:86:85], port => 5, username => "00206b8d8685"
> (pf::radius::authorize)
>
>
> I've been using violations to register devices with 4.6.1 without any
> problems
>
>
> Any idea what im missing ?
>
> regards
>
> Dennis
>
> ------------------------------------------------------------------------------
>
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
>
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y_______________________________________________
> PacketFence-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/packetfence-users
>
>
--
-------------------------------
oben Balken, unten Balken !
-------------------------------
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
