Wireshark-bugs: [Wireshark-bugs] [Bug 2527] New: Numeric IP addresses not interpreted correctly
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 7 May 2008 13:33:37 -0700 (PDT)
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2527

           Summary: Numeric IP addresses not interpreted correctly
           Product: Wireshark
           Version: 1.0.0
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Minor
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: painter@xxxxxxxxxxxxxxxxxxxxxx


Build Information:
Compiled with GTK+ 2.12.8, with GLib 2.14.6, with WinPcap (version unknown),
with libz 1.2.3, without POSIX capabilities, with libpcre 7.0, with SMI 0.4.5,
with ADNS, with Lua 5.1, with GnuTLS 1.6.1, with Gcrypt 1.2.3, with MIT
Kerberos, with PortAudio V19-devel, with AirPcap.

Running on Windows XP Service Pack 2, build 2600, with WinPcap version 4.0.2
(packet.dll version 4.0.0.1040), based on libpcap version 0.9.5, without
AirPcap.

Built using Microsoft Visual C++ 6.0 build 8804
--
Numeric IP addresses in the Display Filter are not processed correctly.
Entering an address of 10.3 for example will not work.

Apparently, you are not using the standard conversion functions which have been
in existence since the inception of the BSD networking code. These functions
provide a rich format for IP address-compliant input.

These functions are inet_aton() and the functional equivalent inet_addr().

These provide the proper interpretation of each dotted component, allow varying
numeric formats and understand the short forms such as used in 10.3,
10.16000010,  172.16.3824, 172.16.65001, 10.0x3d10b or 0xac.16.5 for example.
It will even allow for the most simplified format of a single hex number such
as 0x7b3d9e13.

So, please use these standard conversion functions and allow us the freedom to
use these powerful and efficient input formats. Obviously the change is trivial
since it means the removal of whatever you do now and replace it with a single
call to inet_aton().

Oh yes, the standard functions will also accept tedious formats such as
10.0.0.3 for those who enjoy wasting their time in typing a lot.

PS. I will report the same bug for the WinPcap capture filter.


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.