netdev - Re: iproute2 neighboring

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

Message-ID: <CAGXs5wW_5M4cZQdZoCUgGTTOW5ZEhpWY2p235dBbk_SF1BznfQ@mail.gmail.com>
Date:	Fri, 4 Nov 2011 21:27:39 +0200
From:	Kevin Wilson <wkevils@...il.com>
To:	François-Xavier Le Bail <fx.lebail@...oo.com>
Cc:	David Stevens <dlstevens@...ibm.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"netdev-owner@...r.kernel.org" <netdev-owner@...r.kernel.org>
Subject: Re: iproute2 neighboring

Hi,
Thanks all responses!
The answer that there is a fixed mapping in case of multicast is reasonable,
and I assume this is the reason for not seeing multicast addresses in
neigh table.
>You can also see group memberships with "ip m".
I wonder whether I can know from "ip -m" which multicast addresses
are attached to which ip addresses.
For example,
"ip -m" shows:
2:	em1
...     ip1
...     ip2
...     ip3
	inet  224.0.0.1
	inet6 ff02::1:ffcf:c821
	inet6 ff02::1

is the order important here?
namely, is  ip1 belongs to  224.0.0.1,
ip2 belongs to ff02::1:ffcf:c821, and ip3 belong to ff02::1?

rgs,
Kevin


2011/11/4 François-Xavier Le Bail <fx.lebail@...oo.com>:
>
>
>
>
> ----- Original Message -----
>> From: David Stevens <dlstevens@...ibm.com>
>> To: Kevin Wilson <wkevils@...il.com>
>> Cc: netdev@...r.kernel.org; netdev-owner@...r.kernel.org
>> Sent: Friday, November 4, 2011 4:46 PM
>> Subject: Re: iproute2 neighboring
>>
>>>  From: Kevin Wilson <wkevils@...il.com>
>>
>>>  Hi,
>>>  It seems to me that "ip -6 neigh show" does not show multicast
>> entries
>> from
>>>  IPv6 neighboring  table. Is there a reason for this ?
>>
>> Multicast memberships aren't in the neighbor table. The
>> neighbor table is for translating protocol addresses to
>> MAC addresses and that translation is fixed for multicast
>> destinations.
>>
>> You can see group memberships with "netstat -g". There are also
>> some data in /proc/net/{dev_mcast,igmp6,mcfilter6} depending on
>> what you're looking for.
>>
>>                                                 +-DLS
>
> Hi,
>
> You can also see group memberships with "ip m".
>
> François-Xavier
>
>
--
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