From: Antonio M. <an...@mi...> - 2011-03-31 15:55:02
|
Should of looked for that UPGRADE document. Thank you Olivier! I am having an issue with RADIUS/packetfence.pm. This is a fresh 2.1 install on a VM. The VM has 4 nics. 1- mgmt (untagged, managed) 2- Registration (tagged with reg-vlan) 3- Isolation (tagged with iso-vlan) What's happening now is that when I authenticate in the CP, the Access-Request packet is originating from 127.0.0.1 in the loopback. This request gets proxied, the Access-Accept Packet comes back, it gets sent back to 127.0.0.1 , freeRADIUS enters post-auth, runs the perl script but packetfence doesn't do anything. It should be logging onto the controller via ssh to disassociate the station. I also get an invalid login or password in the CP even though the packet returned as accept. Could it be something with the packet coming from the 127.0.0.1 instead of the management IP address? On our previous set up, the Access-Request packet came from the IP address of the management interface but what I changed on the last set up is not working on this set up which was adding the IP address and hostname to /etc/hosts. -Antonio On 03/29/2011 05:43 PM, Olivier Bilodeau wrote: > Hi Antonio, > >> Mar 29 12:25:11 pf::WebAPI(14019) ERROR: Can not load perl module for >> switch 10.224.232.220, type: pf::SNMP::Meru::MC3000. Either the type is >> unknown or the perl module has compilation errors. > In UPGRADE document (located in /usr/local/pf/): >> [snip] >> o Upgrading from a version prior to 2.0.1: >> >> [snip] >> - Meru Controller 3000 now named Meru Controller >> Since our code should work for all Meru Controllers, we renamed the module. Meru::MC3000 is now Meru::MC. If you upgrade make sure you update your conf/switches.conf or Configuration -> Switches (in the web admin). > > Also, when this change was performed, the Web Admin was left behind.. > *sigh*.. so you need to configure it directly in conf/switches.conf > until our next release (where it is fixed). > > Cheers! |