| Bug ID |
11221
|
| Summary |
Cannot re-set manually resolved address
|
| Product |
Wireshark
|
| Version |
1.12.1
|
| Hardware |
x86
|
| OS |
Ubuntu
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
wireshark 1.12.1 (Git Rev Unknown from unknown)
Copyright 1998-2014 Gerald Combs <[email protected]> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Compiled (64-bit) with GTK+ 3.14.9, with Cairo 1.14.0, with Pango 1.36.8, with
GLib 2.43.92, with libpcap, with libz 1.2.8, with POSIX capabilities (Linux),
with libnl 3, with SMI 0.4.8, with c-ares 1.10.0, with Lua 5.2, without Python,
with GnuTLS 3.3.8, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Feb 25 2014 21:09:53), without AirPcap.
Running on Linux 3.19.0-14-generic, with locale en_US.UTF-8, with libpcap
version 1.6.2, with libz 1.2.8, GnuTLS 3.3.8, Gcrypt 1.6.2.
Intel(R) Core(TM) i5-4200M CPU @ 2.50GHz
Built using gcc 4.9.2.
--
Steps to reproduce:
1) Do some analysis in such a way that you have IPs in your host columns.
2) Do a "Manually Resolve Address" operation (I was doing it from the packet
context menu). Let's say we set 1.1.1.1 -> "addr_1".
3) Let's say you have misspelled your value and want "addr_2" value. Try to do
"Manually Resolve Address" operation again. If you set a new mapping (1.1.1.1
-> "addr_2"), the IP 1.1.1.1 is still will be displayed as "addr_1".
I even tried to switch on/off "Enable for Network Layer" option, but no result.
Also I played a bit with it, but a few things are helping, for example saving
pcapng file and then opening it helps, but not every time.
Found in Ubuntu/Gnome, but may be all-platforms bug.
You are receiving this mail because:
- You are watching all bug changes.
