I can see what you are saying about including debug outout. In my case it was a host configuration problem, old iptables rule was blocking coms, and so there was nothing communicating in the debug which was confusing to me at first. Service seemed to take all my configurations and startup fine. Then when i started digging in, I found my answer. Oh and about the MAC mapping,Yep, that was it,The comparisons are all lower case so, the mac's in the file needed to be in lowercase as well. (2) vmps { (2) if (!&VMPS-Mac) { (2) if (!&VMPS-Mac) -> FALSE (2) mac2vlan: Added VMPS-VLAN-Name: 'Printers' to reply_items (2) [mac2vlan] = ok (2) update reply { (2) &VMPS-Packet-Type = VMPS-Join-Response (2) &VMPS-Cookie = &VMPS-MAC -> 00:01:a6:5b:a7:b1 (2) &VMPS-VLAN-Name = "printer" (2) } # update reply = noop Thanks for your help, -- Manny On Wed, Jun 17, 2015 at 8:00 AM, Alan DeKok <aland@deployingradius.com> wrote:
On Jun 16, 2015, at 8:29 PM, Manny <mvarroyo3+freeradius@gmail.com> wrote:
I did not intend to be impolite or offend. I included the config files just in case anyone noticed anything 'odd'. and will refrain.
The issue for me is that there is a *huge* amount of documentation which says what people should post to the list: the debug output. Yet for almost half of the messages here, people post something *else*.
i've redone everything, and have finally gotten vmps responses. to test, i have used the check_vmps package from nagios and it appears to work at least from what I am seeing in the freeradius respones. Has anybody noticed any odd behavior with freeradius when a mac address have letters in it?
Check for uppercase / lowercase. The "mac2vlan" matching is done based on string equality. Ensure that the case in that file is the same as what's printed by the server in debug mode.
Alan DeKok.
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html