Hi,
anyone who can help with this ADwin frame ? (Especially the Gateway IP)
ADwin configuration protocol
ADwin Debug information
Unused
Unused
Pattern: Unknown (0x6e4c9d8c)
Version: 1087455434
Status: 0x3d2d682c, Status Configurable, Status Bootloader boots, Status Bootloader receive
.... .... .... .... .... .... .... ...0 = Status Bootloader: False
.... .... .... .... .... .... .... ..0. = Status Reprogrammable: False
.... .... .... .... .... .... .... .1.. = Status Configurable: True
.... .... .... .... .... .... .... 1... = Status Bootloader boots: True
.... .... .... .... .... .... ...0 .... = Status Bootloader reprogrammable: False
.... .... .... .... .... .... ..1. .... = Status Bootloader receive: True
.... .... .... .... .... .... .0.. .... = Status Bootloader reprogramming done: False
.... .... .... .... .... .... 0... .... = Status EEPROM Support: False
server version (beta part): 230 Server version: 51930 XILINX Version: 0x8adac926 MAC address: 05:a4:25:f8:6e:3e (05:a4:25:f8:6e:3e) Port (16bit): 41662 DHCP enabled: True Netmask count: 237 Gateway IP: 110.46.141.140 Reply with broadcast: True Scan ID: 0x68437261
Many thanks
Erwin
asked 22 Jan '17, 05:40
Erwin R
6●1●1●2
accept rate: 0%
edited 22 Jan '17, 09:12
Jaap ♦
11.7k●16●101
"help me with this frame" is not really a question... what do you want to ask precisely?
Jasper,
thank you for your interest in my request for help. As asked precisely , let us start with the meaning of the "Gateway IP: 110.46.141.140" . Locating that IP learned me that this a host based in Hong Kong. To continue : what is the purpose of sending this frame in general. I assume this frame has some sense . Next, I would like to know the meaning of "MAC address: 05:a4:25:f8:6e:3e (05:a4:25:f8:6e:3e)" . What could possibly be the host ?
I want to know why my Android device is putting this frame on the wire(less).
I know 0 about "Adwin Config". Googling for more human readable information did not help me any further.
I am looking for some general explanation, probably to fire my next questions for help.
Kind regards
Erwin
Are you sure, that this is really an Adwind Frame?
Each TCP or UDP packet has a source and a destination port. If a UDP packet has a source port of 123 and a destination port of 53 Wireshark would not know, if it is NTP or DNS. The Decode-As Context menu helps.
And, thank you for asking, the afford-mentioned port combination should not be seen on the wire, but is send by a bunch of cable modems anyway.
Can you upload the tracefile for us?