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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 16 Oct 2007 12:46:00 -0700
From:	David Stevens <dlstevens@...ibm.com>
To:	"Joakim Tjernlund" <joakim.tjernlund@...nsmode.se>
Cc:	"'Netdev'" <netdev@...r.kernel.org>, netdev-owner@...r.kernel.org
Subject: RE: Multicast problem

> dev_mcast and igmp looks:
> root@...llenger:/proc/net# m dev_mcast
> 1    eth0            1     0     01005e000001
> 2    eth1            1     0     01005e000001

        These are the hardware multicast addresses for
224.0.0.1 (so, correct).

> root@...llenger:/proc/net# m igmp
> Idx     Device    : Count Querier       Group    Users Timer    Reporter
> 1       eth0      :     1      V3
>                                 E0000001     1 0:00000000 0
> 2       eth1      :     1      V2
>                                 E0000001     1 0:00000000 0
> 4       lo        :     0      V3
>                                 E0000001     1 0:00000000 0

        ...and these are the group memberships for 224.0.0.1, so
also correct. This should receive and answer pings to 224.0.0.1
as long as you don't have ICMP set to ignore broadcasts. You should
not need to put the device in promiscuous mode for a ping of
224.0.0.1 to work, so if you do, then you have a driver, device
or switch problem.
        None of these interfaces have memberships in the OSPF groups,
so if you had OSPF running when you did this, it didn't join.

                                                        +-DLS

-
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ