netdev - Re: broken link-local multicast?

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LRH.1.00.0802150928020.3621@netcore.fi>
Date:	Fri, 15 Feb 2008 09:31:00 +0200 (EET)
From:	Pekka Savola <pekkas@...core.fi>
To:	md@...ux.it, netdev@...r.kernel.org
Subject: Re: broken link-local multicast?

On Thu, 14 Feb 2008, Marco d'Itri wrote:
> Does anybody have any idea about how to debug this?
>
> root@...l-5a:~# ping6 -c 1 -I eth1 ff02::1
> connect: Network is unreachable

Maybe 'netstat -gn' could give clues, because you should be receiving 
a response at least from the loopback address.  Maybe your loopback 
interface has went down, or ospf6d took it down and back up (at least 
some time ago, kernel's v6 got very confused after that).

You may also want to check out that your link-local address on the 
interface you're pinging is still OK.

# netstat -gn | grep ff02
lo              1      ff02::1
eth0            2      ff02::1:ff7b:259
eth0            1      ff02::1

# ping6 -c 1 -I eth0 ff02::1
PING ff02::1(ff02::1) from fe80::207:e9ff:fe7b:259 eth0: 56 data bytes
64 bytes from ::1: icmp_seq=0 ttl=64 time=0.057 ms

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html