Fixed
Status Update
Comments
rk...@google.com <rk...@google.com>
jh...@google.com <jh...@google.com> #2
Removing the gki-partner-respin hotlist from this bug as this doesn’t seem like a respin request.
Please note that if you need to request a respin, please use this respin request intake form.
https://docs.google.com/forms/d/1-qbtELQ9JW0g-kx0tpe34jRgZ-tdym5yJ8RMsvYafcA/viewform?edit_requested=true
Please note that if you need to request a respin, please use this respin request intake form.
tk...@google.com <tk...@google.com> #3
These are both "tristate" configs which means you can enable them as vendor modules. There is no need for them to be enabled in the GKI kernel
rk...@google.com <rk...@google.com>
ma...@google.com <ma...@google.com> #4
Ipv6 nat is not permitted according to Android CDD.
kc...@squareup.com <kc...@squareup.com> #5
Can you link me the text that says ipv6 nat is not permitted?
I can't find anything on the Android 14 CDD that says it's not allowed
ma...@google.com <ma...@google.com> #6
// https://source.android.com/docs/compatibility/15/android-15-cdd#7452_ipv6
C-0-6
// MUST provide third-party applications with direct IPv6 connectivity to the
// network when connected to an IPv6 network, without any form of address
// or port translation happening locally on the device.
C-0-6
// MUST provide third-party applications with direct IPv6 connectivity to the
// network when connected to an IPv6 network, without any form of address
// or port translation happening locally on the device.
ma...@google.com <ma...@google.com> #7
[C-0-6] MUST provide third-party applications with direct IPv6 connectivity to the network when connected to an IPv6 network, without any form of address or port translation happening locally on the device.
rk...@google.com <rk...@google.com> #8
I added CONFIG_NETFILTER_XT_TARGET_LOG
to android16-6.12+. I don't think it is worth backporting (sources and prebuilts) to 14.
Description
PLEASE READ:
This form is only for reporting bugs found in the Android system while developing Android applications. Use the Developer Tools subcomponent for issues with the developer tools.https://issuetracker.google.com/issues/new?component=192633
Please describe the problem in detail. Be sure to include:
Using the prebuilt emulator kernelshttps://android.googlesource.com/kernel/prebuilts/6.1/x86-64/
and also arm64, we noticed that the CONFIG_IP6_NF_NAT and CONFIG_NETFILTER_XT_TARGET_LOG kernel options are not enabled by default. Is it possible to have these enabled by default so we don't have to regnerate a new kernel?
What happened.
What you think the correct behavior should be.
We would like to request to have both of these kernel options enabled by default
No
Don't forget to mention which version of Android you're using, and/or which device the problem appears on (model and Android version). Using Android 14, on emulators (cuttlefish and AVD).
Please also run "adb bugreport" and archive the output.
To avoid the possibility of sharing private information, please share bugreports and screenshots from Google Drive. Share files withandroid-bugreport@google.com and include only Google drive links in your bug. If attaching bug reports or other sensitive data directly to issues, please mark the attachment(s) as “Restricted ( https://developers.google.com/issue-tracker/concepts/restricted-content)” when creating a bug or adding a comment. Restricting or deleting your comment or attachment can also be done using the overflow menu after submitting.
Disclaimer: Please note, by submitting this bug report, you acknowledge that Google may use information included in the bug report to diagnose technical issues and to improve our products and services, in accordance with our Privacy Policy (https://policies.google.com/privacy ), and you agree that we may share it with engineering partners potentially impacted by your issue.
Bug reports include personal information logged on your device or by apps, such as: File names Installed apps and usage Email addresses of the profiles on the device Device identifiers, such as phone number Web history information, including URLs / URIs Location information, including limited location history Network information, such as IP/SSID/MAC addresses and saved or scanned APNs System or device information, such as memory and processes