I'm having trouble with the ifconfig shipped with GNU inetutils 1.8 on
x86-64 linux with glibc 2.11.1. Building and running it (either with or
without -a) only ever gives information for the loopback interface, although
running it in the form 'ifconfig eth0' will correctly give info for the eth0
interface.

I have an older 32-bit linux box here, and when built on that, the inetutils
ifconfig appears to work fine, so I wonder if it could be something x86-64
specific. I see this behaviour on the latest inetutils release (v1.8) but
also on much older versions that I've tried.

I've put a bit of debug code in to try to work out what's going on. If I
instrument if_nameindex() in ifconfig/if_index.c, I find that cur->ifr_name
is (correctly) "lo" for the first interface it finds, but then cur->ifr_name
is empty for the next two and cur->ifr_addr.sa_family doesn't make sense
either, often coming out as 0 instead of the expected 2. Very
puzzling---does anybody have any idea what might be going on here?

Best wishes,

Chris.

Reply via email to