<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 5 Aug 2013, at 23:39, Andy <<a href="mailto:andy@brandwatch.com">andy@brandwatch.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Hello,<br><br>This is my first post here so please excuse any missed etiquette.<br><br>I have read through the wiki's and googled a lot and not found anything.<br></blockquote><div><br></div><div><a href="http://wiki.freeradius.org/vendor/HP#RFC-4675-(multiple-tagged/untagged-VLAN)-Assignment">http://wiki.freeradius.org/vendor/HP#RFC-4675-(multiple-tagged/untagged-VLAN)-Assignment</a></div><div><br></div><div>*sigh*</div><div><br></div><blockquote type="cite">I have been trying configure our switch ports (HP 2910al) with Tagged VLANs via Egress-VLANID and Egress-VLAN-Name.<br><br>The Radius backend is OpenLDAP, and I have tried setting the data type in OpenLDAP to binary, UTF-8 and IA5, but no matter what I do, the value returned by RADIUS is the decimal equivalent of the HEX bit string I enter :(<br><br>For example I'm trying to store and send 0x31000012 to indicate a tagged VLAN (0x31) on VLAN 12. But looking at freeradius -X output I can see it sending the decimal number, when the switch wants the bit string as it was stored, and hence throws an error!<br></blockquote><div><br></div><div>No. The HP switch does not care that FreeRADIUS displayed (but later encoded correctly) your hex string as an integer.</div><div><br></div><div>It does care that you don't seem to understand how to convert decimal numbers to hex and are actually specifying VLAN 18 tagged, which probably doesn't exist if you're getting errors.</div><div><br></div><div>You want 0x3100000C for VLAN 12 tagged.</div><div><br></div><div>-Arran</div></div><br></body></html>