More information ...
After enable debug mode for netwatch
What can we see when snag is raised :Still don't undestand why for netwatch https-get type the TCP handshake is test ?
It gives a lot a false positive alarm .
Do you think it's a bug or i haven't understood the netwatch https-het function ?
After enable debug mode for netwatch
What can we see when snag is raised :
Code:
2025-02-09T18:29:53.702975+01:00 mikrotik netwatch,info event down [ terra ]2025-02-09T18:29:53.702975+01:00 mikrotik netwatch,debug [b][ terra ] [FAIL] TCP handshake[/b]2025-02-09T18:29:53.702975+01:00 mikrotik netwatch,debug [ OK ] http-resp-time: 3.092ms [ <= 200.000ms ] 2025-02-09T18:29:53.703181+01:00 mikrotik netwatch,debug http-status-code: 2025-02-09T18:29:53.703181+01:00 mikrotik netwatch,debug [ OK ] [ 100 <= ] 200 [ <= 299 ] 2025-02-09T18:29:54.640063+01:00 mikrotik netwatch,debug [ terra ] [FAIL] TCP handshake2025-02-09T18:29:54.640063+01:00 mikrotik netwatch,debug [ OK ] http-resp-time: 2.788ms [ <= 200.000ms ] 2025-02-09T18:29:54.640211+01:00 mikrotik netwatch,debug http-status-code: 2025-02-09T18:29:54.640211+01:00 mikrotik netwatch,debug [ OK ] [ 100 <= ] 200 [ <= 299 ] 2025-02-09T18:30:52.819479+01:00 mikrotik netwatch,info event up [ terra ]2025-02-09T18:30:52.819479+01:00 mikrotik netwatch,debug [ terra ] [ OK ] TCP handshake2025-02-09T18:30:52.819626+01:00 mikrotik netwatch,debug [ OK ] tcp-conn-time: 0.376ms [ <= 8000.000ms ] 2025-02-09T18:30:52.819626+01:00 mikrotik netwatch,debug [ OK ] http-resp-time: 2.915ms [ <= 200.000ms ] 2025-02-09T18:30:52.819771+01:00 mikrotik netwatch,debug http-status-code: 2025-02-09T18:30:52.819771+01:00 mikrotik netwatch,debug [ OK ] [ 100 <= ] 200 [ <= 299 ] It gives a lot a false positive alarm .
Do you think it's a bug or i haven't understood the netwatch https-het function ?
Statistics: Posted by airvb — Sun Feb 09, 2025 7:44 pm