[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox-cvs
Subject:    [Bug 6932] New: ifconfig fails with Device not found
From:       bugzilla () busybox ! net
Date:       2014-02-26 15:01:43
Message-ID: bug-6932-161 () https ! bugs ! busybox ! net/
[Download RAW message or body]

https://bugs.busybox.net/show_bug.cgi?id=6932

           Summary: ifconfig fails with Device not found
           Product: Busybox
           Version: 1.22.x
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: blocker
          Priority: P5
         Component: Networking
        AssignedTo: unassigned@busybox.net
        ReportedBy: jlaffaye@freebsd.org
                CC: busybox-cvs@busybox.net
   Estimated Hours: 0.0


Created attachment 5258
  --> https://bugs.busybox.net/attachment.cgi?id=5258
patch for ifconfig (interface.c)

#ifconfig -a
ifconfig: : error fetching interface information: Device not found

# uname -r
2.6.30


This is because it tries to parse the following line from /proc/net/dev
"face |  bytes    pckts errs drop fifo frame  comp multi|  bytes    pckts errs
drop fifo coll carr  comp|txpckt rxbyte txbyte|   rx    tx|   rx    tx|rxerr"

I fixed this bug in the attached patch by ignoring empty interface names (the
parser already handle correctly lines without an interface name).

On the other hand, this error should not be fatal, so ifconfig can print other
(valid) interfaces. That's up for discussion.

-- 
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
_______________________________________________
busybox-cvs mailing list
busybox-cvs@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox-cvs
[prev in list] [next in list] [prev in thread] [next in thread]