Ok. Please see attach. But I'm afraid that is may only case, my unfortunate radius configuration. This is not directly received from the switch packet but from switch->dhcrelay. On Fri, 28 May 2010 13:11:57 +0700 Alan DeKok <aland@deployingradius.com> wrote:
Please supply a packet trace (wireshark / tcpdump) which contains that packet. If we had seen this issue in testing 2.1.9, we would have fixed it.
How to use this announced feature of sub-option for opt82 ?
It was tested to work with a number of different switches.
How to find the reason why radiusd (2.1.9) eats 100% of CPU ?
Supply a "pcap" file containing the packet, so we can reproduce the problem, and fix it.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
-- Anton [WARM-RIPE] Stack ltd division head tel. 8 (3822) 555-797