{"action":"opened","issue":{"url":"https://api.github.com/repos/GlobalNOC/FlowSpaceFirewall/issues/115","labels_url":"https://api.github.com/repos/GlobalNOC/FlowSpaceFirewall/issues/115/labels{/name}","comments_url":"https://api.github.com/repos/GlobalNOC/FlowSpaceFirewall/issues/115/comments","events_url":"https://api.github.com/repos/GlobalNOC/FlowSpaceFirewall/issues/115/events","html_url":"https://github.com/GlobalNOC/FlowSpaceFirewall/issues/115","id":74122742,"number":115,"title":"OFQueueGetRequest messages not handled properly","user":{"login":"gth828r","id":385222,"avatar_url":"https://avatars.githubusercontent.com/u/385222?v=3","gravatar_id":"","url":"https://api.github.com/users/gth828r","html_url":"https://github.com/gth828r","followers_url":"https://api.github.com/users/gth828r/followers","following_url":"https://api.github.com/users/gth828r/following{/other_user}","gists_url":"https://api.github.com/users/gth828r/gists{/gist_id}","starred_url":"https://api.github.com/users/gth828r/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gth828r/subscriptions","organizations_url":"https://api.github.com/users/gth828r/orgs","repos_url":"https://api.github.com/users/gth828r/repos","events_url":"https://api.github.com/users/gth828r/events{/privacy}","received_events_url":"https://api.github.com/users/gth828r/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-05-07T20:45:54Z","updated_at":"2015-05-07T20:45:54Z","closed_at":null,"body":"Looking at the code, it appears that ofp_queue_get_config_requests get handled in `OFControllerChannelHandler.java` by the method `processOFQueueGetRequest`.  I see two issues with the handler:\r\n * `ofp_queue_get_config_request`  are responded to with `ofp_get_config_reply` instead of `ofp_queue_get_config_reply`\r\n * The reply is not using the same XID as the request\r\n\r\nI am seeing this in the 1.0.5-dev branch.  This is non-critical for GENI, because we haven't exposed queues to our experimenters.\r\n\r\nThe main issue is that the response will violate the principle of least surprise if someone does send a queue get config message, and it will interact poorly with some OF libraries that handle symmetric messages by keying off of the XID."}}