Status Update
No update yet.
Comments
su...@google.com
It looks like you are raising an issue as an Android user, rather than an Android Open Source Developer. Our Android Support team will be in contact with you shortly. In the meantime, here are helpful resources:
an...@google.com
su...@google.com
Can you provide the below requested information to better understand the issue:
Android build Which Android build are you using? (e.g. KVT49L)
Device used Which device did you use to reproduce this issue?
Android bug report (new bugreport) After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory.
Alternate method: After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Note: Please upload the files to google drive and share the folder to
ni...@gmail.com
>>> This problem was confirmed on a Motorola G60s phone running Android version 12 Build S3RLS32.114-25-3
Please refer to the earlier referenced issue with regards to the 'bug' status of this matter:
The same point stands; this is NOT a bug, but a failure to implement a common RFC related to IP routing. Bug reports will not help and are not an appropriate way to take this forward.
If you are not clear on this matter, please refer this thread to someone who understands IP networking at the RFC level so that there's a collective 'oh crap, how can we have failed to implement this' moment. Then you can put it right and join the ranks of all the other operating systems (Windows, Mac, Linux...) that do this properly.
Do not let this fresh issue report wither and die like the previous one because of a lack of understanding of the fundamental networking nature of this matter.
su...@google.com Restricted+
ni...@gmail.com
namely:
The Motorola G60s mentioned on the initial report
Samsung Galaxy Tab A7, software Android 12 build SP1A.201812.016.T500XXS4CJ1
Samsung Z Fold 4. Not currently available to check build version.
Option 121 support is missing on all these devices.
On 07/01/2023 05:36, buganizer-system@google.com wrote:
su...@google.com
We have shared this with our product and engineering team and will update this issue with more information as it becomes available.
tz...@gmail.com
ra...@google.com
pa...@gmail.com
It is possible to fix this for old devices too?
dr...@gmail.com
Model number: SM-T500
Android version: 12
Build number: SP1A.210812.016.T500XXU4CWD2
no...@gmail.com
je...@gmail.com
cr...@gmail.com
ra...@google.com
mc...@gmail.com
This issue, or identical issues, has been opened and closed multiple times over the years, so im curious why Android/Google has a different opinion on this than Windows, iOS, etc
km...@gmail.com
Now, it comes to 2025, and WE NEED A REASON FOR "WON'T FIX" for even 7 years or A WORKAROUND.
Description
"DHCP Option 121 Classless Static Route ignored.
Android devices still do not respect DHCP option 121 to accept additional static routes pushed via DHCP and this is a blocker to using the devices in some corporate and small business situations.
DHCP option 121 is described in RFC3442:
Support for this DHCP option should be a 'given', and a cursory check of a Linux desktop machine (Mint 21), the same machine running Windows 10 and a couple of recent Apple iPhones show they all behave as expected in this context.
This problem was confirmed on a Motorola G60s phone running Android version 12 Build S3RLS32.114-25-3
I am not a developer but an IT Systems Manager so go easy on me:
Steps to reproduce:
Configure the LAN DHCP service to push a static route to hosts/clients using DHCP option 121
On an Android-based device, connect to the LAN
Confirm that the device has connected to the LAN and been assigned a working IP address, default gateway and DNS server/s
Confirm that the option 121 static route has NOT been accepted and so resources on the target subnet cannot be accessed.
Workaround: Do not use Android devices on networks that require devices to be assigned and use static network routes.