ping fail with large packets

Home Page Forums Network Management Signal a BUG ping fail with large packets

This topic contains 1 reply, has 0 voices, and was last updated by  DmitryAkaLBVF 5 years, 9 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #41275

    I’m testing Zeroshell Release 1.0.beta11 and have found the next trouble.
    Ping fails when I’m trying to ping Zeroshell router or any host via Zeroshell router with packets more 1468 bytes.

    C:>ping 10.0.1.2 -f -l 1468
    Pinging 10.0.1.2 with 1468 bytes of data:

    Reply from 10.0.1.2: bytes=1468 time=2ms TTL=63
    Reply from 10.0.1.2: bytes=1468 time=1ms TTL=63
    Reply from 10.0.1.2: bytes=1468 time=1ms TTL=63
    Reply from 10.0.1.2: bytes=1468 time=1ms TTL=63

    Ping statistics for 10.0.1.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms

    C:>ping 10.0.1.2 -f -l 1469
    Pinging 10.0.1.2 with 1469 bytes of data:

    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for 10.0.1.2:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:>ping 10.0.1.2 -f -l 1472

    Pinging 10.0.1.2 with 1472 bytes of data:

    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for 10.0.1.2:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:>ping 10.0.1.2 -f -l 1473

    Pinging 10.0.1.2 with 1473 bytes of data:

    Packet needs to be fragmented but DF set.
    Packet needs to be fragmented but DF set.
    Packet needs to be fragmented but DF set.
    Packet needs to be fragmented but DF set.

    Ping statistics for 10.0.1.2:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    MTU setting on Zeroshell is default – 1500
    I’m runing Zeroshell in VMWare 1.0.6 on Windows Server 2003 Enterprise Edition R2 SP2.

    #47115

    imported_fulvio
    Participant

    Probably the hardware (network cards) are not completely supported.
    Try on other hardware.

    Regards
    Fulvio

    #47116

    smart
    Member

    @dmitryakalbvf wrote:

    I’m testing Zeroshell Release 1.0.beta11 and have found the next trouble.
    Ping fails when I’m trying to ping Zeroshell router or any host via Zeroshell router with packets more 1468 bytes.

    C:>ping 10.0.1.2 -f -l 1468
    Pinging 10.0.1.2 with 1468 bytes of data:

    Reply from 10.0.1.2: bytes=1468 time=2ms TTL=63
    Reply from 10.0.1.2: bytes=1468 time=1ms TTL=63
    Reply from 10.0.1.2: bytes=1468 time=1ms TTL=63
    Reply from 10.0.1.2: bytes=1468 time=1ms TTL=63

    Ping statistics for 10.0.1.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms

    C:>ping 10.0.1.2 -f -l 1469
    Pinging 10.0.1.2 with 1469 bytes of data:

    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for 10.0.1.2:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:>ping 10.0.1.2 -f -l 1472

    Pinging 10.0.1.2 with 1472 bytes of data:

    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for 10.0.1.2:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    C:>ping 10.0.1.2 -f -l 1473

    Pinging 10.0.1.2 with 1473 bytes of data:

    Packet needs to be fragmented but DF set.
    Packet needs to be fragmented but DF set.
    Packet needs to be fragmented but DF set.
    Packet needs to be fragmented but DF set.

    Ping statistics for 10.0.1.2:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    MTU setting on Zeroshell is default – 1500
    I’m runing Zeroshell in VMWare 1.0.6 on Windows Server 2003 Enterprise Edition R2 SP2.

    Yeah ! I too get a same results :

    PING response from the server 10.0.1.2

    Pinging 10.0.1.2 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.
    Ping statistics for 10.0.1.2:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    Request timed out message indicates that you are having connection problem in you network . Try to reset your router and check ping test again . I did this ping test using Whoisxy.com

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.