Ping 回傳值 - wrong data byte #45

上週網路斷線, 第一次看到 ping 回傳這種訊息(wrong data byte #45 should be 0x2d but was 0xd), 完整訊息如下述:

  • $ ping xxx.xxx.xx.xx # ping 掛掉的機器 (固定IP)

    PING xxx.xxx.xx.xxx (xxx.xxx.xx.xxx) 56(84) bytes of data.
    64 bytes from xxx.xxx.xx.xxx (xxx.xxx.xx.xxx): icmp_seq=1 ttl=62 time=13.8 ms
    wrong data byte #45 should be 0x2d but was 0xd
    #16 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c d 2e 2f
    #48 30 31 32 33 34 35 36 37
    64 bytes from xxx.xxx.xx.xxx (xxx.xxx.xx.xxx): icmp_seq=2 ttl=62 time=15.0 ms
    wrong data byte #45 should be 0x2d but was 0xd
    #16 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 26 27 28 29 2a 2b 2c d 2e 2f
    #48 30 31 32 33 34 35 36 37

就 Timeout 和 上述訊息不定時的跳動, 打電話回報後, 中華電信大概花 4hr 修復~ 作個紀錄.

  • 下述摘錄自此網頁: binutils, gcc-4.2, gcc-4.3, gcc-snapshot builds

    Washi keeps losing internet connectivity. It's something to do with the network card. It could either be fried or need reseating. I'm not sure yet. If I run a simple ping to the gateway I get very strange error messages like "wrong data byte #45 should be 0x2d but was 0x2f" and then "Warning: time of day gos back (-1998130us), taking countermeasures". There's most certainly some serious corruption going on.


關於 Tsung

對新奇的事物都很有興趣, 喜歡簡單的東西, 過簡單的生活.
本篇發表於 My_Note 並標籤為 , 。將永久鏈結加入書籤。

發表迴響