Date   
Re: YADDNet Registration request

John Pumford-Green
 

Thanks Rosario,

Added to the database.

Cheers.

John

On 05/07/2019 12:07, ros.palermo via Groups.Io wrote:
Hello John/All
My application data

YADDNet Registration request

Rosario
 

Hello John/All

My application data


Name     : Rosario Palermo
RX_ID    : ITZ8294SWL
Location : Ariano irpino, Avellino, Italy
IARU     : JN71MD92VC
Email    : ros.palermo@...


73, Rosario

Re: YADDNet Registration request

John Pumford-Green
 

Thanks Hendrik

Details added to database.

Cheers,

John
GM4SLV

On 05/07/2019 11:41, Hendrik J. Hamer wrote:
Hello John/All
 My application data:

YADDNet Registration request

Hendrik J. Hamer
 

Hello John/All

 My application data:

Name:   Hendrik J. Hamer
QTH:     Vriezenveen NL
IARU:    not available
E-Mail:   hjhamer@...
RX ID's: HOL-DUOr; HOL-NRD-220; HOL-WR-G31DDC
Country: The Netherlands (Prov. Overijssel)

Re: YADDNet Registration request

John Pumford-Green
 

Thanks Frikko,

Added to the database.

Cheers,

John
Gm4SLV

On 05/07/2019 10:10, fj nuijen wrote:
Hello John here are also my application data

Re: YADDNet Registration request

fj nuijen
 

Hello John here are also my application data

Name: Frikko Nuijen
QTH : Boven Pekela 
Loc : JO33LB
E-Mail : NL8811@...
RX id : NL8811
RX Freq : 2.187.500
Country : Netherlands (Prov. Groningen)

Re: Request for registration to YaDDNet

Thomas (tiNG)
 

Hello.


Many thanks, John.


I hope to be QRV until the end of this year.


Kind regards


Thomas (tiNG)
===========================================
      Please reply to funkraum@...
     or contact me on ICQ# 144 821 677
===========================================
   QTH: 54°36'49''N 009°22'43''E, JO44QO
   JRC NRD-525 + VHF/UHF, 2x Icom IC-R71,
     Siemens RK770, Philips D2935 with
      assorted antennas and software.
===========================================
Am 05.07.2019 um 10:21 schrieb John Pumford-Green:

Thanks Thomas!

I've started a Database on the Group Website:

https://groups.io/g/dsc-list/table?id=13068

You are the first member on the list!

Cheers,

John

GM4SLV



On 05/07/2019 09:07, Thomas (tiNG) wrote:
Hi John and group.


Although I'm currently "off air" due to shack still beeing deconstructed I'd like to register for future logging via YaDD.


Here's the requested data:



Re: YADDNet Registration request

John Pumford-Green
 

Thanks Rich,

added to the database table on the group.

Cheers,

John

On 05/07/2019 09:25, Richard Ware wrote:
John/all
Here's my application
Name: Richard Ware (Rich)
Location: Gillingham, Dorset, UK
IARU Locator IO81ub
Receiver ID: Dorset_UK
Email address: richardjware at gmail dot com
There we go !
Rich

YADDNet Registration request

Richard Ware
 

John/all

Here's my application

Name: Richard Ware (Rich)
Location: Gillingham, Dorset, UK
IARU Locator IO81ub
Receiver ID: Dorset_UK
Email address: richardjware at gmail dot com

There we go !
Rich

Re: Request for registration to YaDDNet

John Pumford-Green
 

All,

Just to be as open as possible, I'll even apply for myself...

Name : John Pumford-Green
RX_ID : GM4SLV
Location : Clousta, Shetland, UK
IARU : IP90GG
Email : john@...

Cheers,

John

Re: Request for registration to YaDDNet

John Pumford-Green
 

Thanks Thomas!

I've started a Database on the Group Website:

https://groups.io/g/dsc-list/table?id=13068

You are the first member on the list!

Cheers,

John

GM4SLV

On 05/07/2019 09:07, Thomas (tiNG) wrote:
Hi John and group.
Although I'm currently "off air" due to shack still beeing deconstructed I'd like to register for future logging via YaDD.
Here's the requested data:

Request for registration to YaDDNet

Thomas (tiNG)
 

Hi John and group.


Although I'm currently "off air" due to shack still beeing deconstructed I'd like to register for future logging via YaDD.


Here's the requested data:


Thomas (tiNG)

Germany, Eggebek, JO44QO

"JO44QO" (if possible)

funkraum@...



Hope to read back soon.


Kind regards

--
Thomas (tiNG)
===========================================
      Please reply to funkraum@...
     or contact me on ICQ# 144 821 677
===========================================
   QTH: 54°36'49''N 009°22'43''E, JO44QO
   JRC NRD-525 + VHF/UHF, 2x Icom IC-R71,
     Siemens RK770, Philips D2935 with
      assorted antennas and software.
===========================================

Re: MMSI 22222222

Calico
 

Hi John,

All very interesting indeed-an interesting riddle

I do not assume that commercial fleets cannot have the wrong MMSI.  Rather I used the more tentative term “I
am sceptical”.

Because we do not have any tangible evidence at all, i.e. published reports of any ship station been caught out red-handed. 

I have spent my professional time aboard ships in a radio-coms related role. 
We would never dream of fiddling with MMSIs. Especially when it comes to sailing to such lucrative but also very strict destinations such as Rotterdam and Singapore which is the case with the Baltic Sunrise. 

The professional consequences for anyone involved in any monkey-business, both short and long term, were clear and would lead to dreadful consequences such as:

1) being professionally disqualified, would you do it if you could end-up no more being allowed to work in a job that paid e.g.  your mortgage? 

2) Big trouble for the ship company with insurance brokers and sky-high premiums for the ENTIRE fleet.

3) Being fined and black-listed by port authorities of very hard to get in competitive destinations! 

etc etc 

These are some examples from a practical perspective of why, as I mentioned yesterday, professional legitimate ship stations don’t even dream of messing -up.

Let alone that it is not really that simple to change an MMSI.

If it is a fraud, surely Coast Stations must have noticed. Has either Matt or you perhaps contacted a Coast Station to report it??

Tim

On 5 Jul 2019, at 08:02, John Pumford-Green <john@...> wrote:





On 05/07/2019 00:44, Calico wrote:
Hi Matt again,
When you receive the 22222222 identifiers, do the decoded reports still include longitude-latitude data?  They used at least.


Tim,

That's exactly how we tracked the Medi Kobe, which was using MMSI of Chennai Coast Station. "Chennai" including its GPS coordinates in some DSC messages, initially we spotted Chennai claiming to be in port in Spain, and then going south towards Cape Verde, and across to Brazil.

Obviously it WASN'T actually Chennai on the move....

After watching AIS traffic for vessels following the same course as the DSC position reported by "Chennai" it became evident that only one vessel could be responsible. The Medi Kobe. The correlation between "Chennai's" DSC position and the Medi Kobe AIS position was EXACT.

Wherever the Medi Kobe went (according to its AIS) then Chennai went too (according to its DSC).

Don't assume a Large Vessel can never have the wrong MMSI!

As you may know, the majority of DSC signals on the air are TEST calls, and these DO NOT include positional data. Generally it's only J3E Telephony requests and Distress calls have the position data.

Attached is a search result from YaDDNet showing all DSC messages received from 222222222, of type "J3E Telephony" and carrying "Position" data in the last 12 months.

It looks like the path of a real vessel, and not a DSC-Test-Box.

Perhaps Mats has already extracted the position reports and plotted them on a map?

This is exactly how we correlated the Medi Kobe and Chennai several years ago.

I don't know the details behind Mats deduction about one of the "222222222" stations, being the Baltic Sunrise - I should read back through the group messages - BUT I think you have to be careful to assume ANY large vessel could NEVER (accidentally of for other reasons) have a mis-programmed DSC MMSI.

For the Medi Kobe - they suddenly stopped using Chennai's MMSI and suddenly started using their own MMSI.

Do you have a link for somewhere we might read of formal actions/findings for a case like this, as I assumed at the time that they'd been discovered with a wrong MMSI during an inspection in port, but I don't know how to find out if it ever got noted in a public document.

As for the sudden explosion of a second "222222222" in recent days - it seems to send only to Gris Nez, with a widely varying array of Telecommand symbols, most of them seemingly not valid - this isn't connected (I don't believe) to the one Mats was already monitoring.


All good fun, really.

Cheers,

John





<2019-07-05-074653.txt>

YaDDNet Registration

John Pumford-Green
 

Hello all,


I have now put in place a filter of Receiver IDs on YaDDNet to restrict the ability to upload DSC messages to only registered users.

In the first stage I've added all current uploaders, those who have uploaded data within the last 30 days.

Not included on the access list are those people who have already been responsible for uploading significant quantities of bogus data which needed manual intervention to clean up - and done so more than 3 times, despite repeated requests from me to be careful with configuring YaDD to prevent this.

I now want to begin a NEW list of registered users, arranged via this group, so that all members of the group know who (and where) each YaDDNet reporter is. I will maintain a "YaDDNet Members" list - possibly in the files section of the group - so that everyone can find out which ID belongs to which person, and where in the world they are located.


I will require all uploaders to be members of this group : "The DSC List".

YaDDNet will no longer accept input from ad hoc receiver IDs, even from existing users. Each new RX ID will need to be registered before it will be allowed to upload data.

I want to include as much VALID data,from as many people as possible, in YaDDNet, and I don't want to exclude people from uploading unless they have demonstrated a lack of care in the quality of their data.

Anyone who has already been excluded MAY request access, on the understanding that they MUST ensure that they take better care in future.

I know a registration system won't prevent bad data, but at least I/we will know how to contact the responsible person. At the moment many of the people uploading are not known to us, other than by their RX ID and their IP address (http://gm4slv.plus.com:8000/pages/php/logger_ip.php)


To begin the registration process....

Please send a message to the group with the following information:

Your Name
Your Location : Country/City and IARU Locator
Your Choice of Receiver ID(s) : you may register multiple IDs.
Your email address

I won't accept direct email requests, please send only to the DSC List itself, so that everything is visible to the community.

ALL CURRENT UPLOADERS MUST ALSO SEND THE REQUIRED INFORMATION

Once I have a list of users I will replace the current access-list with a new one carrying only the receiver IDs registered in this way.

At some point in the near future I will also change the network UDP/IP port that accepts YaDDNet messages, and communicate the new information to registered uploaders privately. This will reduce the unsolicited traffic from people who use YaDD's default settings.

I am also intending to change the policy of data retention on YaDDNet - and will send a message about my thoughts separately.

Regards,

John
GM4SLV

YaDDNet

http://gm4slv.plus.com:8000/index.php

Re: MMSI 22222222

John Pumford-Green
 

On 05/07/2019 00:44, Calico wrote:
Hi Matt again,
When you receive the 22222222 identifiers, do the decoded reports still include longitude-latitude data?  They used at least.

Tim,

That's exactly how we tracked the Medi Kobe, which was using MMSI of Chennai Coast Station. "Chennai" including its GPS coordinates in some DSC messages, initially we spotted Chennai claiming to be in port in Spain, and then going south towards Cape Verde, and across to Brazil.

Obviously it WASN'T actually Chennai on the move....

After watching AIS traffic for vessels following the same course as the DSC position reported by "Chennai" it became evident that only one vessel could be responsible. The Medi Kobe. The correlation between "Chennai's" DSC position and the Medi Kobe AIS position was EXACT.

Wherever the Medi Kobe went (according to its AIS) then Chennai went too (according to its DSC).

Don't assume a Large Vessel can never have the wrong MMSI!

As you may know, the majority of DSC signals on the air are TEST calls, and these DO NOT include positional data. Generally it's only J3E Telephony requests and Distress calls have the position data.

Attached is a search result from YaDDNet showing all DSC messages received from 222222222, of type "J3E Telephony" and carrying "Position" data in the last 12 months.

It looks like the path of a real vessel, and not a DSC-Test-Box.

Perhaps Mats has already extracted the position reports and plotted them on a map?

This is exactly how we correlated the Medi Kobe and Chennai several years ago.

I don't know the details behind Mats deduction about one of the "222222222" stations, being the Baltic Sunrise - I should read back through the group messages - BUT I think you have to be careful to assume ANY large vessel could NEVER (accidentally of for other reasons) have a mis-programmed DSC MMSI.

For the Medi Kobe - they suddenly stopped using Chennai's MMSI and suddenly started using their own MMSI.

Do you have a link for somewhere we might read of formal actions/findings for a case like this, as I assumed at the time that they'd been discovered with a wrong MMSI during an inspection in port, but I don't know how to find out if it ever got noted in a public document.

As for the sudden explosion of a second "222222222" in recent days - it seems to send only to Gris Nez, with a widely varying array of Telecommand symbols, most of them seemingly not valid - this isn't connected (I don't believe) to the one Mats was already monitoring.


All good fun, really.

Cheers,

John

DSC log from Dorset_UK 1st-4th July inclusive

Richard Ware
 

Hello all

This covers the period from 1st Jul 0001Z to 4th Jul 2359Z

Nothing outstanding. The plethora of Italian CRS seems to have
stopped, with only Palermo being heard so far this month.
The short evenings don't help.
No sign of Corsen
Cap de la Hague SS was logged on Ch70

20190701 1745 2187.5 002050480 Ostende Radio
20190702 0313 2187.5 002111240 Bremen Radio
20190701 0006 2187.5 002191000 Lyngby Radio
20190701 0015 2187.5 002241022 Coruna Radio
20190701 0002 2187.5 002241024 Valencia Radio
20190701 0017 2187.5 002241026 Las Palmas Radio
20190701 0246 2187.5 002275000 CROSS Etel
20190701 0002 2187.5 002275100 CROSS Gris Nez
20190701 0617 2187.5 002275200 CROSS Jobourg
20190701 0004 2187.5 002320001 Shetland CG
20190701 0028 2187.5 002320004 Aberdeen CG
20190701 0054 2187.5 002320007 Humber CG
20190701 0140 2187.5 002320010 Dover CG
20190701 0029 2187.5 002320011 Solent CG
20190701 0014 2187.5 002320014 Falmouth CG
20190702 0046 2187.5 002320017 Milford Haven CG
20190701 0107 2187.5 002320018 Holyhead CG
20190702 1819 2187.5 002320019 Liverpool CG
20190701 2257 2187.5 002320021 Belfast CG
20190701 1841 2187.5 002320024 Stornoway CG
20190701 0020 2187.5 002442000 Netherlands CG
20190702 0239 2187.5 002470002 Palermo Radio
20190702 0231 2187.5 002500100 Malin Head Radio
20190703 0115 2187.5 002500200 Valentia Radio
20190701 0025 2187.5 002570000 PC Norway
20190702 2116 2187.5 002570100 Tjome Radio
20190701 0149 2187.5 002570300 Rogaland Radio
20190701 0338 2187.5 002570500 Floroe Radio
20190704 2235 2187.5 002570700 Bodoe Radio
20190701 2304 2187.5 002610210 Witowo Radio
20190701 0224 2187.5 002652000 Stockholm Radio
20190701 2209 2187.5 002653000 Goteborg Radio
20190704 2107 2187.5 002711000 Istanbul Radio
20190701 2310 2187.5 002733700 St Petersburg Radio
20190701 0113 2187.5 002770330 Klaipeda MRCC
20190701 0306 2187.5 003313000 Aasiaat Radio
20190703 0600 156525.0 002275100 CROSS Gris Nez
20190702 1156 156525.0 002275200 CROSS Jobourg
20190703 0654 156525.0 002288227 Cap de La Hague SS
20190701 0933 156525.0 002320011 Solent CG
20190702 0709 156525.0 002320012 Portland CG

Decoders: DSC decoder + SeaTTY
Rxs: Alinco DX-R8 and ICOM IC-R6
Log compiled manually. E&OE

Regards
Rich (Dorset_UK)

Re: MMSI 22222222

Calico
 

Hi Matt again,
When you receive the 22222222 identifiers, do the decoded reports still include longitude-latitude data?  They used at least. 

In the (rather unlikely) case they do,
do they bear any QTH similarity? Normally the position is automatically provided by satellite input, hence the coordinates in the received reports could be useful in shedding some light. 

Thanks,
Tim

On 4 Jul 2019, at 22:09, Mats A <omnia@...> wrote:

GMDSS-Testbox

Re: MMSI 22222222

Calico
 

Hi Matts,

Who knows what and mainly who exactly may emit erroneous MMSIs indeed. 

However, as far as established legitimate professional commercial ship-stations are concerned (i.e.  Baltic Sunrise, a larger than 300,000 ton super-tanker), I am sceptical that they would alter their MMSI. 

Have we for example, read in any officially released report that a commercial ship-station has been caught red-handed? If so, can its details be shared please?

73

Tim


On 4 Jul 2019, at 22:09, Mats A <omnia@...> wrote:

Hi Tim and Group,

It my be that some users do use this MMSI, but that is not in accordance with the radio regs. and ITU-R M.585 for the maritime mobile service.

As far as i know the GMDSS-Testbox which is used extensively all over the world by radio surveyors, are programmed with 999999999.
I have two in my possession, and keep track of about 20 units more.

Anyway the insane amount of logs from 222222222 has continued all night and all day long, and at the worst propagation time today (when i arrived at home from work) i received messages about every 4 minutes. I tried to restart everything but it continued to rule out any weird stuff in my setup, but it continued.
Then i tried to connect to well known web SDR servers some 150 km north of me and in northern Germany, and decode the same messages by YaDD there as well.

Maybe someone cleaver have invented a new kind of spam, DSC-spam.

//Mats

Re: MMSI 22222222

Mats A
 

Hi Tim and Group,

It my be that some users do use this MMSI, but that is not in accordance with the radio regs. and ITU-R M.585 for the maritime mobile service.

As far as i know the GMDSS-Testbox which is used extensively all over the world by radio surveyors, are programmed with 999999999.
I have two in my possession, and keep track of about 20 units more.

Anyway the insane amount of logs from 222222222 has continued all night and all day long, and at the worst propagation time today (when i arrived at home from work) i received messages about every 4 minutes. I tried to restart everything but it continued to rule out any weird stuff in my setup, but it continued.
Then i tried to connect to well known web SDR servers some 150 km north of me and in northern Germany, and decode the same messages by YaDD there as well.

Maybe someone cleaver have invented a new kind of spam, DSC-spam.

//Mats

REU - DSC Logs from Ariano Irpino, South Italy

Rosario
 

Report from      :Rosario Palermo iz8294swl

QTH                  :Ariano Irpino AV,Italy

Locators           :41°08'01.8"N 15°04'54.3"E

Receiever         :SDRplay RSP1A, JRC NDR 525

Antenna  1        :genuine PA0RDT MiniWhip at 4m

Antenna  2        :dipole 30 mt

Navtex Decoder   :Yadd 1.7.1

Hi all,

20190703 1444  8414.5 002070810 Varna Radio, BUL, 1071 Km
20190703 1447  8414.5 002371000 Olympia Radio, GRC, 827 Km
20190703 1504  8414.5 002241022 Coruna Radio, ESP, 1904 Km
20190703 1527  8414.5 002091000 Cyprus Radio, CYP, 1729 Km
20190703 1840  2187.5 002711000 Istanbul Radio, TUR, 1154 Km
20190703 1901  2187.5 002070810 Varna Radio, BUL, 1071 Km
20190703 1950  2187.5 002442000 Netherlands CG Radio, HOL, 1475 Km
20190703 2143  2187.5 002191000 Lyngby Radio, DNK, 1687 Km
20190703 2154  2187.5 002371000 Olympia Radio, GRC, 827 Km
20190703 2154  2187.5 002570000 Public Correspondence, NOR, -- Km
20190703 2157  2187.5 002470002 Palermo Radio, SCY, 365 Km
20190703 2159  2187.5 002470124 MRSC Crotone Radio, ITA, 285 Km
20190703 2239  2187.5 002570300 Rogaland Radio, NOR, 2064 Km
20190703 2242  2187.5 002241022 Coruna Radio, ESP, 1904 Km
20190703 2254  2187.5 002734411 Novorossiysk Radio, RUS, 1889 Km
20190703 2258  2187.5 002715000 Izmir Radio, TUR, 1032 Km
20190703 2319  2187.5 002241024 Valencia Radio, ESP, 1412 Km
20190703 2321  2187.5 002320007 Humber Coastguard, ENG, 1972 Km
20190703 2333  2187.5 002320010 Dover Coastguard, ENG, -- Km
20190703 2338  2187.5 002320014 Falmouth Coastguard, ENG, 1925 Km
20190703 2353  2187.5 002275000 CROSS Etel, FRA, 1621 Km
20190703 2359  2187.5 002275400 CROSS La Garde, FRA, 762 Km
20190704 0016  2187.5 002470120 MRSC Augusta Radio, ITA, 429 Km
20190704 0042  2187.5 002712000 Samsun Radio, TUR, 1778 Km
20190704 0047  2187.5 002320001 Shetland Coastguard, SHE, 2438 Km
20190704 0047  2187.5 002311000 Torshavn Radio, FRO, 2746 Km
20190704 0102  2187.5 002734487 Taganrog Radio, RUS, 1966 Km
20190704 0112  2187.5 002241026 Las Palmas Radio, CNR, 3083 Km
20190704 0138  2187.5 002653000 Goteborg Radio, SWE, 1836 Km
20190704 0148  2187.5 002570500 Floroe Radio, NOR, 2379 Km
20190704 0220  2187.5 003313000 Aasiaat Radio, GRL, 4966 Km
20190704 0743  2187.5 002470128 Mazara del Vallo Radio, ITA, 438 Km

73, Rosario