Matti Aarnio [EMAIL PROTECTED] writes:
.. the original reason was apparently that _ifconfig_ blew up
when it saw protocols that it didn't understand on network
interfaces. Possibly when there was no IP protocol on an
interface.
It's not only ifconfig, a lot of programs use SIOCGIFCONF
to
.. the original reason was apparently that _ifconfig_ blew up
when it saw protocols that it didn't understand on network
interfaces. Possibly when there was no IP protocol on an
interface.
This happened on DECNET, and apparently on others too.
Thus the SIOCGIFCONF ioctl is not returning much
On Mon, Feb 04, 2008 at 03:38:35PM +0100, Andi Kleen wrote:
Matti Aarnio [EMAIL PROTECTED] writes:
.. the original reason was apparently that _ifconfig_ blew up
when it saw protocols that it didn't understand on network
interfaces. Possibly when there was no IP protocol on an