tracker-server.log

Eadmund2 years ago

Hi,

My raspbery-pi install runs and works with the mobile phone client fine. I'm now trying to crack the nut of getting the actual tracker (a Deaohk TK300 working (clone I think). This does not connect and I have no idea of port / protocol - so I am following your guidance and looking at logs...

However, when connecting with the working phone, I get no entries in the log? Is this correct? Is there a verbose logging flag (or whatever) I need to set? I figure I need to see log entries for this before I start worying about the clone - just so I know its all working to that point!

any help or advice appriciated!

Regards

Eadmund

Anton Tananaev2 years ago

Have you checked the troubleshooting guide?

Eadmund2 years ago

Hi Anton

Thanks for replying. Yes I did look – it turned out to be a ipv6 routing issue on the raspberry pi 4. I turned it off and using only ipv4 everything sprang to life (I noticed using netstat).

I added to end of etc sysctl.conf (see below)

net.ipv6.conf.all.disable_ipv6 = 1
net.ipv6.conf.default.disable_ipv6 = 1
net.ipv6.conf.lo.disable_ipv6 = 1

I’ve had to a pain of a setup to get round my fritzbox router only allowing 1 port mapping per ip and mac for external access. In the end I added the following to etc rc.local to create a second mac address and so ip that the frizbox was happy to create DHCP entries for and so route to from externally accessing devices. I used: ip link add link eth0 address 00:22:22:22:22:22 eth0.2 type macvlan. I locked the frizt so it always issues those addresses, tied them via ports 8082 & 5023 (the now determined correct port for the protocol) and turned of any automatic port mapping – and it all worked.

Your guide on examining protocols in the logs was fantastic – thanks!

For anyone else trying to get this working on a pi 4, I also had to download the java client and re-point the app to it before it ran – I don’t know why it didn’t run on a pi, by default but it really resisted until I did this. (service wouldn’t start as it could not find java). There was possibly a more elegant fix, but this worked for me.

Also for your compatibility guide page, the Deaohk TK300 runs ok on port 2023. But users of this device should note that the documentation is incorrect, and to set a new IP and port for a mapping service, use the command “adminip123456 Ip port”, and NOT “admin123456 ip port”, where 123456 is your password- that threw me for a good hour.

Regards

Eadmund