Problem gt02/gt06

Ricky0112 years ago

Hi everyone, having trouble with china unit sold as gt02 but I'm getting this on port 5023:

2023-04-10 23:49:02  INFO: [T09ec35d9: gt06 < 188.120.102.51] 7e0100002d01917289059300000022044e373034343443303036445f4f50454e5f4a54383038000000003238393035393302d4c1423237313931d47e

If I decode it I get:
N70444C006D_OPEN_JT808 2890593 B27191
and some rubbish that can't even be pasted.

Please help?

Anton Tananaev2 years ago

You should probably read this first:

https://www.traccar.org/clones/

Ricky0112 years ago

Thanks, I already did, that's how I got to the hex to text.

Anton Tananaev2 years ago

OK. Can you please post the logs with all the ports tested.

Ricky0112 years ago

Well that is another problem… I’ve tested all the ports listed, and only when I use port 5023 I get something in the log, the rest of the ports don’t put anything in the log.

I’ve tested with tcpdump on Linux, the device is sending traffic on all ports, but Traccar log is empty, except for port 5023.

Thanks so much!

Anton Tananaev2 years ago

OK, let's see the tcpdump and also provide proof that Traccar is using those ports and not some other process.

Ricky0112 years ago

Would you like pcap file, or something else?

Process listening on clone related ports is java:

(00:40:00)root@omega:~> netstat -tulpan | grep 5001
tcp6       0      0 :::5001                 :::*                    LISTEN      322741/java
udp6       0      0 :::5001                 :::*                                322741/java
(00:40:11)root@omega:~> netstat -tulpan | grep 5002
tcp6       0      0 :::5002                 :::*                    LISTEN      322741/java
udp6       0      0 :::5002                 :::*                                322741/java
(00:40:15)root@omega:~> netstat -tulpan | grep 5006
tcp6       0      0 :::5006                 :::*                    LISTEN      322741/java
(00:40:20)root@omega:~> netstat -tulpan | grep 5013
tcp6       0      0 :::5013                 :::*                    LISTEN      322741/java
udp6       0      0 :::5013                 :::*                                322741/java
(00:40:27)root@omega:~> netstat -tulpan | grep 5015
tcp6       0      0 :::5015                 :::*                    LISTEN      322741/java
(00:40:32)root@omega:~> netstat -tulpan | grep 5023
tcp6       0      0 :::5023                 :::*                    LISTEN      322741/java
tcp6       0      0 164.68.101.170:5023     188.120.102.51:8448     ESTABLISHED 322741/java
tcp6       0      0 164.68.101.170:5023     77.243.29.173:4864      ESTABLISHED 322741/java
tcp6       0      0 164.68.101.170:5023     77.243.29.172:4608      ESTABLISHED 322741/java
(00:40:44)root@omega:~> netstat -tulpan | grep 5036
tcp6       0      0 :::5036                 :::*                    LISTEN      322741/java
(00:40:57)root@omega:~> netstat -tulpan | grep 5093
tcp6       0      0 :::5093                 :::*                    LISTEN      322741/java
Anton Tananaev2 years ago

Maybe netstat output would be enough. I see that you have active connections on port 5023, but nothing on other ports. Configure your device to send data to port 5015 and show that there's an active connection.

Ricky0112 years ago

tcpdump on port 5015:

(00:49:38)root@omega:~> tcpdump -nnvvi any port 5015
tcpdump: listening on any, link-type LINUX_SLL (Linux cooked v1), capture size 262144 bytes
00:54:26.694451 IP (tos 0x0, ttl 116, id 623, offset 0, flags [none], proto TCP (6), length 52)
    77.243.29.172.4613 > 164.68.101.170.5015: Flags [S], cksum 0xfd30 (correct), seq 187397, win 64240, options [mss 1400,nop,wscale 1,nop,nop,sackOK], length 0
00:54:26.694598 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52)
    164.68.101.170.5015 > 77.243.29.172.4613: Flags [S.], cksum 0x75b4 (incorrect -> 0x347f), seq 1407743094, ack 187398, win 64240, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
00:54:27.697027 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52)
    164.68.101.170.5015 > 77.243.29.172.4613: Flags [S.], cksum 0x75b4 (incorrect -> 0x347f), seq 1407743094, ack 187398, win 64240, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
00:54:29.713046 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52)
    164.68.101.170.5015 > 77.243.29.172.4613: Flags [S.], cksum 0x75b4 (incorrect -> 0x347f), seq 1407743094, ack 187398, win 64240, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
00:54:33.809092 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52)
    164.68.101.170.5015 > 77.243.29.172.4613: Flags [S.], cksum 0x75b4 (incorrect -> 0x347f), seq 1407743094, ack 187398, win 64240, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
00:54:42.005096 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52)
    164.68.101.170.5015 > 77.243.29.172.4613: Flags [S.], cksum 0x75b4 (incorrect -> 0x347f), seq 1407743094, ack 187398, win 64240, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0
00:54:58.129128 IP (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto TCP (6), length 52)
    164.68.101.170.5015 > 77.243.29.172.4613: Flags [S.], cksum 0x75b4 (incorrect -> 0x347f), seq 1407743094, ack 187398, win 64240, options [mss 1460,nop,nop,sackOK,nop,wscale 7], length 0

netstat:

(00:54:49)root@omega:~> netstat -tulpan | grep 5015
tcp6       0      0 :::5015                 :::*                    LISTEN      322741/java
tcp6       0      0 164.68.101.170:5015     77.243.29.172:4613      SYN_RECV    -

log: nothing...

Anton Tananaev2 years ago

This seems suspicious:

cksum 0x75b4 (incorrect -> 0x347f)

It's also not clear why the connection is in the SYN_RECV state.

I suspect you have some network or system issue.

Ricky0112 years ago

in the meantime, it connected, somehow...

2023-04-11 17:36:18  INFO: [T7f397582] connected
2023-04-11 17:36:18  INFO: [T7f397582: huabao < 77.243.25.192] 7e0100002d019172890593005a0022044e373034343443303036445f4f50454e5f4a54383038000000003238393035393302d4c14232373139318e7e
2023-04-11 17:36:18  INFO: [T7f397582: huabao > 77.243.25.192] 7e8100000f0191728905930000005a003031393137323839303539332b7e

but no GPS info, only that the tracker was online XY minutes ago...

Anton Tananaev2 years ago

That's because it didn't report any GPS info.

Ricky0112 years ago

you think it's broken/malfunctioning?

Anton Tananaev2 years ago

Not sure. Maybe it just doesn't have a GPS fix. Or it could be some other reason.

Ricky0112 years ago

GPS is ok, when I ask for GPS info with SMS text "G1234" I get proper coordinates:

http://maps.google.com/maps?q=+44.65558,+020.19856
ID:19172890593
ACC:OFF
GPS:V
Speed:0.00KM/H
23-04-12 00:10:50