Alessandro Boch e415b1f495 Do not use 4 byte ip addresses in encryption code ... - Because of a bug in the netlink xfrm code, our code will fail to find and remove the states. While we could wait for the netlink library fix, there is no longer a need to convert the parsed IP addresses to the canonical notation given the previous SPI computation (which worked on that 4 byte address assumption) is now replaced by the fnv hash. - Also modify driver option that enables ipsec to "encrypted" Signed-off-by: Alessandro Boch <aboch@docker.com>		2016-07-23 19:00:47 -07:00
..
ovmanager	ovmanager: Error out on vxlan id alloc failure	2016-06-28 13:46:22 -07:00
encryption.go	Do not use 4 byte ip addresses in encryption code	2016-07-23 19:00:47 -07:00
filter.go	Overlay driver to check for chain presence	2016-04-13 10:47:42 -07:00
joinleave.go	Merge pull request #1337 from mavenugo/adv-addr	2016-07-21 09:51:51 -07:00
ov_endpoint.go	Persist and restore overlay endpoints to handle daemon restart	2016-06-13 23:48:00 -07:00
ov_network.go	Do not use 4 byte ip addresses in encryption code	2016-07-23 19:00:47 -07:00
ov_serf.go	Adding Advertise-addr support	2016-07-21 02:44:25 -07:00
ov_utils.go	Gracefully handle missing xfrm modules	2016-06-20 17:25:32 -07:00
overlay.go	Do not use 4 byte ip addresses in encryption code	2016-07-23 19:00:47 -07:00
overlay.pb.go	Convert overlay peer updates to use protobuf	2016-05-18 20:44:50 -07:00
overlay.proto	Convert overlay peer updates to use protobuf	2016-05-18 20:44:50 -07:00
overlay_test.go	Add libnetwork agent mode support	2016-05-02 18:19:32 -07:00
peerdb.go	Persist and restore overlay endpoints to handle daemon restart	2016-06-13 23:48:00 -07:00