Re: [Wireshark-users] Unable to post questions at ask.wireshark.org

2024-04-22 Thread Maynard, Chris via Wireshark-users
-users mailto:wireshark-users-boun...@wireshark.org>> On Behalf Of Maynard, Chris via Wireshark-users Sent: Tuesday, April 23, 2024 12:31 AM To: Community support list for Wireshark mailto:wireshark-users@wireshark.org>> Cc: Maynard, Chris mailto:christopher.mayn...@igt.com&g

Re: [Wireshark-users] Unable to post questions at ask.wireshark.org

2024-04-22 Thread Maynard, Chris via Wireshark-users
What is your username on ask.wireshark.org? If your account is blocked, then there’s either a reason it was blocked or possibly it was blocked in error. The first thing to do would be to review your past account activity to determine why your account was blocked in the first place. - Chris

Re: [Wireshark-users] 2 questions

2024-02-09 Thread Maynard, Chris via Wireshark-users
> -Original Message- > From: Wireshark-users On > Behalf Of Maynard, Chris via Wireshark-users > Sent: Tuesday, February 6, 2024 12:21 PM > To: 'Community support list for Wireshark' us...@wireshark.org> > Cc: Maynard, Chris > Subject: Re: [Wire

Re: [Wireshark-users] 2 questions

2024-02-06 Thread Maynard, Chris via Wireshark-users
2 archives are not archiving them? - Chris > -Original Message- > From: Wireshark-users On > Behalf Of Maynard, Chris via Wireshark-users > Sent: Tuesday, February 6, 2024 12:21 PM > To: 'Community support list for Wireshark' us...@wireshark.org> > Cc: Maynard, Chris > Subject:

Re: [Wireshark-users] 2 questions

2024-02-06 Thread Maynard, Chris via Wireshark-users
> -Original Message- > From: Wireshark-users On > Behalf Of Jean-Michel Collard > Sent: Saturday, December 30, 2023 9:37 PM > To: wireshark-users@wireshark.org > Subject: [Wireshark-users] 2 questions > > First of all : Happy New Year to everyone  And a happy belated new year to you! >

Re: [Wireshark-users] Custom CAN dissector script

2023-06-07 Thread Maynard, Chris via Wireshark-users
I don't know why I'm not receiving all messages on this thread, but I'm unable to respond to the latest one from Guy, so I'm responding to this one instead. In any case, here's a simple proof-of-concept in Lua using the "Decode As" solution referenced below: local can_id =

Re: [Wireshark-users] LUA support for compressed protocols

2023-05-31 Thread Maynard, Chris via Wireshark-users
I don’t have any examples to share, but Lua does have support for compressed data in the form of tvbrange:uncompress(name). You could searching at https://wiki.wireshark.org/Lua (as well as the examples and contrib pages) to *possibly* find some examples using it. - Chris Ref: 11.6.3.28.

Re: [Wireshark-users] [Wireshark-dev] The Wireshark wiki has a new home

2020-08-12 Thread Maynard, Chris via Wireshark-users
> -Original Message- > From: Wireshark-dev On Behalf > Of Guy Harris > Sent: Tuesday, August 11, 2020 11:52 PM > To: Developer support list for Wireshark > Cc: Community support list for Wireshark > Subject: Re: [Wireshark-dev] The Wireshark wiki has a new home > > On Aug 11, 2020, at

Re: [Wireshark-users] LUA dissector - combine data from 2 UDP packets, display issue

2020-08-03 Thread Maynard, Chris via Wireshark-users
By the way, in case anyone is interested, attached is the capture file I used to test the “Frag Proto” from https://osqa-ask.wireshark.org/questions/55621/lua-udp-reassembly. - Chris From: Maynard, Chris Sent: Monday, August 3, 2020 5:42 PM To: Community support list for Wireshark Subject:

Re: [Wireshark-users] LUA dissector - combine data from 2 UDP packets, display issue

2020-08-03 Thread Maynard, Chris via Wireshark-users
I download the fragproto.lua implementation from the OSQA question and tested it against the data provided; it seemed to work fine. Without knowing more details about your own dissector, it’s rather difficult to provide more help. Can you share the basics along with some simple test data? -

Re: [Wireshark-users] LUA-script in Tshark

2020-08-03 Thread Maynard, Chris via Wireshark-users
> -Original Message- > From: Wireshark-users On > Behalf Of Gisle Vanem > Sent: Saturday, August 1, 2020 2:54 AM > To: wireshark-users > Subject: [Wireshark-users] LUA-script in Tshark > > Hello list. > > I use this .lua-script: >

Re: [Wireshark-users] Name resolve a custom column

2020-06-20 Thread Maynard, Chris via Wireshark-users
From: Wireshark-users On Behalf Of Sri Sent: Saturday, June 20, 2020 12:27 PM To: wireshark-users@wireshark.org Subject: Re: [Wireshark-users] Name resolve a custom column No, there isn't. What field are you referring to, exactly? Please provide a very small capture file - even 1 single

Re: [Wireshark-users] Newbee - propose Splat Button

2020-05-08 Thread Maynard, Chris via Wireshark-users
he chance to fool around a bit. Stay safe. BobG On 5/7/20 12:57 PM, Bob Gustafson wrote: Super - thanks much. With code too! Now, should I play with this new button Tool, or debug my coreos boot script... Best regards - BobG On 5/7/20 12:38 PM, Maynard, Chris via Wireshark-users wrote: It seems

Re: [Wireshark-users] Newbee - propose Splat Button

2020-05-07 Thread Maynard, Chris via Wireshark-users
It seems like the desired functionality is to inject a "marker" packet into the capture? If so, you could use an external program, something like ping or nc, to do that. I tend to use a separate script for this, something such as: #!/bin/sh if (( ${#} < 1 )) then

Re: [Wireshark-users] CoAP dissector mixed-up about Accept and Content-Format?

2019-11-13 Thread Maynard, Chris via Wireshark-users
> -Original Message- > From: Wireshark-users [mailto:wireshark-users-boun...@wireshark.org] On > Behalf Of Stuart Longland > Sent: Tuesday, November 12, 2019 7:52 PM > To: wireshark-users@wireshark.org > Subject: [Wireshark-users] CoAP dissector mixed-up about Accept and Content- > Format?

Re: [Wireshark-users] accessibility of Wireshark

2019-10-09 Thread Maynard, Chris via Wireshark-users
> -Original Message- > From: Wireshark-users [mailto:wireshark-users-boun...@wireshark.org] On > Behalf Of RJ Sandefur > Sent: Wednesday, October 9, 2019 12:13 AM > To: wireshark-users@wireshark.org > Subject: [Wireshark-users] accessibility of Wireshark > > Hi, I'm RJ. I'd like to know

Re: [Wireshark-users] Wireless toolbar in Wireshark 3.0

2019-09-20 Thread Maynard, Chris via Wireshark-users
> -Original Message- > It is much more convenient to have some more control using the toolbar than > make magic in the console ;-) I agree. > I haven't tried capturing on Windows with npcap yet but as I can see, there's > very little cards supported. > I some years back I desperately

Re: [Wireshark-users] Wireless toolbar in Wireshark 3.0

2019-09-20 Thread Maynard, Chris via Wireshark-users
> -Original Message- > > recently I noticed that the Wireless toolbar is no longer available in > Wireshark > 3.0. > Any idea if/when it will be available? There doesn't appear to be anyone looking into this, but a bug report has been filed for it. See

Re: [Wireshark-users] Capture filter with multiple VLANs

2019-08-01 Thread Maynard, Chris via Wireshark-users
How about a capture filter such as this? "vlan and not (ether[14:2]&0x0fff = 20 or ether[14:2]&0x0fff = 30)" - Chris See also: https://ask.wireshark.org/question/3877/vlan-filter/ > -Original Message- > From: Wireshark-users [mailto:wireshark-users-boun...@wireshark.org] On > Behalf