android_external_android-clat/config.c, branch replicant-6.0-0003 Unnamed repository; edit this file 'description' to name the repository. Process packets in bursts. 2016-06-09T04:15:23+00:00 Lorenzo Colitti lorenzo@google.com 2015-09-25T16:27:34+00:00 bee83f8d7edb48a1d8b8f2333a1b259854c44b95 Add a "packet_burst" config option that will cause clatd to read (and write) in bursts of up to that number of packets, instead of always only reading one packet at a time. This reduces poll overhead and improves performance. The variable is initially set to 10. Bug: 24113287 Change-Id: I7feba4127538c5a89f92e0ebea1fb75971d6b901 
Add a "packet_burst" config option that will cause clatd to read
(and write) in bursts of up to that number of packets, instead of
always only reading one packet at a time. This reduces poll
overhead and improves performance.

The variable is initially set to 10.

Bug: 24113287
Change-Id: I7feba4127538c5a89f92e0ebea1fb75971d6b901
Never use a statically-configured IID on wifi. 2014-11-11T02:06:44+00:00 Lorenzo Colitti lorenzo@google.com 2014-11-11T01:00:02+00:00 2596f42a4f4c42bfb96ccbfc2700dbf70502ec75 Bug: 12111730 Change-Id: I062d81f2b65e6e89baae0f840cbd673f8051d523 
Bug: 12111730
Change-Id: I062d81f2b65e6e89baae0f840cbd673f8051d523
Use different IPv4 addresses on different clat interfaces. 2014-10-31T16:17:22+00:00 Lorenzo Colitti lorenzo@google.com 2014-10-31T12:54:33+00:00 798f9934fca523dfb57136bd185cf6e9460323ad Previously the code would use 192.0.0.4 on all clat interfaces. This works, but it has the problem when a clat interface goes down, we do not reset TCP connections on its IP address if there is another clat interface up. Fix this by assigning every clat interface its own IP address in 192.0.0.0/29. Bug: 12111730 Change-Id: I28c831acd93b0980efea8e90c1cdf8b607beac68 
Previously the code would use 192.0.0.4 on all clat interfaces.
This works, but it has the problem when a clat interface goes
down, we do not reset TCP connections on its IP address if there
is another clat interface up.

Fix this by assigning every clat interface its own IP address in
192.0.0.0/29.

Bug: 12111730
Change-Id: I28c831acd93b0980efea8e90c1cdf8b607beac68
Unduplicate IPv6 address setting code. 2014-10-29T02:53:05+00:00 Lorenzo Colitti lorenzo@google.com 2014-10-21T04:41:21+00:00 1352a3a26c4d7c32b38b7fadb837799a23014aa6 Currently, the IPv6 address gets set in two different codepaths depending on whether it's being configured on startup or happens because the interface changed its prefix. Refactor the two into a common function. Change-Id: I37035401bef7a57ff40540bd0f2aed0f6863269d 
Currently, the IPv6 address gets set in two different codepaths
depending on whether it's being configured on startup or happens
because the interface changed its prefix. Refactor the two into
a common function.

Change-Id: I37035401bef7a57ff40540bd0f2aed0f6863269d
Generate a random IID if one is not specified. 2014-10-28T06:30:45+00:00 Lorenzo Colitti lorenzo@google.com 2014-10-09T13:29:45+00:00 9808952bdf2fa6ce4cbd790d1967691bb95bf327 - Add code to generate a random IPv6 address that's checksum-neutral with the NAT64 prefix and clat IPv4 address. - Only calculate the IP address after the NAT64 prefix is known. - Because the clat IPv6 address is no longer determinisitic, modify interface_poll so it checks whether the prefix has changed instead of checking whether the IPv6 address has changed. - Add/update unit tests. Change-Id: Ia53716ca5315ebdd0eaa3ad3a07552bf18e9dd5c 
- Add code to generate a random IPv6 address that's
  checksum-neutral with the NAT64 prefix and clat IPv4 address.
- Only calculate the IP address after the NAT64 prefix is known.
- Because the clat IPv6 address is no longer determinisitic,
  modify interface_poll so it checks whether the prefix has
  changed instead of checking whether the IPv6 address has
  changed.
- Add/update unit tests.

Change-Id: Ia53716ca5315ebdd0eaa3ad3a07552bf18e9dd5c
Cleanup: Remove unused "ipv6_local_address". 2014-10-27T19:28:11+00:00 Sreeram Ramachandran sreeram@google.com 2014-10-23T16:38:19+00:00 74151e9d0cda83f77d9dbce62bf8a1340cb08386 This was originally used on the "clat" interface. That interface is not created anymore (since the switch to using a raw socket). Note that the v6 address used on the raw socket is a combination of the plat subnet plus a host ID, and not this link-local address. Also fixup default values to match clatd.conf values. Change-Id: I3470a02e6798b65cae0f8d7f074ce51fb0647e6a 
This was originally used on the "clat" interface. That interface is not created
anymore (since the switch to using a raw socket). Note that the v6 address used
on the raw socket is a combination of the plat subnet plus a host ID, and not
this link-local address.

Also fixup default values to match clatd.conf values.

Change-Id: I3470a02e6798b65cae0f8d7f074ce51fb0647e6a
Simplify and always retry DNS64 prefix discovery. 2014-09-24T07:02:31+00:00 Erik Kline ek@google.com 2014-09-22T04:32:27+00:00 0ec5dfa1da6a97532dc8cca825bae4edfb7d3dce - Only request AAAAs for the IPv4-only hostname, since that's all the information being used. Perhaps at some point in the future when _validation_ of the IPv4 address(es)'s presence within the IPv6 address(es) is being done this should be revisited. - Only use the first AAAA returned to find the DNS64 prefix. It's not clear how to properly resolve any potential DNS64 prefix conflicts anyway. - Re-try DNS64 prefix discovery on any type of error. If clatd was started (presumably an IPv6-only network), retry DNS64 prefix discovery with exponential backoff. Some "permanent" errors can be indistinguishable from transient errors (e.g. receiving an erroneous SERVFAIL from a DNS resolver, ...). - Fix-up back-off logic to not sleep 128 then 120, 120, ... :-) Bug: 17569702 Change-Id: I226ea7772cd7c88d2b60153ef76e5435400e11aa 
  - Only request AAAAs for the IPv4-only hostname, since that's
    all the information being used.  Perhaps at some point in the
    future when _validation_ of the IPv4 address(es)'s presence
    within the IPv6 address(es) is being done this should be
    revisited.

  - Only use the first AAAA returned to find the DNS64 prefix.
    It's not clear how to properly resolve any potential DNS64
    prefix conflicts anyway.

  - Re-try DNS64 prefix discovery on any type of error.
    If clatd was started (presumably an IPv6-only network), retry
    DNS64 prefix discovery with exponential backoff.  Some
    "permanent" errors can be indistinguishable from transient
    errors (e.g. receiving an erroneous SERVFAIL from a DNS
    resolver, ...).

  - Fix-up back-off logic to not sleep 128 then 120, 120, ...
    :-)

Bug: 17569702
Change-Id: I226ea7772cd7c88d2b60153ef76e5435400e11aa
Use a packet socket to receive packets. 2014-06-11T03:42:20+00:00 Lorenzo Colitti lorenzo@google.com 2014-06-03T03:56:38+00:00 d44fac888a441cf21111358f43384f3942399d5d Combined with the previous change to send on a raw socket instead of a tunnel interface, this allows us to get rid of the clat interface and remove all the routing configuration code. Bug: 15340961 Change-Id: I9d9b90f9b4f58dcc3c102abcdc32a2c7ee86b01d 
Combined with the previous change to send on a raw socket
instead of a tunnel interface, this allows us to get rid of the
clat interface and remove all the routing configuration code.

Bug: 15340961
Change-Id: I9d9b90f9b4f58dcc3c102abcdc32a2c7ee86b01d
Make DNS request for plat prefix detection network specific. 2014-06-02T14:38:30+00:00 Paul Jensen pauljensen@google.com 2014-05-30T17:19:10+00:00 a1c871c8efad6c0b69e27d3b85e82a27e282b8be When plat prefix detection is done on a non-default network it must use the network specific version of getaddrinfo() so the plat prefix corresponds to the particular network. The network is specified to clatd via a NetID command line argument. Change-Id: I77a47b24e68c7786f790974f05787a40a4934af5 
When plat prefix detection is done on a non-default network it
must use the network specific version of getaddrinfo() so the
plat prefix corresponds to the particular network.  The network
is specified to clatd via a NetID command line argument.

Change-Id: I77a47b24e68c7786f790974f05787a40a4934af5
Remove unused variables 2014-01-02T23:58:14+00:00 Bernhard Rosenkränzer Bernhard.Rosenkranzer@linaro.org 2013-12-12T09:28:16+00:00 a33592bd08a20c6a521b8508975b7a74ecdf4f03 Remove unused variables -- they cause warnings (and errors with -Werror) when building with clang 3.4. Change-Id: I03fff9b1b9d620763f41c8b31a19c4724726739c Signed-off-by: Bernhard Rosenkränzer <Bernhard.Rosenkranzer@linaro.org> 
Remove unused variables -- they cause warnings (and errors with
-Werror) when building with clang 3.4.

Change-Id: I03fff9b1b9d620763f41c8b31a19c4724726739c
Signed-off-by: Bernhard Rosenkränzer <Bernhard.Rosenkranzer@linaro.org>