May-6th-2019, 03:01 PM
Hey Armin,
unfortunately I must bother you again.
We've tested the new Image in our test-field and I've got the response that it could not get pinged.
Therefore, I've build up a testing environment myself and got the following result:
As you can see, every ~ fourth ping gets timed out. When I use the same setup and configuration for netPi's standard ethernet-Port, the pinging works just fine.
Do you have any idea where this behaviour could come from or where the packages could get lost?
Thanks,
Andi
unfortunately I must bother you again.
We've tested the new Image in our test-field and I've got the response that it could not get pinged.
Therefore, I've build up a testing environment myself and got the following result:
Code:
Ping wird ausgeführt für 172.16.8.202 mit 32 Bytes Daten:
Antwort von 172.16.8.202: Bytes=32 Zeit=1ms TTL=63
Zeitüberschreitung der Anforderung.
Antwort von 172.16.8.202: Bytes=32 Zeit=1ms TTL=63
Antwort von 172.16.8.202: Bytes=32 Zeit=1ms TTL=63
Ping-Statistik für 172.16.8.202:
Pakete: Gesendet = 4, Empfangen = 3, Verloren = 1
(25% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 1ms, Maximum = 1ms, Mittelwert = 1ms
C:\Windows>ping 172.16.8.202
Ping wird ausgeführt für 172.16.8.202 mit 32 Bytes Daten:
Antwort von 172.16.8.202: Bytes=32 Zeit=1ms TTL=63
Antwort von 172.16.8.202: Bytes=32 Zeit=1ms TTL=63
Antwort von 172.16.8.202: Bytes=32 Zeit=1ms TTL=63
Antwort von 172.16.8.202: Bytes=32 Zeit=2ms TTL=63
Ping-Statistik für 172.16.8.202:
Pakete: Gesendet = 4, Empfangen = 4, Verloren = 0
(0% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 1ms, Maximum = 2ms, Mittelwert = 1ms
C:\Windows>ping 172.16.8.202
Ping wird ausgeführt für 172.16.8.202 mit 32 Bytes Daten:
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Antwort von 172.16.8.202: Bytes=32 Zeit=1ms TTL=63
Antwort von 172.16.8.202: Bytes=32 Zeit=1ms TTL=63
Ping-Statistik für 172.16.8.202:
Pakete: Gesendet = 4, Empfangen = 2, Verloren = 2
(50% Verlust),
Ca. Zeitangaben in Millisek.:
Minimum = 1ms, Maximum = 1ms, Mittelwert = 1ms
As you can see, every ~ fourth ping gets timed out. When I use the same setup and configuration for netPi's standard ethernet-Port, the pinging works just fine.
Do you have any idea where this behaviour could come from or where the packages could get lost?
Thanks,
Andi