Last-UE-Activity-Time AVP over S6a in IDA message

asked 2023-04-02 08:48:37 +0000

Why the time is decoded like that "Apr 18, 2089 18:38:39.000000000 UTC" while its Hexa stream is "640f12af" , as when decode this value to the human readable format it gives different date & time, so need to know how Wireshark calculates it please.

answered 2023-04-13 07:32:30 +0000

Anders

5023 ●97 ●58

Hi, I think your timestamp is in UNIX epoch,The Unix epoch (or Unix time or POSIX time or Unix timestamp) is the number of seconds that have elapsed since January 1, 1970 (midnight UTC/GMT), But Looking in RFC 3588, "Time" is "represents the number of seconds since 0h on 1 January 1900 with respect to the Coordinated Universal Time (UTC)."

edit flag offensive delete link

Comments

Yes, my system uses UNIX reference time (1970) and this AVP shall use reference to 1900, but based on this the final timestamp shown in the Wireshark shall be lagging by 70 years (2023 - 70), but what's displayed is leading by 66 years !

Mr.Diaa ( 2023-04-17 14:43:18 +0000 )edit

add a comment

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Last-UE-Activity-Time AVP over S6a in IDA message

1 Answer

Comments

Your Answer

Question Tools

Stats

Last-UE-Activity-Time AVP over S6a in IDA message edit

1 Answer

Comments

Your Answer

Question Tools

Stats

Last-UE-Activity-Time AVP over S6a in IDA message