-
Notifications
You must be signed in to change notification settings - Fork 510
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
changing internal representation of ip addresses from string to binary
as stated. currently katran is exposed to capslock like issues. e.g. we could add same v6 address multiple times and that would pass all the tests (e.g. real fc00::1 fc00:0::1 fc00:0:0::1 etc). current behavior wont break anything, as in forwarding plane everything is in binary anyway, but we would consume more resources than needed. (e.g. real for regular vip could in any format, but quic's real in exploded) tested by: - it compiles (c) - unittests - katran_tester --- 1. this is taking care only about real's addresses, struct VipKey still has vip's address as a string. so it would take more work to modify that as well (as VipKey is a public API. current changes wont break anything external as API's return values have not changed. only internal's ones) 2. if i run clang-format on KatranLb.h/cpp it makes some changes in unrelated lines (most likely either format from 8.0 has some modifications or it was not run on that files for a while). what would you prefer? would you accept diff w/ some unrelated changed caused by clang format?
- Loading branch information
Showing
7 changed files
with
106 additions
and
64 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.