[Wireshark-dev] buildbots aren't building?
The last revision any of the buildbots seem to have built is 41145 whereas 41183 is the last commit. Everything's green, but nothing seems to be happening (according to the waterfall display). Clicking "force build" seems to work. ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Built wireshark failed make[2]: *** [services] Error 1
On Fri, 24 Feb 2012 02:32:51 -0700 Marcel Haas wrote >i wanna bulit wireshark and get a failure. >Maybe someone of u know the reason. >/usr/bin/perl ./tools/make-services.pl >starting to fetch http://www.iana.org/assignments/port-numbers ... >request for http://www.iana.org/assignments/port-numbers failed with >result code:500 at ./tools/make-services.pl line 90 What version of Wireshark are you trying to build? Which operating system? ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Decode MTP3 message
I solve it. First 16 bits are from MTP2 , others are ISUP message than can be decoded. Thanks all Cheers > Date: Fri, 24 Feb 2012 09:24:37 -0500 > From: jeff.morriss...@gmail.com > To: wireshark-dev@wireshark.org > Subject: Re: [Wireshark-dev] Decode MTP3 message > > Martin Kaiser wrote: > > Thus wrote Anya Verizi (anya_ver...@hotmail.com): > > > >> I have to decode this sequence 02 00 10 c0 00 19 81 0f 0f 00 2c 01 01 11 > >> 02 16 00 00 but when I put it in txt and run as pcap I got this > > > your problem is the leading 05 00 00 00 00 bytes > > > Those bytes starting at 05 are, presumably, a fake MTP3 header (i.e., > the sequence above is just ISUP but there's no DLT for just ISUP). > > Do you know what (ISUP) message type this is supposed to be? It's > clearly not an RLC (0x10). I don't think it's a Subsequent Address > (0x02) and 0x00 and 0xc0 aren't valid either. > > Or, do you know what the 02 is supposed to be? The first octet of... > > Are you sure this is ISUP? > ___ > Sent via:Wireshark-dev mailing list > Archives:http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Decode MTP3 message
For example I will take this sequence : MTP3(U)RCV 1/00: ISUP 0 2 0010c0 001981 0d 3d001000 When I put in txt it like this 05 00 00 00 00 3d 00 10 00 I got Release complete message. But I'm not sure what are bits before...I have many those sequences ,ISUP, from which I must figure out where are isup messages... > Date: Fri, 24 Feb 2012 09:24:37 -0500 > From: jeff.morriss...@gmail.com > To: wireshark-dev@wireshark.org > Subject: Re: [Wireshark-dev] Decode MTP3 message > > Martin Kaiser wrote: > > Thus wrote Anya Verizi (anya_ver...@hotmail.com): > > > >> I have to decode this sequence 02 00 10 c0 00 19 81 0f 0f 00 2c 01 01 11 > >> 02 16 00 00 but when I put it in txt and run as pcap I got this > > > your problem is the leading 05 00 00 00 00 bytes > > > Those bytes starting at 05 are, presumably, a fake MTP3 header (i.e., > the sequence above is just ISUP but there's no DLT for just ISUP). > > Do you know what (ISUP) message type this is supposed to be? It's > clearly not an RLC (0x10). I don't think it's a Subsequent Address > (0x02) and 0x00 and 0xc0 aren't valid either. > > Or, do you know what the 02 is supposed to be? The first octet of... > > Are you sure this is ISUP? > ___ > Sent via:Wireshark-dev mailing list > Archives:http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Decode MTP3 message
Martin Kaiser wrote: Thus wrote Anya Verizi (anya_ver...@hotmail.com): I have to decode this sequence 02 00 10 c0 00 19 81 0f 0f 00 2c 01 01 11 02 16 00 00 but when I put it in txt and run as pcap I got this your problem is the leading 05 00 00 00 00 bytes Those bytes starting at 05 are, presumably, a fake MTP3 header (i.e., the sequence above is just ISUP but there's no DLT for just ISUP). Do you know what (ISUP) message type this is supposed to be? It's clearly not an RLC (0x10). I don't think it's a Subsequent Address (0x02) and 0x00 and 0xc0 aren't valid either. Or, do you know what the 02 is supposed to be? The first octet of... Are you sure this is ISUP? ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Decode MTP3 message
Thus wrote Anya Verizi (anya_ver...@hotmail.com):
> I have to decode this sequence 02 00 10 c0 00 19 81 0f 0f 00 2c 01 01 11 02
> 16 00 00 but when I put it in txt and run as pcap I got this
> Frame 1 (23 bytes on wire, 23 bytes captured)
> Arrival Time: Feb 24, 2012 13:38:09.0
> [Time delta from previous captured frame: 0.0 seconds]
> [Time delta from previous displayed frame: 0.0 seconds]
> [Time since reference or first frame: 0.0 seconds]
> Frame Number: 1
> Frame Length: 23 bytes
> Capture Length: 23 bytes
> [Frame is marked: False]
> [Protocols in frame: mtp3:isup]
> Message Transfer Part Level 3
> Service information octet
> 00.. = Network indicator: International network (0x00)
> ..00 = Spare: 0x00
> 0101 = Service indicator: ISUP (0x05)
> Routing label
> ..00 = DPC: 0
> 00.. = OPC: 0
> = Signalling Link Selector: 0
> ISDN User Part
> CIC: 2
> Message type: Release complete (16)
> Pointer to start of optional part: 192
> [Malformed Packet: ISUP]
> [Expert Info (Error/Malformed): Malformed Packet (Exception occurred)]
> [Message: Malformed Packet (Exception occurred)]
> [Severity level: Error]
> [Group: Malformed]
> 05 00 00 00 00 02 00 10 c0 00 19 81 0f 0f 00 2c ...,
> 0010 01 01 11 02 16 00 00 ...
I tried your sequence
[martin@homePc]$ cat a.t2p
00 02 00 10 c0 00 19 81 0f 0f 00 2c 01 01 11 02 16 00 00
[martin@homePc]$ ./text2pcap -l 141 !$ a.pcap
[martin@homePc ]$ ./tshark -r a.pcap -V -x
Frame 1: 18 bytes on wire (144 bits), 18 bytes captured (144 bits) on
interface 0
Interface id: 0
Arrival Time: Feb 24, 2012 14:57:52.0 CET
[Time shift for this packet: 0.0 seconds]
Epoch Time: 1330091872.0 seconds
[Time delta from previous captured frame: 0.0 seconds]
[Time delta from previous displayed frame: 0.0 seconds]
[Time since reference or first frame: 0.0 seconds]
Frame Number: 1
Frame Length: 18 bytes (144 bits)
Capture Length: 18 bytes (144 bits)
[Frame is marked: False]
[Frame is ignored: False]
[Protocols in frame: mtp3:mtp3mg]
Message Transfer Part Level 3
Service information octet
00.. = Network indicator: International network (0x00)
..00 = Spare: 0x00
0010 = Service indicator: Maintenance Special Message
(MTNS) (0x02)
Routing label
..01 = DPC: 4096
Signalling Area Network Code (SANC): Liechtenstein
(Principality of) (2-000)
Unique Signalling Point Name: LTN ISC Vaduz
Signalling Point Operator Name: LTN Liechtenstein TeleNet AG
1100 00.. = OPC: 768
Signalling Area Network Code (SANC): Unknown (0-096)
Unique Signalling Point Name: Unknown
Signalling Point Operator Name: Unknown
= Signalling Link
Selector: 0
Message Transfer Part Level 3 Management
1001 = H0 (Message Group): Unknown (0x09)
Unknown message (13 bytes)
02 00 10 c0 00 19 81 0f 0f 00 2c 01 01 11 02 16 ..,.
0010 00 00 ..
your problem is the leading 05 00 00 00 00 bytes
___
Sent via:Wireshark-dev mailing list
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Decode MTP3 message
I have to decode this sequence 02 00 10 c0 00 19 81 0f 0f 00 2c 01 01 11 02 16
00 00 but when I put it in txt and run as pcap I got this
Frame 1 (23 bytes on wire, 23 bytes captured)
Arrival Time: Feb 24, 2012 13:38:09.0
[Time delta from previous captured frame: 0.0 seconds]
[Time delta from previous displayed frame: 0.0 seconds]
[Time since reference or first frame: 0.0 seconds]
Frame Number: 1
Frame Length: 23 bytes
Capture Length: 23 bytes
[Frame is marked: False]
[Protocols in frame: mtp3:isup]
Message Transfer Part Level 3
Service information octet
00.. = Network indicator: International network (0x00)
..00 = Spare: 0x00
0101 = Service indicator: ISUP (0x05)
Routing label
..00 = DPC: 0
00.. = OPC: 0
= Signalling Link Selector: 0
ISDN User Part
CIC: 2
Message type: Release complete (16)
Pointer to start of optional part: 192
[Malformed Packet: ISUP]
[Expert Info (Error/Malformed): Malformed Packet (Exception occurred)]
[Message: Malformed Packet (Exception occurred)]
[Severity level: Error]
[Group: Malformed]
05 00 00 00 00 02 00 10 c0 00 19 81 0f 0f 00 2c ...,
0010 01 01 11 02 16 00 00 ...
> Date: Fri, 24 Feb 2012 13:51:42 +0100
> From: li...@kaiser.cx
> To: wireshark-dev@wireshark.org
> Subject: Re: [Wireshark-dev] Decode MTP3 message
>
> Thus wrote Anya Verizi (anya_ver...@hotmail.com):
>
> > Can anyone know how I can decode MTP3 message? For example I put code
> > in txt file and then to pcap (text2pcap -l 141 file.txt file.pcap
> > ), but when I open it in wireshark I got malformed packet:ISUP? Do I
> > )must put some in txt file before?
>
> in the input file for text2pcap, each line must start with an offset
> e.g. if your packet contains 0x1 0x2, the input line for text2pcap should be
>
> 00 0x01 0x02
>
> can you run tshark -r -V -x and post the output for one
> malformed packet?
>
> ___
> Sent via:Wireshark-dev mailing list
> Archives:http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
___
Sent via:Wireshark-dev mailing list
Archives:http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
Re: [Wireshark-dev] Decode MTP3 message
Thus wrote Anya Verizi (anya_ver...@hotmail.com): > Can anyone know how I can decode MTP3 message? For example I put code > in txt file and then to pcap (text2pcap -l 141 file.txt file.pcap > ), but when I open it in wireshark I got malformed packet:ISUP? Do I > )must put some in txt file before? in the input file for text2pcap, each line must start with an offset e.g. if your packet contains 0x1 0x2, the input line for text2pcap should be 00 0x01 0x02 can you run tshark -r -V -x and post the output for one malformed packet? ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] Decode MTP3 message
Hello, Can anyone know how I can decode MTP3 message? For example I put code in txt file and then to pcap (text2pcap -l 141 file.txt file.pcap ), but when I open it in wireshark I got malformed packet:ISUP? Do I must put some in txt file before? Thanks Anya ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] Built wireshark failed make[2]: *** [services] Error 1
Hey guys, i wanna bulit wireshark and get a failure. Maybe someone of u know the reason. libtool: link: rm -f .libs/rawshark.nm .libs/rawshark.nmS .libs/rawshark.nmT libtool: link: (cd .libs && gcc -DINET6 -D_U_="__attribute__((unused))" -g -O2 -Wall -W -Wextra -Wdeclaration-after-statement -Wendif-labels -Wpointer-arith -Wno-pointer-sign -Warray-bounds -Wcast-align -Wformat-security -I/usr/local/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/pcap -c -fno-builtin "rawsharkS.c") libtool: link: rm -f ".libs/rawsharkS.c" ".libs/rawshark.nm" ".libs/rawshark.nmS" ".libs/rawshark.nmT" libtool: link: gcc -DINET6 "-D_U_=__attribute__((unused))" -g -O2 -Wall -W -Wextra -Wdeclaration-after-statement -Wendif-labels -Wpointer-arith -Wno-pointer-sign -Warray-bounds -Wcast-align -Wformat-security -I/usr/local/include -pthread -I/usr/include/gtk-2.0 -I/usr/lib64/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/pcap -Wl,--as-needed -o .libs/rawshark rawshark-capture-pcap-util-unix.o rawshark-capture-pcap-util.o rawshark-cfile.o rawshark-clopts_common.o rawshark-disabled_protos.o rawshark-frame_data_sequence.o rawshark-packet-range.o rawshark-print.o rawshark-ps.o rawshark-sync_pipe_write.o rawshark-timestats.o rawshark-util.o rawshark-tap-megaco-common.o rawshark-tap-rtp-common.o rawshark-version_info.o rawshark-rawshark.o .libs/rawsharkS.o -pthread -Wl,--export-dynamic -Wl,--export-dynamic -L/usr/local/lib wiretap/.libs/libwiretap.so epan/.libs/libwireshark.so -L/usr/lib64 /mnt/ssd/wire/wiretap/.libs/libwiretap.so /mnt/ssd/wire/wsutil/.libs/libwsutil.so wsutil/.libs/libwsutil.so -lgthread-2.0 -lrt -lgmodule-2.0 -lglib-2.0 -lm -lpcap -lkrb5 -lk5crypto -lcom_err -lkeyutils -lresolv -ldl -lz -pthread cp tools/idl2wrs.sh idl2wrs chmod +x idl2wrs /usr/bin/perl ./tools/make-services.pl starting to fetch http://www.iana.org/assignments/port-numbers ... request for http://www.iana.org/assignments/port-numbers failed with result code:500 at ./tools/make-services.pl line 90. make[2]: *** [services] Error 101 make[2]: Leaving directory `/mnt/ssd/wire' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/mnt/ssd/wire' make: *** [all] Error 2 regards Marcel ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
[Wireshark-dev] packet-mip, vendor_id, r41171
Hi, I get a warning(==eror) compiling the latest svn [ 5%] Building C object epan/CMakeFiles/epan.dir/dissectors/packet-mip.c.o /home/martin/wireshark.svn/epan/dissectors/packet-mip.c: In function 'dissect_mip_extensions': /home/martin/wireshark.svn/epan/dissectors/packet-mip.c:424:11: error: variable 'nvse_vendor_id' set but not used [-Werror=unused-but-set-variable] cc1: all warnings being treated as errors It looks like this was introduced in r41171. nvse_vendor_id is really not used, but the actual id is stored in an hf and and added to the tree. Could we just remove nvse_vendor_id? Patch attached. Best regards, Martin Index: epan/dissectors/packet-mip.c === --- epan/dissectors/packet-mip.c (revision 41173) +++ epan/dissectors/packet-mip.c (working copy) @@ -421,7 +421,6 @@ gint hdrLen; guint32 cvse_vendor_id; guint16 cvse_vendor_type; - guint32 nvse_vendor_id; guint16 nvse_vendor_type; int cvse_local_offset= 0; int nvse_local_offset= 0; @@ -648,7 +647,6 @@ /*Vendor ID & nvse type & nvse value are included in ext_len, so do not increment offset for them here.*/ nvse_local_offset = offset + hdrLen; proto_tree_add_item(ext_tree, hf_mip_nvse_vendor_org_id, tvb, nvse_local_offset, 4, ENC_BIG_ENDIAN); - nvse_vendor_id = tvb_get_ntohl(tvb, nvse_local_offset); nvse_local_offset+=4; /*Vendor NVSE Type*/ ___ Sent via:Wireshark-dev mailing list Archives:http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
