Bug ID |
11495
|
Summary |
IPv4 Adress is backwards
|
Product |
Wireshark
|
Version |
1.99.x (Experimental)
|
Hardware |
x86
|
OS |
Red Hat
|
Status |
UNCONFIRMED
|
Severity |
Minor
|
Priority |
Low
|
Component |
TShark
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Created attachment 13845 [details]
Look at the SETCLIENTID
Build Information:
jhereg:wireshark loghyr$ ./tshark -v
TShark (Wireshark) 1.99.0 (194a4a6 from master)
--
Look at the SETCLIENTID:
Network File System, Ops(1): SETCLIENTID
[Program Version: 4]
[V4 Procedure: COMPOUND (1)]
Tag: <EMPTY>
length: 0
contents: <EMPTY>
minorversion: 0
Operations (count: 1): SETCLIENTID
Opcode: SETCLIENTID (35)
client
verifier: 0x55e3248831560ed6
id: <DATA>
length: 41
contents: <DATA>
fill bytes: opaque data
callback
cb_program: 0x40000000
cb_location
r_netid: tcp
length: 3
contents: tcp
fill bytes: opaque data
r_addr: 192.168.29.21.218.35
length: 20
contents: 192.168.29.21.218.35
[IPv4 address 21.29.168.192, protocol=tcp, port=55843]
^^^^^^^^^^^^^^
callback_ident: 0x00000001
You are receiving this mail because:
- You are watching all bug changes.