After settting up a trace i found this error :
what could be the cause? asked 05 Aug '11, 07:09 jay edited 05 Aug '11, 07:22 SYN-bit ♦♦ |
One Answer:
This either was not a radius accounting packet, but wireshark thought it was because it was sent on the radius accounting port (1813) or it was indeed a radius accounting packet, but wireshark was not able to dissect it correctly. answered 05 Aug '11, 07:25 SYN-bit ♦♦ |
We'd need to see the trace - or, at least, the offending packet from the trace - to know for sure, but my suspicion is that it wasn't a RADIUS packet but was dissected as such because it was sent to port 1813. (TCP and UDP ports, unlike, for example, Ethernet packet types, are not certain indicators of packet types.)