[tcpdump-workers] DLT Request for Radio Data System (RDS)

2016-09-13 Thread Jonathan Brucker
I am posting to request a value for DLT_RDS and LINKTYPE_RDS.

Radio Data System (RDS) is a communications protocol standard
published in 1992 for embedding small amounts of digital information
in conventional FM radio broadcasts.

The standard is also known as Radio Broadcast Data System (RBDS) in the US.

References and Specifications:
https://en.wikipedia.org/wiki/Radio_Data_System
http://www.nrscstandards.org/SG/nrsc-4-B.pdf
http://www.rds.org.uk/2010/RDS-Specification.htm

Thanks,
Jonathan Brucker.


RDS Packet Structure

+---+
|  RDS Information Word 1   |
| (2 Octets)|
+---+
|  RDS Information Word 2   |
| (2 Octets)|
+---+
|  RDS Information Word 3   |
| (2 Octets)|
+---+
|  RDS Information Word 4   |
| (2 Octets)|
+---+
|RDS Offset Symbol 1|
| (1 Octet) |
+---+
|RDS Offset Symbol 2|
| (1 Octet) |
+---+
|RDS Offset Symbol 3|
| (1 Octet) |
+---+
|RDS Offset Symbol 4|
| (1 Octet) |
+---+


Description:

Note: the RDS frame is also known as a "group" in the RDS standard.

The RDS frame consists of 4 RDS Information Words, each 16 bits,
followed by 4 Offset Symbols, each 8 bits, for a total of 12 octets.

The Information Words are as specified in the RDS standard.
Encoding is Big-Endian, as in the standard.

The Offset Symbols are ASCII characters representing the detected
syndromes for the corresponding Information Words, and are used in
the interpretation of Information Words, as per RDS standard.

The valid Offset Symbols are:

Offset | in RDS | bit sequence
Symbol | Standard   | in RDS standard
---||
"A"| A  | 001100
"B"| B  | 0110011000
"C"| C  | 0101101000
"c"| c' (C-TAG) | 110101
"D"| D  | 0110110100
"E"| E (MMBS)   | 00

(from US RBDS Standard 1998, tables P.2, P.3)

Sample Frames:

d3 93 05 c8 e1 17 57 44 41 42 43 44
d3 93 05 c9 e1 17 52 20 41 42 43 44
d3 93 05 ca e1 17 33 20 41 42 43 44
d3 93 05 cf e1 17 20 20 41 42 43 44

The preceding 4 frames encode the following station:
* Program Identification (PI) = 0xd393
* Station Name = "WDR 3   "
* Alternate Frequency = 89.8 MHz
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers


Re: [tcpdump-workers] [the-tcpdump-group/tcpdump] tcpdump fails to build when openssl-1.1 was built with --api=1.1.0 (#539)

2016-09-13 Thread Michael Richardson
Lars Wendler  wrote:
> If you think this is not something that requires fixing may I suggest that
> you document the requirement of openssl-1.1.0 being compiled with 
--api=1.0.0
> or --api=0.9.8 somewhere?

How are various distros compiling?  I would imagine either having two
packages, or can it be compiled with both APIs?

--
]   Never tell me the odds! | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works| network architect  [
] m...@sandelman.ca  http://www.sandelman.ca/|   ruby on rails[

___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers


Re: [tcpdump-workers] DLT Request for Radio Data System (RDS)

2016-09-13 Thread Guy Harris
On Sep 4, 2016, at 6:43 AM, Jonathan Brucker  wrote:

> I am posting to request a value for DLT_RDS and LINKTYPE_RDS.
> 
> Radio Data System (RDS) is a communications protocol standard
> published in 1992 for embedding small amounts of digital information
> in conventional FM radio broadcasts.
> 
> The standard is also known as Radio Broadcast Data System (RBDS) in the US.
> 
> References and Specifications:

IEC 62106 Edition 3.0 (2015-03) "Specification of the radio data system (RDS) 
for VHF/FM sound broadcasting in the frequency range from 87,5 MHz to 108,0 
MHz", and earlier versions thereof.

> The Offset Symbols are ASCII characters representing the detected
> syndromes for the corresponding Information Words, and are used in
> the interpretation of Information Words, as per RDS standard.

OK, so in this format the offset words are given as ASCII characters rather 
than as the bit sequences.

I've assigned a value of 265 for LINKTYPE_RDS and DLT_RDS, and added an entry 
for it in http://www.tcpdump.org/linktypes.html; the update to that page 
probably won't appear immediately, but it should show up in 24 hours or so.
___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers


[tcpdump-workers] buildbot failure in OpenCSW Buildbot on tcpdump-solaris10-i386

2016-09-13 Thread buildbot
The Buildbot has detected a new failure on builder tcpdump-solaris10-i386 while 
building OpenCSW Buildbot. Full details are available at:

https://buildfarm.opencsw.org/buildbot/builders/tcpdump-solaris10-i386/builds/1053

Buildbot URL: https://buildfarm.opencsw.org/buildbot/

Buildslave for this Build: unstable10x

Build Reason: The Triggerable scheduler named 'trigger-tcpdump-solaris10-i386' 
triggered this build
Build Source Stamp: HEAD
Blamelist: 

BUILD FAILED: failed shell shell_1 shell_2

Sincerely,
 -The Buildbot



___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers


[tcpdump-workers] buildbot failure in OpenCSW Buildbot on tcpdump-solaris10-amd64

2016-09-13 Thread buildbot
The Buildbot has detected a new failure on builder tcpdump-solaris10-amd64 
while building OpenCSW Buildbot. Full details are available at:

https://buildfarm.opencsw.org/buildbot/builders/tcpdump-solaris10-amd64/builds/1089

Buildbot URL: https://buildfarm.opencsw.org/buildbot/

Buildslave for this Build: unstable10x

Build Reason: The Triggerable scheduler named 'trigger-tcpdump-solaris10-amd64' 
triggered this build
Build Source Stamp: HEAD
Blamelist: 

BUILD FAILED: failed shell shell_1 shell_2

Sincerely,
 -The Buildbot



___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers


[tcpdump-workers] buildbot failure in OpenCSW Buildbot on libpcap-solaris10-amd64

2016-09-13 Thread buildbot
The Buildbot has detected a new failure on builder libpcap-solaris10-amd64 
while building libpcap. Full details are available at:

https://buildfarm.opencsw.org/buildbot/builders/libpcap-solaris10-amd64/builds/466

Buildbot URL: https://buildfarm.opencsw.org/buildbot/

Buildslave for this Build: unstable10x

Build Reason: The SingleBranchScheduler scheduler named 
'schedule-libpcap-solaris10-amd64' triggered this build
Build Source Stamp: [branch master] 21ab5f1175655f1bb523764c7d70bc94c1e651b1
Blamelist: Guy Harris 

BUILD FAILED: failed shell shell_1 shell_3

Sincerely,
 -The Buildbot



___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers


[tcpdump-workers] buildbot failure in OpenCSW Buildbot on libpcap-solaris10-i386

2016-09-13 Thread buildbot
The Buildbot has detected a new failure on builder libpcap-solaris10-i386 while 
building libpcap. Full details are available at:

https://buildfarm.opencsw.org/buildbot/builders/libpcap-solaris10-i386/builds/518

Buildbot URL: https://buildfarm.opencsw.org/buildbot/

Buildslave for this Build: unstable10x

Build Reason: The SingleBranchScheduler scheduler named 
'schedule-libpcap-solaris10-i386' triggered this build
Build Source Stamp: [branch master] 21ab5f1175655f1bb523764c7d70bc94c1e651b1
Blamelist: Guy Harris 

BUILD FAILED: failed shell shell_1 shell_3

Sincerely,
 -The Buildbot



___
tcpdump-workers mailing list
tcpdump-workers@lists.tcpdump.org
https://lists.sandelman.ca/mailman/listinfo/tcpdump-workers