Hi,
We're having an issue with Samsung Galaxy S3 (4.1.1.) where we're connecting to specific SSID, this SSID is passed to access gateway, access gateway acts as DHCP server.
The S3 can connect and sends DHCP request on first association with empty request and receives and uses IP allocated from access gateway, establishes session at access gateway, passes data, everything works fine.
The issue we're having is that we'll disconnect S3 from Wi-Fi and then reconnect but S3 sends DHCP request with option 50 (requested IP address) with same address previously requested.
This is generally not an issue but our access gateway will not allow session for user if user sends DHCP requested with option 50 set.
There doesn't appear to be a way to have S3 not send DHCP request with option 50 set after first association.
Examining verbose logcat output always shows request going with option 50.
We've tried doing 'forget network', tried rebooting phone, tried resetting to factory default but same results. When we select network on the SSID, it's set for DHCP, not 'static'.
Once we associate with SSID and receive IP address, outside of factory defaulting the S3, it will always send request for same IP address. Setting low lease time at access gateway's DHCP pool wouldn't do much help as that would just leave users not able to connect within lease time.
We rooted one of the S3s and found we could avoid this by going in and deleting the dhcp*lease files in the adb shell in the "dhcp" directory (as a guess):
We tried calling S3 and got no help from them after spending one hour with support trying to explain what DHCP is, so no resolution.
We searched this S3 forum and found nothing, so now asking for your feedback.
Is there way to avoid this?
I think all signs are pointing to 'no'.
While it's fine that we can avoid this by using rooted phone, we can't have this as solution for hundreds of thousands of users (hopefully millions).
We're having an issue with Samsung Galaxy S3 (4.1.1.) where we're connecting to specific SSID, this SSID is passed to access gateway, access gateway acts as DHCP server.
The S3 can connect and sends DHCP request on first association with empty request and receives and uses IP allocated from access gateway, establishes session at access gateway, passes data, everything works fine.
The issue we're having is that we'll disconnect S3 from Wi-Fi and then reconnect but S3 sends DHCP request with option 50 (requested IP address) with same address previously requested.
This is generally not an issue but our access gateway will not allow session for user if user sends DHCP requested with option 50 set.
There doesn't appear to be a way to have S3 not send DHCP request with option 50 set after first association.
Examining verbose logcat output always shows request going with option 50.
We've tried doing 'forget network', tried rebooting phone, tried resetting to factory default but same results. When we select network on the SSID, it's set for DHCP, not 'static'.
Once we associate with SSID and receive IP address, outside of factory defaulting the S3, it will always send request for same IP address. Setting low lease time at access gateway's DHCP pool wouldn't do much help as that would just leave users not able to connect within lease time.
We rooted one of the S3s and found we could avoid this by going in and deleting the dhcp*lease files in the adb shell in the "dhcp" directory (as a guess):
We tried calling S3 and got no help from them after spending one hour with support trying to explain what DHCP is, so no resolution.
We searched this S3 forum and found nothing, so now asking for your feedback.
Is there way to avoid this?
I think all signs are pointing to 'no'.
While it's fine that we can avoid this by using rooted phone, we can't have this as solution for hundreds of thousands of users (hopefully millions).