summaryrefslogtreecommitdiff
path: root/Tethering/src/android/net/ip/IpServer.java
Commit message (Collapse)AuthorAgeFilesLines
* Add config_p2p_leases_subnet_prefix_length configurationmarkchien2022-03-311-1/+7
| | | | | | | | | | | | | | | | Add new rro configuration which can be used to make the p2p dhcp prefix length larger to reserve the address range outside of leases subnet prefix length for EAPOL-Key feature. This configuration only valid if its value larger than dhcp server address prefix length and config_tether_enable_legacy_wifi_p2p_dedicated_ip is true. E.g.:leaseSubnetPrefixLength = 25, p2p static address = 192.168.49.1/24 dhcp range: 192.168.49.0 ~ 192.168.49.127 (192.168.49.1/25), reserved 192.168.49.128 ~ 192.168.49.255 for EAPOL-Key feature. Bug: 170056953 Test: atest TetheringTests Change-Id: I1319efd871796da7234383a29ab64a1623101ae7
* Merge changes from topic "dedup-interfaceparams"Maciej Żenczykowski2022-03-051-1/+1
|\ | | | | | | | | | | * changes: Remove unused InterfaceParams jarjar rule Deduplicate InterfaceParams
| * Deduplicate InterfaceParamsPatrick Rohr2022-03-041-1/+1
| | | | | | | | | | | | | | | | CS should use InterfaceParams from frameworks/libs/net. Test: builds Bug: 222448728 Change-Id: I1f45d3171b265461a8724b4be7b212c030b63fe9
* | Pass whole TetheringConfiguration to IpServermarkchien2022-03-031-4/+5
|/ | | | | | | | | This is a no-op CL that passing whole TetheringConfiguration to IpServer to reduce the number of IpServer constructor parameters. Bug: 170056953 Test: atest TetheringTests Change-Id: I4ec17f7ecaefd7f275139ad9c7f7551635b192c9
* Use new bluetooth API to enable/disable bt tethering after Tmarkchien2022-01-171-7/+8
| | | | | | | | | | | | | This change only apply to the device after T. Use new bluetooth API to change bluetooth tethering settings and the new API provide the callback to to notify Tethering when bluetooth interface is ready. Tethering doesn't use bluetooth interface status change event from netlink to add/remove IpServer anymore. Tag: #feature Bug: 190438212 Test: TetheringTest Change-Id: Iae92d98d500f83b116da7282cf1130fb8fecf53d
* Rename tethering util folder and its package namemarkchien2021-11-091-4/+4
| | | | | | | | | | | | | | Move tethering util files from android.net.util into com.android.networkstack.tethering.util. The goal is move all of tethering internal files into its own namespace com.android.networkstack.tethering.util. Bug: 205088391 Test: atest TetheringTests atest CtsTetheringTest atest TetheringPrivilegedTests Change-Id: I6559fb4f873b3cad5b210b10e49df1b6c6914a70
* Move to f/l/n instead of RouteUtilsChalard Jean2021-10-291-4/+3
| | | | | Test: TetheringTests Change-Id: I35b36538463a7fc2f02e142719c898d1694b2d6b
* Use SdkLevel util instead of explicitly checking the versionmarkchien2021-08-121-4/+2
| | | | | | | | | | There are IpServerTest test case fail because the code check the wrong code name for T pre-release builds. Bug: 194812819 Test: atest TetheringTests Change-Id: I73bf58c60b6e790fe0060b60c023c10f5d8cbfa8
* Skip bpf offload if upstream interface is VCNmarkchien2021-07-131-2/+14
| | | | | | | | | Bpf offload do not support VCN network yet, don't start bpf offload if the interface is ipsec*. Bug: 191178945 Test: atest TetheringTests Change-Id: I1ad8cededddec42f45b08aaa31d583c548d105f0
* Clear IPv4 offload rules when tethering stoppedHungming Chen2021-06-231-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The condition for deleting IPv4 forwarding rules. 1. When the tethering client has gone, deletes the client and its rules. 2. When the upstream has gone, deletes all rules. 3. When the upstream has changed, deletes all rules. Test: atest TetheringCoverageTests and check IPv4 offload rules via dumpsys tethering in the following test cases. Bug: 190783768 Test cases: a. Loss upstream interface while tethering 1. Enable WIFI tethering 2. Disable upstream interface 3. Check the rules are removed. b. Loss downstream interfaces while tethering 1. Enable WIFI tethering 2. Enable BT tethering 3. Disable BT tethering 4. Check the BT tether rules are removed. 5. Disable WIFI tethering 6. Check the WIFI tether rules are removed. c. Switch upstream interface while tethering 1. Enable WIFI tethering 2. Enable BT tethering 3. Switch upstream interface from cellular to wifi. 4. Check all rules are removed. d. Enable NAT failure (manual) Log: The rule deletion in each case. - IpServer#stopIPv4: case b and case d. - BpfCoordinator#updateUpstreamNetworkState: case a and case c. Test case a 06-23 09:58:59.245 [...] Tethering: [BpfCoordinator] updateUpstreamNetworkState tetherOffloadRule4Clear wlan2 Test case b 06-07 22:17:51.886 [..] Tethering: [bt-pan] cleanupUpstream bt-pan 06-07 22:17:51.888 [..] Tethering: [bt-pan] stopIPv4 bt-pan 06-07 22:18:23.769 [..] Tethering: [wlan2] cleanupUpstream wlan2 06-07 22:18:23.772 [..] Tethering: [wlan2] stopIPv4 wlan2 Test case c 06-08 11:11:48.277 [..] Tethering: [BpfCoordinator] updateUpstreamNetworkState tetherOffloadRule4Clear bt-pan 06-08 11:11:48.396 [..] Tethering: [BpfCoordinator] updateUpstreamNetworkState tetherOffloadRule4Clear wlan2 06-08 11:11:48.579 [..] Tethering: [wlan2] cleanupUpstreamInterface wlan2 06-08 11:11:48.808 [..] Tethering: [bt-pan] cleanupUpstreamInterface bt-pan Enabling NAT failure 06-08 13:04:18.117 [..] Tethering: [wlan2] Exception enabling NAT [..] 06-08 13:04:18.234 [..] Tethering: [wlan2] cleanupUpstream wlan2 06-08 13:04:18.246 [..] Tethering: [wlan2] stopIPv4 wlan2 Change-Id: Id505a3deb277bbe0f44403234d8ca8bbf01eec80
* Suppress IpServer message logsmarkchien2021-06-081-7/+14
| | | | | | | | | | | | | | | | To avoid log flooding, suppress CMD_IPV6_TETHER_UPDATE and CMD_NEIGHBOR_EVENT message log because they appear frequentlg and don't have any content which means they are ueseless for debugging. Also remove logMessage from BaseServingState to fix duplicated message because all the message already log in TetheredState and LocalHotspotState which inherit BaseServingState. Bug: 162920185 Bug: 185649441 Test: atest TetheringCoverageTests atest MtsTetheringTestLatestSdk atest CtsTetheringTest Change-Id: Ib8fe719f3c1c4a65e6b5152df5e5adf33aba2079
* Allow callers of startTethering to choose local-only mode.Lorenzo Colitti2021-04-191-1/+1
| | | | | | | | | | | This is useful for OEMs that want to use RNDIS or NCM as a local-only link that is directly connected to some other host. This can be used to implement USB tethering using NCM, which currently only supports local-only mode. Bug: 175090447 Test: TetheringIntegrationTests:EthernetTetheringTest#testLocalOnlyTethering Change-Id: I0ffaa46e4640e5b235340a15d25909106ceb0c07
* Set the limit whenever any IPv4 or IPv6 rule exists.Lorenzo Colitti2021-04-011-8/+26
| | | | | | | | | | | | | | | | | | | | | | | | Currently, BpfCoordinator only sets the data limit on a given upstream whenever the first IPv6 rule is created on that upstream, and clears it whenever the last rule is deleted on that upstream. It never does this when adding or removing IPv4 rules. This makes it impossible to offload traffic on IPv4-only networks. Fix this by setting the limit when IPv4 rules are created or deleted as well. Test: atest TetheringCoverageTests Manual tests as the follows Test {add, clear} limit with IPv6-only network [OK] Test {add} limit with IPv4-only upstream [OK] TODO: Test {clear} limit with IPv4-only network. blocked by aosp/1579873 because the IPv4 rules have never deleted. Change-Id: I5a29bdd18e564318759f617023163e23fb5a3ed0
* [NFCT.TETHER.15] Attach BPF program in the mainline moduleHungming Chen2021-03-111-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Migrate Maze's BPF program attaching and detaching functions from system/netd/server/OffloadUtils.{c, h} to tethering module. Test: atest TetheringCoverageTests Test case #1: Enable WiFi hotspot and check tc filters are added or removed on both wlan1 and rmnet_data#. $ adb shell tc filter show dev wlan1 ingress filter protocol ipv6 pref 1 bpf chain 0 filter protocol ipv6 pref 1 bpf chain 0 handle 0x1 prog_offload_schedcls_tether_upstream6_ether:[*fsobj] direct-action not_in_hw id 2 tag 7cf020cc09a7c982 filter protocol ip pref 2 bpf chain 0 filter protocol ip pref 2 bpf chain 0 handle 0x1 prog_offload_schedcls_tether_upstream4_ether:[*fsobj] direct-action not_in_hw id 7 tag 2f87d55b636c082c $ adb shell tc filter show dev rmnet_data2 ingress; filter protocol ipv6 pref 1 bpf chain 0 filter protocol ipv6 pref 1 bpf chain 0 handle 0x1 prog_offload_schedcls_tether_downstream6_rawip:[*fsobj] direct-action not_in_hw id 3 tag 8b3885b75bd261de filter protocol ip pref 2 bpf chain 0 filter protocol ip pref 2 bpf chain 0 handle 0x1 prog_offload_schedcls_tether_downstream4_rawip:[*fsobj] direct-action not_in_hw id 6 tag b1c9478c91f8df9a Test case #2: Enable USB tethering and check tc filters are added or removed on both rndis0 and rmnet_data#. Test case #3: Enable WiFi and USB tethering and check tc filter are added or removed on rndis0, wlan1 and rmnet_data#. Change-Id: I3f9a65043271bc8f5bf1b82ae505c471625ca9de
* Remove IpServer.Dependencies#getIfIndex.Lorenzo Colitti2021-01-271-12/+0
| | | | | | | This code is unused. Test: atest TetheringTests Change-Id: Iaac422d72e8538b67798cb3ae3737deb7b426401
* [NFCT.TETHER.7] Prepare the downstream information for IPv4 offload ruleHungming Chen2021-01-221-0/+28
| | | | | | | | | | | | | | Add and remove downstream client information to BpfCoordinator Required for building IPv4 forwarding rule when a conntrack event is received. The IpServer provides the following elements of a rule which is not included in conntrack event: - Downstream interface index - Downstream Mac address - Client IP address to Client Mac address Test: atest TetheringCoverageTests Change-Id: I84db13acc047ace5730d17f0d3dd99544f516084
* [NFCT.TETHER.1] Add conntrack monitor to BpfCoordinatorHungming Chen2021-01-211-0/+11
| | | | | | | | A preparation for starting monitoring conntrack event which is required by IPv4 tethering offload. Test: atest TetheringCoverageTests Change-Id: Ied46aeca193554f52a90889dfdf92827e94845d6
* Make the IP subnet persistent till rebootmarkchien2020-10-061-4/+4
| | | | | | | | | Make the IP subnet persistent if it do not conflict with upstream. It allow client to reuse its IP that usually reduce DHCP procedure. Bug: 168169687 Test: atest TetheringTests Change-Id: Iddc5304730dce7b11c5d124b7eddce057d752bbd
* tethering: DAD Proxy DaemonTyler Wear2020-09-221-8/+37
| | | | | | | DAD proxy daemon responsible for forwarding NS/NA between tethered iface and upstream iface. Change-Id: I2e58e10e7fa7dba6a6f63ad03b000549f3afc37e
* Revert "Revert "Move Inet[4]AddressUtils to libs/net""Chalard Jean2020-08-071-1/+2
| | | | | | | | | | | | | | | This patch is still needed and should go in now that the error is fixed. The patch was submitted into rvc-dev and is already in rvc-dev-plus-aosp (patch in in ag/11923559, revert skipped in ag/12072199). A follow-up will remove the unused services.net-module-wifi target. Test: originally tested in aosp/1324109 Test: m; manual: flashed, wifi and telephony working Test: atest NetworkStackCoverageTests Change-Id: I1074eedb0b0f156a1135e11210ec102de15ea674 Merged-In: Icd141a992c46290c74929785e261a1cd57bc001b
* Merge "Update language to comply with Android's inclusive language guidance"Chiachang Wang2020-07-301-6/+10
|\
| * Update language to comply with Android's inclusive language guidanceChiachang Wang2020-07-291-6/+10
| | | | | | | | | | | | | | | | | | See https://source.android.com/setup/contribute/respectful-code for reference. Test: m ; atest TetheringTests Bug: 161896447 Change-Id: Idc58697c72fb00896bee00185fefc50c1a24dd35
* | Always stop dhcp server even it is obsoletemarkchien2020-07-291-3/+7
|/ | | | | | | | If dhcp server is obsolete, explicitly stop it to shut down its thread. Bug: 161418295 Test: atest CtsTetheringTest Change-Id: Ic5b876bd23711ec8d832879a7baee0495246b218
* Revert "Move Inet[4]AddressUtils to libs/net"Chalard Jean2020-07-021-2/+1
| | | | | | | | | This reverts commit cf86031c12405ddb5817cf834c49a032480547b3. Reason for revert: Breaks the build b/160390899 Merged-In: Icd141a992c46290c74929785e261a1cd57bc001b Change-Id: Ie10e66f61393602f17fbb61bf17230b176bf1f44
* Move Inet[4]AddressUtils to libs/netRemi NGUYEN VAN2020-07-021-1/+2
| | | | | | | | | | | | | | | | | | The classes should not be picked up from frameworks/base, as they are part of several mainline modules. Also refine comments in DhcpResults following feedback in previous change. (cherry-pick from internal branch skipping wifi classes; no other conflict) Bug: 151052811 Test: m; manual: flashed, wifi and telephony working Test: atest NetworkStackCoverageTests Merged-In: I7074651c6a2a7a6b11bcf13cc4bb03833d7d655f Change-Id: I7074651c6a2a7a6b11bcf13cc4bb03833d7d655f
* Tethering: Add WiGig supportDedy Lansky2020-06-221-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | | This change is a combination of following changes: 1) Tethering: add TETHERING_WIGIG type Currently both WIFI and WIGIG use the same tethering type, TETHERING_WIFI. This causes conflicts between the frameworks, when both WIFI and WIGIG SoftAPs are started, one or both will not work. Fix this by using a seperate tethering type for WIGIG. 2) Tethering: remove TETHERING_WIGIG state machine on interface down The wigig state machine relies on a TETHERING_STATE_CHANGED broadcast that is sent when the tethering state machine is first created, during interface up. Currently the tethering state machine is not removed on interface down except for TETHERING_BLUETOOTH, and as a result wigig tethering only works the first time SoftAP is started. In order to fix this, remove the tethering state machine on interface down for TETHERING_WIGIG as well. Bug: 143356416 Test: TetheringCoverageTests Change-Id: Ic4d3aca0ed69234093af7f0206dab3335938c52a
* Merge "Let only Ethernet manage ethernet interface up and down"Mark Chien2020-06-191-2/+3
|\
| * Let only Ethernet manage ethernet interface up and downMilim Lee2020-06-191-2/+3
| | | | | | | | | | | | | | | | | | | | | | When LAN link is changed for using ethernet interface from Ethernet tethering to Ethernet, there is confiict as Ethernet Tethering is trying to make ethernet link down and Ethernet is trying to make ethernet link up. So, this would make Ethernet only manage ethernet interface link state. Test: manual Bug: 130840861 Change-Id: I1cd40ae764bdeecbb59e3889e9399b7f4b05f9cc
* | Memory leak due to no stop for IpNeighborMonitor.h.zhang2020-06-181-0/+1
|/ | | | | | | | | | | | | | 1. When Wi-Fi enabled, ap0 interface is added and IpNeighborMonitor's start() is invoked in IpServer's constructor. 2. There's no stop for IpNeighborMonitor when IpServer stop. 3. During overnight test for Wi-Fi, networkstack is too slow to process request due to memory leak in IpNeighborMonitor and binder buffer is blocked causing exception. Solution: Invoke IpNeighborMonitor.stop() in UnavailableState.enter(). Bug: 159097215 Test: automatic, turn on and off Wi-Fi every 6 seconds overnight Change-Id: I8f60c13706f05306e8f25a15f7861d7ecabbc10e
* [BOT.6] Make BpfCoordinator to support data limitHungming Chen2020-06-091-35/+15
| | | | | | | | | | | | | | | | | | | | The BPF tethering coordinator listens to the forwarding rule changes for updating data limit which is applied in the following conditions. - After adding the first rule on a given upstream, add data limit. - After removing the last rule on a given upstream, clear data limit. - The service applies a new data limit on current upstream. The reason for relying on rule changes is because the Tethering and IpServer objects have multi-internal state machines. It is hard to synchronize all of their states. Note that the data limit cleanup for stopping or switching upstream relies on offload rules are all removed as well. Bug: 150736748 Test: manual Change-Id: I829d36339973f9473fe6b616c48aa288f18d1c46
* Merge "Stop reducing RA advertised ipv6 mtu by 16 - not needed."Maciej Żenczykowski2020-06-031-6/+1
|\
| * Stop reducing RA advertised ipv6 mtu by 16 - not needed.Maciej Żenczykowski2020-06-021-6/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This effectively reverts: commit da0fb1bca8eda1ce8159289a2ea9e4f6933ce517 Author: Maciej Żenczykowski <maze@google.com> Date: Wed Feb 19 01:24:39 2020 -0800 Reduce advertised ipv6 mtu by 16 to fit ethernet header This is a temporary hack to workaround the inability of current kernel's ebpf bpf_skb_change_mode() function to prefix a 14-byte ethernet header on to a packet without going over the upstream (source, rawip) interface's mtu *before* we bpf_redirect() to the downstream (destination, ethernet) interface. Test: build, atest, atest TetheringTests Bug: 149816401 Test: flashed a flame with new kernel and it works at 1500 mtu Bug: 149816401 Signed-off-by: Maciej Żenczykowski <maze@google.com> Change-Id: I76a75a16fa27b47d78816b2f9379ef4bb68beb00 Merged-In: I76a75a16fa27b47d78816b2f9379ef4bb68beb00
* | [BOT.5] Move class Ipv6ForwardingRule from IpServer to the coordinatorHungming Chen2020-05-291-35/+1
| | | | | | | | | | | | | | | | | | This is a preparation for moving adding/removing forwarding rules from IpServer to BpfCoordinator. Bug: 150736748 Test: atest IpServerTest Change-Id: I85316ef09ff3c9389ded11dcc384493d699da48e
* | [BOT.2] Create a coordinator and stats provider to provide tether statsHungming Chen2020-05-291-1/+14
|/ | | | | | | | | | | Make BPF tethering offload coordinator, BpfCoordinator, registers a network stats provider, BpfTetherStatsProvider, and provide the tethering stats from the BPF map. Bug: 150736748 Test: new test BpfCoordinatorTest Change-Id: I22e71f87b67668f7e733e4f215d93bf5b2c9380d
* Tethering: ensure downstream prefix do not conflict with upstreammarkchien2020-05-271-89/+80
| | | | | | | | | | | | | | | | | - Add New class PrivateAddressCoordinator to coordinate the private address conflict problem. - Downstream prefix would be random in 192.168.0.0/24 ~ 192.168.255.0/24. - If new upstream prefix is conflict with existing downstream prefix, downstream would be kicked out and it would request a new one. - The last conflict upstream prefixes would be blacklist. Avoid to select downstream prefix which is conflict with prefixes in blacklist. Bug: 130879722 Test: -build, flash, boot -atest TetheringTests Change-Id: Ib45b87bcd9eeb5da03fb7ec90b1af9ca53998cf5
* Adjust TTL for ipv6 tetheringmarkchien2020-05-241-7/+6
| | | | | | | | | | | | If upstream is cellular, set the TTL in Router Advertisements to "network-set TTL - 1" for carrier requirement. For other non-cellular upstream, set TTL as "network-set TTL + 1" to preventing arbitrary distinction between tethered and untethered traffic. Bug: 154776299 Test: atest TetheringTests Change-Id: I7f2696a642f96c6aafb5613b980bf5bcdd08bbda
* Support MirrorLink DHCPDECLINE.Xiao Ma2020-05-131-62/+170
| | | | | | | | | Add the specific implementation of onNewPrefixRequest callback on IpServer side, also refactor some common code. Bug: 130741856 Test: atest TetheringTests Change-Id: If2871bf899cb5890bbfee18063a194c92b6f474e
* A minor followup change for BPF offload device option stuffHungming Chen2020-05-121-6/+6
| | | | | | | | | - Correct description and spelling in the code and xml files. - Add a TODO for refactoring the IpServer constructor. - Refine the if-statement for starting IP neighbor monitor. Test: atest IpServerTest Change-Id: If9c8bc6f785fa80575db56de4e223292e9807ace
* Use device option to control BPF offload featuresHungming Chen2020-05-051-7/+27
| | | | | | | | | | | If BPF offload device config is not enabled: - Does not add/remove offload forwarding rules through disabling IP neighbor monitor. - Does not apply the RA MTU reduction. Bug: 149997301 Test: atest IpServerTest Change-Id: I2d6f80f0229f580c4b16243a064e889a6c37f77a
* Don't crash when receiving an RTM_DELNEIGH or NUD_FAILED.Lorenzo Colitti2020-04-141-2/+7
| | | | | | | | | | | | | | | | These events don't have MAC addresses, so the code attempts to create an Ipv6ForwardingRule with a null MAC address. This crashes when attempting to get the raw MAC address bytes to send to netd in the TetherOffloadRuleParcel. This was not caught by unit tests because the test exercise this code path in a way that is not correct (by sending RTM_DELNEIGH and NUD_FAILED events with MAC addresses). Fix the unit tests to properly pass in null MAC addresses for these events. Bug: 153697068 Test: fixed existing tests to be more realistic Change-Id: I26d89a81f1c448d9b4809652b079a5f5eace3924
* Merge "Rename IDhcpLeaseCallbacks to IDhcpEventCallbacks for more generic."Xiao Ma2020-04-061-2/+7
|\
| * Rename IDhcpLeaseCallbacks to IDhcpEventCallbacks for more generic.Xiao Ma2020-04-061-2/+7
| | | | | | | | | | | | Bug: 130741856 Test: atest TetheringTests Change-Id: I66614fbf67fba1e7dab0b8a2d41bc30a726e4f38
* | Migrate to TetherOffloadRuleParcel in IpServerLorenzo Colitti2020-04-041-4/+16
|/ | | | | | | | | | The netd tethering offload IPCs are changing from taking a list of primitives to taking a TetherOffloadRuleParcel. Modify their only caller. Bug: 140541991 Test: atest IpServerTest Change-Id: I83718c80ef9d31199c87021b4dd5821717fd5ba5
* Merge "Assign specific client address to dhcp server"Treehugger Robot2020-03-301-8/+24
|\
| * Assign specific client address to dhcp servermarkchien2020-03-191-8/+24
| | | | | | | | | | | | | | | | Bug: 141256482 Test: manual atest TetheringTests Change-Id: Ief76c98c843ba5420224cbf0f34464f366c891b7
* | TetheringManager API clean upmarkchien2020-03-191-2/+2
|/ | | | | | | | | | | | | | | | | | | | | | | Per API review: - @IntDef defined on the type integer parameter - have getters on each parameter that is set in the TetheringRequest.Builder - new added API should not be deprecated Below APIs is moved from system-current to module-lib-current that only plafrom code(e.g. ConnectivityManager and Settings) can use them. TetheringRequest. onTetherableInterfaceRegexpsChanged, TetheringInterfaceRegexps: Only platform code can use them because interfaces by regular expressions are a mechanism which is planning to be deprecated. Also rename some constants for easier to understand. Bug: 149858697 Bug: 151243337 Test: m doc-comment-check-docs atest TetheringTests Change-Id: I45cb21d5bc919f6d32c42650326597d5173ea028 Merged-In: Idd041f0fbeca411ea23e49786a50dd7feb77ef45
* Merge "Support static address configuration"Mark Chien2020-03-171-6/+22
|\
| * Support static address configurationmarkchien2020-03-171-6/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Application can specify static ipv4 server and client address to setup tethering and this is one shot configuration. Tethering service would not save the configuration and the configuration would be reset when tethering stop or start failure. When startTethering callback fired, it just mean tethering is requested successful. Therefore, callers may call startTethering again if startTethering successful but do not receive following tethering active notification for a while. Tethering service never actually does anything synchronously when startTethering is called: -startProvisioningIfNeeded just posts a message to the handler thread. -enableTetheringInternal doesn't do anything synchronously, it just asks the downstreams to get their interfaces ready and waits for callbacks. If tethering is already enabled with a different request, tethering would be disabled and re-enabled. Bug: 141256482 Test: -build, flash, boot -atest TetheringTests -atest CtsTetheringTest Change-Id: I0399917e7cefa1547d617e688225544c4fc1a231
* | Cleanup the TetheredClients APIRemi NGUYEN VAN2020-03-131-2/+5
|/ | | | | | | | | | Add comments to getters as requested in API review, and remove the expirationTime private field that was planned to be replaced with LinkAddress expiration. Test: atest TetheringTests Fixes: 150878126 Change-Id: Iecf65859cdeeaac2fa7b817b4f505c510424ac89
* Merge changes I4a624ea4,I8626932eLorenzo Colitti2020-02-251-3/+18
|\ | | | | | | | | | | * changes: Fix a logic error in IpServerTest#addRemoveipv6ForwardingRules Clear IPv6 forwarding rules when losing upstream or stopping.
generated by cgit v1.2.3 (git 2.25.1) at 2026-01-13 15:51:24 +0000