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  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 24 Sep 2008 13:31:32 +0300 (EEST)
From:	Pekka Savola <>
Subject: /proc/net/igmp group address encoding


I've spotted some irritating IGMPv3/v2 compat problems on RHEL4, and 
I'm working on trying to see if these are due to bugs already fixed in 
latest kernels.  In the process, I started wondering about 
/proc/net/igmp format (on

[ ~]$ more /proc/net/igmp
Idx	Device    : Count Querier	Group    Users Timer	Reporter
1	lo        :     0      V3
 				010000E0     1 0:00000000		0
2	eth0      :     2      V3
 				010000E0     1 0:00000000		0
3	wmaster0  :     3      V3
 				010000E0     1 0:00000000		0
4	wlan0     :     3      V3
 				010000E0     1 0:00000000		0

(The header and the fields seem to be a little off in the output..)

[ ~]$ netstat -gn | grep eth0
eth0            1
eth0            1      ff02::1

It appears "010000E0" is encoded in in hex but 
right-to-left.  Other groups are similarly encoded.  /proc/net/igmp6 
is encoded in a human-friendly format.

Is this intentional?  Should this be changed, e.g. to flow 
left-to-right and use the dotted quad IP address format?

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
More majordomo info at

Powered by blists - more mailing lists