ping result with lots of (DUP!)



  • i manage to get the wireless working, but with the abovementioned issue. follows is the captured console text

    BusyBox v1.26.2 () built-in shell (ash)


    / __ ___ ()_ ___ / __ __ _ ___ ___ ____ _
    / // / _ / / _ / _ \ / // / ' / -) _ / _/
    _
    /////_//// _////_/_, /_,/
    W H A T W I L L Y O U I N V E N T ? /
    __/

    Ω-ware: 0.1.9 b159

    root@Omega-C105:/# ping google.com
    PING google.com (216.58.203.78): 56 data bytes
    64 bytes from 216.58.203.78: seq=0 ttl=55 time=36.340 ms
    64 bytes from 216.58.203.78: seq=0 ttl=55 time=43.622 ms (DUP!)
    64 bytes from 216.58.203.78: seq=0 ttl=55 time=57.795 ms (DUP!)
    64 bytes from 216.58.203.78: seq=0 ttl=55 time=63.237 ms (DUP!)
    64 bytes from 216.58.203.78: seq=1 ttl=55 time=48.618 ms
    64 bytes from 216.58.203.78: seq=1 ttl=55 time=60.106 ms (DUP!)
    64 bytes from 216.58.203.78: seq=2 ttl=55 time=26.864 ms
    64 bytes from 216.58.203.78: seq=3 ttl=55 time=45.031 ms
    64 bytes from 216.58.203.78: seq=3 ttl=55 time=48.404 ms (DUP!)
    64 bytes from 216.58.203.78: seq=3 ttl=55 time=61.614 ms (DUP!)
    64 bytes from 216.58.203.78: seq=3 ttl=55 time=76.493 ms (DUP!)
    64 bytes from 216.58.203.78: seq=3 ttl=55 time=88.581 ms (DUP!)
    64 bytes from 216.58.203.78: seq=3 ttl=55 time=102.957 ms (DUP!)
    64 bytes from 216.58.203.78: seq=3 ttl=55 time=113.015 ms (DUP!)
    64 bytes from 216.58.203.78: seq=3 ttl=55 time=118.433 ms (DUP!)
    64 bytes from 216.58.203.78: seq=3 ttl=55 time=121.935 ms (DUP!)
    ^C
    --- google.com ping statistics ---
    4 packets transmitted, 4 packets received, 12 duplicates, 0% packet loss
    round-trip min/avg/max = 26.864/69.565/121.935 ms



  • it's difficult to say exactly why the packets are getting duplicated. However, one of the reasons could be that Omega AP has the same IP range as the router (ifconfig should tell you if this is the case).

    Might be also worth connecting to your router with another device and pinging the same host to ensure that the router is not at fault.


Log in to reply
 

Looks like your connection to Onion Community was lost, please wait while we try to reconnect.