>From "Policies and Access Control->Profiles->MY_NET->automatically registered
>device,scan engine->openvas" I use connection ethernet-NoEAP for MAB, no
>automatically registered wih radius and only scans engine -> openvas
and inside "Compliance->Scan Engine->Openvas->ip,user,password,aler,s
Is it caused by linux based dhcp-forwarder ? As I can see the correct dhcp
packets in my linux server. And I use udp-reflector to forward the traffic to
pf. The cmd is "/usr/local/bin/udp_reflector -s pcap9:67 -d :767 -b
25000 &"___
PacketFence-users m
Hello Murilo,
I dont see any logs in those locations for some reason. They are empty
files. We have syslog-ng running on the same box, so i suspect rsyslog
was removed.
Thanks
Blake
On Wed, Jan 30, 2019 at 2:05 PM Murilo Calegari <
murilo.calegari.so...@gmail.com> wrote:
> Hi, Blake,
>
> P
Hi, Blake,
Please post packetfence.log and radius.log for the authentication of a
specific device.
Regards,
Murilo Calegari
Em qua, 30 de jan de 2019 19:36, William Blake MacIsaac via
PacketFence-users escreveu:
> Hello All,
>
> I'm having a heck of a time setting up Packetfence with 802.1X W
Hello All,
I'm having a heck of a time setting up Packetfence with 802.1X Wireless
(WPA2 Enterprise).As soon as i add the WLC (MERU) to the switch group,
anyone can authenticate to the Wireless SSID without any authentication
happening. I have followed the steps in the packetfence documentat
On 2019-01-30 10:49 a.m., IT?? wrote:
--3.?0?2Do?0?2you?0?2see?0?2logs?0?2in?0?2/usr/local/pf/logs/pfdhcplistener.log?0?2?
You should see DHCP requests in this file.
--
Nicolas Quiniou-Briand
n...@inverse.ca :: +1.514.447.4918 *140 :: https://inverse.ca
Inverse inc. :: Leaders behind SOGo
Hello Fabrice,
and thanks for your reply, i tracked the nonworking part down to:
there is no portal http instance on https://127.0.01:443
what did i do to have it be gone ? i dont know, i did not reconfigure
anything. I think it may have been the first reboot after updates which
caused that.
Hello,
upon further investigation, i guess ha-proxy-portal cannot connect to
127.0.0.1:80
Jan 30 11:25:42 srv-wlan haproxy[26179]: backend 192.168.220.1-backend
has no server available!
Jan 30 11:25:51 srv-wlan haproxy[26179]: 192.168.220.27:51630
[30/Jan/2019:11:25:48.287] portal-http-192.1
Hi!
The documentation [1] states that the HPE 5400 series supports "downloadable
ACLs". During my tests with an HPE Aruba 5412 zl2 v3 I noticed that the Perl
module used (Procurve_5400.pm) neither inherited nor implemented the
returnRadiusAccessAccept function.
The function implemented in 2930M.p
1. Do you see DHCP incoming traffic coming on your management interface ?
2. Does pfdhcplistener is running on this interface ?
3. Do you see logs in /usr/local/pf/logs/pfdhcplistener.log ?
--
Nicolas Quiniou-Briand
n...@inverse.ca :: +1.514.447.4918 *140 :: https://inverse.ca
Inverse inc. :
Thank you very much. I did this to detect nodes but pf can't detect any nodes
now. Our dhcp server is also the core switch, I make a traffic mirror of dhcp
traffic to my linux server. And then forwarding the dhcp traffic to pf
management ip via udp_reflector tool. I do get the traffic on pf mana
11 matches
Mail list logo
