lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <464e900f-c256-4d22-6a83-a3aea0fca8bc@mellanox.com>
Date:   Mon, 28 Aug 2017 17:48:49 +0300
From:   Tariq Toukan <tariqt@...lanox.com>
To:     Linux Kernel Network Developers <netdev@...r.kernel.org>,
        David Miller <davem@...emloft.net>,
        Alexey Kuznetsov <kuznet@....inr.ac.ru>,
        Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>
Cc:     ranro@...lanox.com, guye@...lanox.com,
        Eran Ben Elisha <eranbe@...lanox.com>
Subject: IPv6 loopback issue report

Hi all,

We encountered the following issue in our regression tests over net-next 
branch.
IPv6 loopback ping fails, while it works for IPv4.

Reproduces with all NICs, doesn't seem to be a driver issue.

Example:

# ifconfig ens8
ens8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         inet 11.141.16.6  netmask 255.255.0.0  broadcast 11.141.255.255
         inet6 fe80::7efe:90ff:fecb:7502  prefixlen 64  scopeid 0x20<link>
         ether 7c:fe:90:cb:75:02  txqueuelen 1000  (Ethernet)
         RX packets 12  bytes 1164 (1.1 KiB)
         RX errors 0  dropped 0  overruns 0  frame 0
         TX packets 30  bytes 2484 (2.4 KiB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

# ping -c 3 11.141.16.6
PING 11.141.16.6 (11.141.16.6) 56(84) bytes of data.
64 bytes from 11.141.16.6: icmp_seq=1 ttl=64 time=0.017 ms
64 bytes from 11.141.16.6: icmp_seq=2 ttl=64 time=0.014 ms
64 bytes from 11.141.16.6: icmp_seq=3 ttl=64 time=0.014 ms

--- 11.141.16.6 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2025ms
rtt min/avg/max/mdev = 0.014/0.015/0.017/0.001 ms

#  /bin/ping6 -c 3 fe80::7efe:90ff:fecb:7502%ens8
PING fe80::7efe:90ff:fecb:7502%ens8(fe80::7efe:90ff:fecb:7502) 56 data bytes

--- fe80::7efe:90ff:fecb:7502%ens8 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2043ms

Regards,
Tariq Toukan

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ