| Bug ID |
10836
|
| Summary |
e212.mcc / e212.mnc filter for both ULI and RAI
|
| Product |
Wireshark
|
| Version |
unspecified
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Enhancement
|
| Priority |
Low
|
| Component |
GTK+ UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Created attachment 13373 [details]
Screenshot
Build Information:
C:\TEMP\Wireshark>
wireshark 1.10.7 (v1.10.7-0-g6b931a1 from master-1.10)
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+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, with
GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5, without POSIX capabilities,
without libnl, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.1, without Python,
with GnuTLS 2.12.18, with Gcrypt 1.4.6, without Kerberos, with GeoIP, with
PortAudio V19-devel (built Apr 22 2014), with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM) i3-4030U CPU @ 1.90GHz, with 8088MB of physical memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
Good day kind sirs!
My remark is concerning the GTP protocol which contains a RAI (Routing Area
Identifier) parameter and also a ULI (User Location Information) parameter.
The filter for both values is the same "e212.mcc" and "e212.mnc". In some cases
the RAI and ULI fields contain different data but since both use the "e212.mcc"
and "e212.mnc" filter it is not possible to differentiate between ULI and RAI
while filtering.
A separate filter for ULI and RAI would be advantageous.
Kind regards and a happy new year!
You are receiving this mail because:
- You are watching all bug changes.