[Wireshark-dev] gerrit.wireshark.org certificate trouble?

e moment. Can somebody confirm and/or report to the respective sysadmin? Thanks! Regards, Harald -- - Harald Weltehttp://laforge.gnumonks.org/ "

[Wireshark-dev] RFC: Ericsson OM2000 dissector in bugzilla

. If such a mail to the list is uncalled for, please send a STFU! in response and I will not send further such requests to the list. Thanks in advance, Harald -- - Harald Weltehttp://laforge.gnumonk

[Wireshark-dev] Why are authors never Cc'ed before their code is changed?

ea how to improve this situation? 4) How do other wireshark dissector authors deal with this problem? Thanks in advance! Regards, Harald -- - Harald Weltehttp://laforge.gnumonks.org/ "Privacy in r

[Wireshark-dev] [PATCH] new dissector for ip.access GSM A-bis over IP

= --- /dev/null 1970-01-01 00:00:00.0 + +++ epan/dissectors/packet-gsm_abis_ip.c2009-07-03 22:20:16.0 +0200 @@ -0,0 +1,279 @@ +/* packet-gsm_abis_ip.c + * Routines for packet dissection of ip.access A-bis over IP + * Copyright 2009 by Harald Welte + * + * $I

Re: [Wireshark-dev] [PATCH] new dissector for ip.access GSM A-bis over IP

hat function? I don't ;) I'll fix those two issues and re-submit (this time to the bugtracker) as soon as I find a minute for it. Regards, -- - Harald Weltehttp://laforge.gnumonks.org/ "Pri

Re: [Wireshark-dev] [PATCH] new dissector for ip.access GSM A-bis over IP

On Sat, Jul 04, 2009 at 01:55:56PM +0200, Jaap Keuter wrote: > Hi Haralt, > > Could file it in bugs.wireshark.org ? > Thats the way we track patches. ok, will do so. -- - Harald Weltehttp://laforge.

Re: [Wireshark-dev] [PATCH] new dissector for ip.access GSM A-bis over IP

On Sat, Jul 04, 2009 at 01:55:56PM +0200, Jaap Keuter wrote: > Hi Haralt, > > Could file it in bugs.wireshark.org ? > Thats the way we track patches. and updated vrsion has been submitted as bug # 3697 -- - Harald Weltehttp://laforge.

[Wireshark-dev] Does anyone have IuH (RUA/HNBAP) captures?

nside SCTP)? Thanks a lot. -- - Harald Weltehttp://laforge.gnumonks.org/ "Privacy in residential applications is a desirable marketing option." (ET

[Wireshark-dev] hfinfo.string const initializer / change VALS by preference ?

protocols, too. Any help is appreciated. [p.s.: Once the dissector is finished, it will of course be submitted!] -- - Harald Weltehttp://laforge.gnumonks.org/ "Privacy in residential applications i

Re: [Wireshark-dev] hfinfo.string const initializer / change VALS by preference ?

OpenBSC is great project! thanks! wireshark too ;) -- - Harald Weltehttp://laforge.gnumonks.org/ "Privacy in residential applications is a desirable marketing option."

[Wireshark-dev] pcapng / interface names / OPT_IDB_NAME

specific reason why this information is not obtained/displayed or written when writing an output file, even in pcap-ng mode? Maybe there are some preferences I'm missing, or I'm looking at the wrong code? Any related help is appreciated. Regards, Harald --

[Wireshark-dev] MATE, ip_addr and same source/est IP / loopback traffic

ress in there to make sure the IP address is really the only difference in those files] Thanks in advance, Harald p.s.: My tests were don with wireshark Version 3.3.0 (v3.3.0rc0-1701-g4bea0e7c2ebf), but I've been seeing this problem in all my builds for at least 7 month

[Wireshark-dev] MATE not extracting fields as requested

bug or I'm stimply not able to use MATE as expected. Thanks in advance. Regards, Harald -- - Harald Weltehttp://laforge.gnumonks.org/ "Privacy in reside

Re: [Wireshark-dev] MATE not extracting fields as requested

t aware of encapsulations that would repeat multiple gsm_um payload in the one packet * mtp3: Here it is indeed quite normal to have multiple MTP3 messages encapsulated in e.g. one IP/SCTP packet with multiple DATA chunks containing M2UA or M2PA, which then conta

Re: [Wireshark-dev] pcapng / interface names / OPT_IDB_NAME

pecific interface (see "man 7 packet") and when recvmsg() is used, you will get the interface index of the interface on a per-packet basis. Am I misunderstanding the capabilities of AF_PACKET sockets? Or is this simply something wireshark never implemented, but it cou

Re: [Wireshark-dev] MATE, ip_addr and same source/est IP / loopback traffic

addresses the given packets were using. I'll file a bug for this one, then too :/ -- - Harald Weltehttp://laforge.gnumonks.org/ "Privacy in residential applications is a desirable mark

Re: [Wireshark-dev] pcapng / interface names / OPT_IDB_NAME

Hi Guy, On Fri, Oct 23, 2020 at 10:21:36AM -0700, Guy Harris wrote: > On Oct 17, 2020, at 7:25 AM, Harald Welte wrote: > > > I'm currently facing a problem where I need to create pcap files > > Or, at least, *some* form of capture file correct. > Yes, those

Re: [Wireshark-dev] pcapng / interface names / OPT_IDB_NAME

if it's found, write the packet out with that interface index; > > if it's *not* found, write out an IDB for the new interface, > add it to the table, and write the packet out with that interface index. Irrespective of current/future libpcap, this reflects

Re: [Wireshark-dev] MATE not extracting fields as requested

my local build is running. Thanks. Regards, Harald [1] https://gitlab.com/wireshark/wireshark/-/issues/12182 -- - Harald Weltehttp://laforge.gnumonks.org/ "Privacy in residential applications i

[Wireshark-dev] re-load IKEv2 / ESP UAT during wireshark gui runtime

seems rather clumsy to me, if there's no good reason against the good old "signal to re-read config files" approach. Thanks for your input, Harald -- - Harald Weltehttp://laforge.gnumonks.org/ =

Re: [Wireshark-dev] PCAP-over-IP in Wireshark?

d for) to capture telecom signalling traffic. Manual can be found at https://downloads.osmocom.org/docs/latest/osmopcap-usermanual.pdf -- - Harald Weltehttp://laforge.gnumonks.org/ "Privacy in r