Hi I use freeradius 3.0.x (accounting). I found strange error log message Normal log mode: Fri Aug 7 15:14:09 2015 : Error: Receive - Fri Aug 7 15:14:12 2015 : Error: Receive - Fri Aug 7 15:14:14 2015 : Error: Receive - Fri Aug 7 15:14:17 2015 : Error: Receive - Fri Aug 7 15:14:19 2015 : Error: Receive - When i run radiusd in the debug mode error messages look like: Debug log mode: Receive - Length field value too large, expected maximum of 4096 bytes, got 26209 bytes Receive - Length field value too large, expected maximum of 4096 bytes, got 26209 bytes Pcap is included in the attachment ( between F5 network element and radius instance). The network element is testing RADIUS availability. Thx.
On Aug 7, 2015, at 10:07 AM, Peter Balsianok <balsianok.peter@gmail.com> wrote:
Hi
I use freeradius 3.0.x (accounting). I found strange error log message
Normal log mode: Fri Aug 7 15:14:09 2015 : Error: Receive - Fri Aug 7 15:14:12 2015 : Error: Receive - Fri Aug 7 15:14:14 2015 : Error: Receive - Fri Aug 7 15:14:17 2015 : Error: Receive - Fri Aug 7 15:14:19 2015 : Error: Receive -
When i run radiusd in the debug mode error messages look like: Debug log mode: Receive - Length field value too large, expected maximum of 4096 bytes, got 26209 bytes Receive - Length field value too large, expected maximum of 4096 bytes, got 26209 bytes
Pcap is included in the attachment ( between F5 network element and radius instance). The network element is testing RADIUS availability.
No PCAP attached. Your F5 health probes are configured wrong. I'll fix the messages, they were already fixed in v3.1.x. -Arran
Thank you very much Arran. ( i didnt wait for uploading PCAP file). -Peter On Fri, Aug 7, 2015 at 4:09 PM, Arran Cudbard-Bell < a.cudbardb@freeradius.org> wrote:
On Aug 7, 2015, at 10:07 AM, Peter Balsianok <balsianok.peter@gmail.com> wrote:
Hi
I use freeradius 3.0.x (accounting). I found strange error log message
Normal log mode: Fri Aug 7 15:14:09 2015 : Error: Receive - Fri Aug 7 15:14:12 2015 : Error: Receive - Fri Aug 7 15:14:14 2015 : Error: Receive - Fri Aug 7 15:14:17 2015 : Error: Receive - Fri Aug 7 15:14:19 2015 : Error: Receive -
When i run radiusd in the debug mode error messages look like: Debug log mode: Receive - Length field value too large, expected maximum of 4096 bytes, got 26209 bytes Receive - Length field value too large, expected maximum of 4096 bytes, got 26209 bytes
Pcap is included in the attachment ( between F5 network element and radius instance). The network element is testing RADIUS availability.
No PCAP attached. Your F5 health probes are configured wrong. I'll fix the messages, they were already fixed in v3.1.x.
-Arran
- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
On Aug 7, 2015, at 10:24 AM, Peter Balsianok <balsianok.peter@gmail.com> wrote:
Thank you very much Arran. ( i didnt wait for uploading PCAP file).
Ok, pushed a fix. The problem is the F5 is using a generic UDP service probe on port 1812, you need to configure the special RADIUS probe which sends actual RADIUS packets instead of F5 test data. You're not the first one to run into this. I originally saw the problem a couple of months ago at a customer site. Previously the server didn't emit any error messages when it received a malformed packet, you just saw the "Ready to process requests" message, as the select() returned and blocked again. -Arran
participants (2)
-
Arran Cudbard-Bell -
Peter Balsianok