Posts: 53
Threads: 14
Joined: May 2019
Reputation:
0
Using tinypilot as a wifi client. It's software is almost a year old.
Using a microtik access point.
Have all clients set for static ips via dhcp.
tinypilot sets the wrong address often.
Worse yet it changes ip while running sometimes.
Other clients work properly.
One it pi0w with raspbian buster lite.
Anyone having this problem?
Any suggestions.
Posts: 2,179
Threads: 20
Joined: Jun 2016
Reputation:
64
as a client tinypilot is using dhcp so the ip address can change.
I will try to support fixed ip for clients in a future version. For now the easiest solution is to have your access point assign static ip based on mac addresses.
Posts: 53
Threads: 14
Joined: May 2019
Reputation:
0
Got a little more related to this.
Loaded new image of tinypilot.
Very worthwhile.
Still get wrong address sometimes. Logs indicated it being the access point but like to see a dump of the network traffic and that's challenging to do in this environment. Tinypilot is the only client with the problem.
One thing I did find is when tinypilot renews it's dhcp lease it looses networking for a while.
This causes problems.
I changed the lease time to 24 hours, the max I can set from 10 minutes.
At least will have issues less often.
Am using kplex to connect pypilot to my nmea router.
It would loose connection and it would drop out of wind or gps.
Set kplex to persist so hopefully it will continue anyway.
Anyhow I suggest lengthening the lease time on your access point if you use tinypilot as a wifi client.
As I recall others are reporting loosing connections occasionally.
