{"action":"opened","issue":{"url":"https://api.github.com/repos/spohara79/estreamer/issues/5","repository_url":"https://api.github.com/repos/spohara79/estreamer","labels_url":"https://api.github.com/repos/spohara79/estreamer/issues/5/labels{/name}","comments_url":"https://api.github.com/repos/spohara79/estreamer/issues/5/comments","events_url":"https://api.github.com/repos/spohara79/estreamer/issues/5/events","html_url":"https://github.com/spohara79/estreamer/issues/5","id":195100761,"number":5,"title":"Endianess flip on EventData parse for uint8[16]","user":{"login":"TeePaps","id":3230497,"avatar_url":"https://avatars.githubusercontent.com/u/3230497?v=3","gravatar_id":"","url":"https://api.github.com/users/TeePaps","html_url":"https://github.com/TeePaps","followers_url":"https://api.github.com/users/TeePaps/followers","following_url":"https://api.github.com/users/TeePaps/following{/other_user}","gists_url":"https://api.github.com/users/TeePaps/gists{/gist_id}","starred_url":"https://api.github.com/users/TeePaps/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/TeePaps/subscriptions","organizations_url":"https://api.github.com/users/TeePaps/orgs","repos_url":"https://api.github.com/users/TeePaps/repos","events_url":"https://api.github.com/users/TeePaps/events{/privacy}","received_events_url":"https://api.github.com/users/TeePaps/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-12T22:12:54Z","updated_at":"2016-12-12T22:12:54Z","closed_at":null,"body":"It seems that the endianess of struct fields with type `uint8[16]` get their endian flipped when they are parsed.\r\n\r\nFor example, `initiator_ip` is of that type. When I manually check the buffer, I get:\r\n`\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\xff\\xff\\xac\\x10\\x0a\\xca`\r\nWhich is an IP address in the form: `::ffff:172.16.10.202`\r\n\r\n\r\nBut the value in the parsed event data field is an integer with this hex representation:\r\n`\\xca\\x0a\\x10\\xac\\xff\\xff\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00\\x00`\r\n\r\nFor other types, like `uint32`, this problem does not occur.\r\n"}}
{"actor":{"display_login":"TeePaps"}}