FYI: I’ve just found this bug while porting the ‘re serve’ to ‘can log … tcpserver’. It seems we are binding to :3000 (or wherever) when we start, but not unbinding (closing the socket) when we stop. That means starting then stopping leaves the port in a weird state (where we can see a connection, but not accept it). Also can’t start, stop, start properly. I’ll commit the fix in the next hour or so. Regards, Mark
On 19 Jan 2019, at 9:34 PM, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Should not be.
Are you sure the ‘re’ is running?
Regards, Mark.
On 19 Jan 2019, at 9:32 PM, Michael Eric Menk <mikeemenk@gmail.com <mailto:mikeemenk@gmail.com>> wrote:
On 19.01.2019 14:22, Tamás Kovács wrote:
Then, on workstation:
- nc 192.168.4.1 3000 | tee log.crtd
And the send me the log.crtd file.
Is the OVMS firewalled if it's connected as a WIFI client?
nmap -P0 -p 3000 192.168.1.84
Starting Nmap 7.60 ( https://nmap.org <https://nmap.org/> ) at 2019-01-19 14:31 CET Nmap scan report for 192.168.1.84 Host is up.
PORT STATE SERVICE 3000/tcp filtered ppp
Nmap done: 1 IP address (1 host up) scanned in 2.12 seconds
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev