Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

confirm_query needs refactoring #16

Open
cunha opened this issue Feb 7, 2017 · 0 comments
Open

confirm_query needs refactoring #16

cunha opened this issue Feb 7, 2017 · 0 comments

Comments

@cunha
Copy link
Member

cunha commented Feb 7, 2017

There are two issues with struct confirm_query that will make it harder to understand and maintain going forward. These should be easy to fix, so seems worth doing:

  • IPv4 and IPv4 fields should be placed into named structs inside confirm_query. Instead of
	union {
		/* `ip4_id` is not used to identify probes (in
		 * `confirm_query_cmp`) as it is not returned in
		 * `ECHO_REPLY` packets. */
		uint16_t ipid;
		struct {
			uint8_t traffic_class;
			uint32_t flow_label;
		};
	};

We should have something like:

	union {
		/* `ip4_id` is not used to identify probes (in
		 * `confirm_query_cmp`) as it is not returned in
		 * `ECHO_REPLY` packets. */
		struct {
			uint16_t id;
		} ip4;
		struct {
			uint8_t traffic_class;
			uint32_t flow_label;
		} ip6;
	};
  • Another (more subtle) problem is that struct confirm_query stores TCP header fields by name, but stores (what we use to set) the content of ICMP header fields by content (e.g., flowid and revflow). This should be streamlined (without further thinking, it seems we should accept only header fields and let the user use whatever field it wants as the flow identifier. (Note that this would require us to move the reverse flow identifier functionality (revflow) somewhere else.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant