Ask Your Question

dandreye's profile - activity

2024-02-13 09:11:21 +0000 received badge  Famous Question (source)
2024-02-13 09:11:21 +0000 received badge  Popular Question (source)
2024-02-13 09:11:21 +0000 received badge  Notable Question (source)
2023-11-29 14:06:05 +0000 commented answer Redefining a proprietary PFCP IE

@Chuckc Sorry just noticed your comment as it was hiding under "see more comments". I did the same byte swap myself too

2023-11-10 17:33:54 +0000 commented answer Redefining a proprietary PFCP IE

Thank you so much!

2023-11-10 17:26:52 +0000 commented answer Redefining a proprietary PFCP IE

Well spotted - thank you: I'll double check with the vendor. Meanwhile a complete sample lua PFCP dissector would still

2023-11-10 17:16:14 +0000 commented answer Redefining a proprietary PFCP IE

@Chuckc: thank you. Can it still be redefined w/o any C/C++ coding then?

2023-11-10 16:44:32 +0000 edited question Redefining a proprietary PFCP IE

Redefining a proprietary PFCP IE Hi All, Proprietary PFCP IE Type 245 is decoded (by the current stable WS build) as so

2023-11-10 16:43:59 +0000 edited question Redefining a proprietary PFCP IE

Redefining a proprietary PFCP IE Hi All, Proprietary PFCP IE Type 245 is decoded (by the current stable WS build) as so

2023-11-10 16:43:12 +0000 edited question Redefining a proprietary PFCP IE

Redefining a proprietary PFCP IE Hi All, Proprietary PFCP IE Type 245 is decoded (by the current stable WS build) as so

2023-11-10 16:42:31 +0000 edited question Redefining a proprietary PFCP IE

Redefining a proprietary PFCP IE Hi All, Proprietary PFCP IE Type 245 is decoded (by the current stable WS build) as so

2023-11-10 16:42:13 +0000 edited question Redefining a proprietary PFCP IE

Redefining a proprietary PFCP IE Hi All, Proprietary PFCP IE Type 245 is decoded (by the current stable WS build) as so

2023-11-10 16:41:34 +0000 edited question Redefining a proprietary PFCP IE

Redefining a proprietary PFCP IE Hi All, Proprietary PFCP IE Type 245 is decoded (by the current stable WS build) as so

2023-11-10 16:40:52 +0000 edited question Redefining a proprietary PFCP IE

Redefining a proprietary PFCP IE Hi All, Proprietary PFCP IE Type 245 is decoded (by the current stable WS build) as so

2023-11-10 16:40:24 +0000 edited question Redefining a proprietary PFCP IE

Redefining a proprietary PFCP IE Hi All, Proprietary PFCP IE Type 245 is decoded (by the current stable WS build) as so

2023-11-10 16:39:59 +0000 edited question Redefining a proprietary PFCP IE

Redefining a proprietary PFCP IE Hi All, Proprietary PFCP IE Type 245 is decoded (by the current stable WS build) as so

2023-11-10 16:39:26 +0000 edited question Redefining a proprietary PFCP IE

Redefining a proprietary PFCP IE Hi All, Proprietary PFCP IE Type 245 is decoded (by the current stable WS build) as so

2023-11-10 16:39:06 +0000 edited question Redefining a proprietary PFCP IE

Redefining a proprietary PFCP IE Hi All, Proprietary PFCP IE Type 245 is decoded (by the current stable WS build) as so

2023-11-10 16:09:45 +0000 asked a question Redefining a proprietary PFCP IE

Redefining a proprietary PFCP IE Hi All, Proprietary PFCP IE Type 245 is decoded (by the current stable WS build) as so

2023-10-29 04:05:34 +0000 received badge  Popular Question (source)
2023-10-29 04:05:34 +0000 received badge  Notable Question (source)
2023-10-29 04:05:34 +0000 received badge  Famous Question (source)
2022-11-10 09:33:38 +0000 received badge  Notable Question (source)
2022-11-10 09:33:38 +0000 received badge  Famous Question (source)
2022-11-10 09:33:38 +0000 received badge  Popular Question (source)
2022-05-04 20:31:38 +0000 received badge  Notable Question (source)
2022-05-04 20:31:38 +0000 received badge  Popular Question (source)
2022-02-16 14:56:17 +0000 marked best answer time displayed without ms with one profile during live capture

Hi All,

It was all working fine with this very Wireshark version 3.4.2 running on Ubuntu 18.04.5 for months and months until recently: Version 3.4.2 (Git v3.4.2 packaged as 3.4.2-1~ubuntu18.04.0+wiresharkdevstable1)

And now despite the profile currently in use still has Time column set to "Time, as specified" as always before, only the whole seconds of relative or absolute time are now displayed during live capture. Switching to a different or default profile "adds the milliseconds back" but switching back to the "damaged" profile in question returns the issue. If however I save my pcap as a file and then open it with the same profile then the milliseconds are there, so only the live traffic capturing and only with the "damaged" profile is being affected. Looks like some setting was accidentally hurt, which I'm struggling to find....any ideas before I recreate the profile from scratch?

Many thanks in anticipation!

2022-02-16 10:08:25 +0000 commented question time displayed without ms with one profile during live capture

@chuckc: spot on: thank you! @cmaynard: the width is fine, so the column just got half empty with Seconds (i.e. whole se

2022-02-16 10:07:44 +0000 commented question time displayed without ms with one profile during live capture

@chuckc: spot on: thank you! @cmaynard: the width is fine, so the column just got half empty with Seconds (i.e. whole se

2022-02-16 08:20:33 +0000 commented question time displayed without ms with one profile during live capture

@chuckc: spot on: thank you! @cmaynard: the width is fine, so the column just got half empty when whole seconds were sel

2022-02-16 08:15:11 +0000 commented question time displayed without ms with one profile during live capture

@chuckc: spot on: thank you! @cmaynard: the width is fine, so the column just becomes half empty when whole seconds are

2022-02-15 22:19:38 +0000 edited question time displayed without ms with one profile during live capture

time displayed without ms with one profile during live capture Hi All, It was all working fine with this very Wireshark

2022-02-15 22:18:29 +0000 edited question time displayed without ms with one profile during live capture

time displayed without ms with one profile during live capture Hi All, It was all working fine with this very Wireshark

2022-02-15 22:17:44 +0000 edited question time displayed without ms with one profile during live capture

time displayed without ms with one profile during live capture Hi All, It was all working fine with this very Wireshark

2022-02-15 22:17:22 +0000 edited question time displayed without ms with one profile during live capture

time displayed without ms with one profile during live capture Hi All, It was all working fine with this very Wireshark

2022-02-15 22:16:38 +0000 asked a question time displayed without ms with one profile during live capture

time displayed without ms with one profile during live capture Hi All, It was all working fine with this very Wireshark

2021-12-04 03:32:24 +0000 received badge  Famous Question (source)
2021-12-04 03:32:24 +0000 received badge  Notable Question (source)
2021-05-06 21:45:32 +0000 commented answer Undissecting tcp2123/tcp2152 currently dissected as GTP

@grahamb I see now: thank you (sorry my OP wasn't detailed enough). I'll have to use the IP addresses in it then.

2021-05-06 21:43:21 +0000 commented answer Undissecting tcp2123/tcp2152 currently dissected as GTP

@grahamb I see now: thank you. I'll have to use the IP addresses in it then.

2021-05-06 18:19:50 +0000 commented answer Undissecting tcp2123/tcp2152 currently dissected as GTP

Well I need it for my genuine GTP traffic that the traffic in question is mixing up with :-)

2021-05-06 18:18:27 +0000 commented answer Undissecting tcp2123/tcp2152 currently dissected as GTP

Well I need it for my genuine GTP traffic that the traffic in question is messing up :-)

2021-05-06 17:10:59 +0000 edited question Undissecting tcp2123/tcp2152 currently dissected as GTP

Undissecting tcp2123/tcp2152 currently dissected as GTP Hi All, can I somehow "undissect" tcp2123/tcp2152 that are curre

2021-05-06 17:08:58 +0000 edited question Undissecting tcp2123/tcp2152 currently dissected as GTP

Undissecting tcp2123/tcp2152 currently dissected as GTP Hi All, can I somehow "undissect" tcp2123/tcp2152 that are curre

2021-05-06 17:07:10 +0000 asked a question Undissecting tcp2123/tcp2152 currently dissected as GTP

Undissecting tcp2123/tcp2152 currently dissected as GTP Hi All, can I somehow "undissect" tcp2123/tcp2152 that are curre

2021-05-04 23:44:35 +0000 commented question wireshark not able to open in external display

Seeing exact same with Ubuntu 18.04 X11 client and Windows Xming X11 server. Was using wireshark-gtk instead of wireshar

2021-05-04 23:44:02 +0000 commented question wireshark not able to open in external display

Seeing exact same with Ubuntu 18.04 X11 client and Windows Xming X11 server. Having to use wireshark-gtk instead of wire

2021-05-04 22:09:16 +0000 commented question wireshark not able to open in external display

Seeing exact same with Ubuntu 18.04. Having to use wireshark-gtk instead of wireshark to get around it. X11 server: Xmin

2021-05-04 22:00:51 +0000 commented question wireshark not able to open in external display

Seeing exact same with Ubuntu 18.04. Having to use wireshark-gtk instead of wireshark to get around it but it doesn't se