Database Users

Does anyone have a proper workaround for the obtaining IP address?

Honestly I have no idea why this is happening on my android 4.0+ devices. I will get stuck on obtaining IP address connecting to certain networks and the only thing that worked for my home network is static IP. But for instances when I don't have access to the router to know what the static IP should be, is there a way to get this working? This happened on my phone as well. I was at a local cafe which had wifi and before I upgraded my samsung galaxy s2 to ICS, I could connect to their wifi no problem, now it has the same issue, and so does my Nexus 7. I don't know what to enter for static IP, I entered some random IP, it connected but internet still didn't work. Why is this problem plaguing ICS onward, and does anyone have a workaround when static IP is not an option?

This is definitely not a universal problem (I've never heard of it before). Are you running stock roms? If not, then do you have these problems with stock roms?

C2Q
Why are you posting this to multiple threads?
There is no "proper way" to use a static IP for a router that is setup for DHCP only. For routers that use both, many times the static IP's are reserved for specific devices.
Sent from my Nexus 7

Because I didn't notice the other thread before I posted this one. Anyway then why is this obtaining IP address loop a problem on ICS? As I said, my phone on GB would manage to connect/obtain an IP address just fine before I upgraded to ICS. This happened with my home router and other areas as well. The solution that worked for me at home was to assign a random static IP within my routers IP range. But if I don't know the gateway IP this won't work. So what gives? I'm kind of confused what you mean by routers set up for DCHP only. If I use static or DCHP options on the android device to connect, they will both work (this was before ICS).

I ran into similar issues with my nexus 7 and my work open wifi. It needs you to connect to a web login page where you accept a use policy before you can surf. My nexus would connect but never redirect to that login page.
The issue was resolved by using static IP instead of DHCP and also by changing the DNS values to DNS1 8.8.8.8 and DNS2 4.4.8.8
Changing those settings lets me finally use my work wifi. My phone also has the same issue (its an ICS phone, whilst the nexus is jelly bean) but is not resolved with this change.

Sunburn74 said:
the issue was resolved by using static IP instead of DHCP and also by changing the DNS values to DNS1 8.8.8.8 and DNS2 4.4.8.8
Click to expand...
Click to collapse
Sure that is not 8.8.4.4 ?

Thanks for posting this question. I have exactly the same problem with my Samsung S3 (ICS) and Nexus 7 (Jellybean). My old Samsung S2 (Gingerbread) worked fine.
I am trying to connect to a hotel open network. When I try I get the looping "Obtaining IP..." message. I have a strong network signal.
What gives? How come earlier versions of Android worked but later ones don't?
As the OP stated, the static option works insofar as I can then connect to the network but the made up static IP numbers do not actually let me download (or upload) data. As the OP wrote, you need to know some valid values for the static IP setting.
Does anyone have a solution for this (apart from downgrading to Gingerbread)?

Ive always had this issue but my home router has dhcp off. A majority of routers start with 192.168.1.1 or 192.168.1.2 so its not hard to work it out.
BT routers always start with 192.168.1.254 so there's another option dunno why my devices do it but im used to it. My Wifes Xoom 2 and wildfire S are stock and do not have the issues my rooted ones do but i have just put it down to coincidence

First off. Is your modem in service? Do other devices connect? Have your restarted your tab? Does it connect to other networks? Meaning going to another WiFi hotspot If you can answer yes to all of these questions we move on....
What modem/router are you connecting to?
What type of WiFi encryption are you using? Wep-open, WPA, wpa2-psk
On the tab does it fail to obtain the IP address? Meaning it says "remembered"?
Not going to lie more the 3/4ths of the time you have the wrong WIFI PASSWORD. CHECK IT AGAIN usually its on the modem/router or if you have no clue here is a hint: on windows vista and windows 7 under control panel>network and sharing center>manage WiFi networks if your right click on the network name such as "Ilovepancakes"and go to properties it will have a security tab that you can click on and show password.
Sent from my Nexus 7 using XDA Premium HD app

bonesy said:
Ive always had this issue but my home router has dhcp off. A majority of routers start with 192.168.1.1 or 192.168.1.2 so its not hard to work it out.
Click to expand...
Click to collapse
I don't know what you mean. Do you mean that I should try these numbers to see if they work? You need a number of values to set up static IP addressing to work.

Did you dirty-flash your Nexus? A while back my Gnex wifi connections would take longer to complete the handshake. I did a factory reset/fresh install & it has been much faster.

strongergravity said:
Did you dirty-flash your Nexus?
Click to expand...
Click to collapse
My Nexus (and GS3) is completely stock (I have only added a launcher).
This problem seems to be caused by older routers, which don't seem to like something about newer versions of Android.
I'm not sure if it's something Google can fix, but the combination of old router and new Android seems to make logging onto wi-fi networks a problem.

Bump.

Ive been struggling with this problem for a week now since getting a transformer infinity. My s3 gets stuck when I try to connect to it. The tab cycles through connecting, obtain a valid address and saved.

I bought a new 32gb nexus yday and had this issue. I entered advanced settings, changed dhcp to static. Changed IP addy to 192.168.1.1 and it worked fine. Only had to do it once. After that it connected to every network fine without changing settings again.
Sent from my Nexus 7 using xda app-developers app

Warrior1975 said:
I bought a new 32gb nexus yday and had this issue. I entered advanced settings, changed dhcp to static. Changed IP addy to 192.168.1.1 and it worked fine. Only had to do it once. After that it connected to every network fine without changing settings again.
Click to expand...
Click to collapse
This worked for me also (Infuse 4G on JB), but it seems like this is only a problem on WiFi AP's that have marginal signal strength, even though they appear to have full bars. I personally have never have seen this issue on a network that was performing properly.

Same here!
Same thing is happening to me! Im using he htc desire c running ics.. my phone detects the wifi network, shows that it has excellent strength, but it gets stuck at "Obtaining IP Address"! My friend and I both bought the same model a couple of weeks earlier and till now neither of us have been able to connect to a wifi network! Please Help!!!

its a DHCP bug
This is probably not a problem with your network configuration unless it works everywhere else; im having the same problem as well as other people i know and its definitely a bug with DHCP, so the only way to work around this is by using a static ip as far as i know

bobbyelliott said:
I don't know what you mean. Do you mean that I should try these numbers to see if they work? You need a number of values to set up static IP addressing to work.
Click to expand...
Click to collapse
What he's saying is that most routers will begin assigning addresses starting with 192.168.1.1 or 192.168.2.1 for itself (you can access the router configuration page by typing in this address into a web browser), and then increment upwards afterwards. If you knew that the router started its DHCP addressing with 192.168.1.1, for example, you could try 192.168.1.2, and so on and soforth.
If you did a "dirty" upgrade, I'd recommend doing a factory wipe (after an appropriate backup-- there are some good apps out there that can handle this). In-place OS upgrades have a bad habit of being finicky. Android is also generally less tolerant of network "misconfigurations" than, say, Windows, OS X, or iOS. Many networks that use captive portals (your standard coffeeshop Wi-Fi) deliberately use an altered network setup to support their access policies, such as a captive portal.
However, with the exception of corporate/enterprise networks (which may require fine-tuning because of increased security), you really shouldn't be messing around with this if you don't have at least a rudimentary understanding of how networking works. That's not meant to be insulting, but when people plug in random values and find it doesn't work, it tends to lead to more frustration than utility.
(fyi: The reason you can "connect" by tossing in a random set of octets your your IP and DNS is because you've properly authenticated against your router, but you'll never be able to receive data unless your router's DHCP lease lines up with your self-assigned IP, because the router never handed that address out to you. It's the digital equivalent of building a mailbox in front of your house without registering with the post office, and wondering why you never get mail).

[Q] Does the Nexus Player support "login" WiFi networks (such as those at a hotel(?

[Q] Does the Nexus Player support "login" WiFi networks (such as those at a hotel(?
One of the biggest disappointments I had with Chromecast was that it was impossible to set the unit up in a hotel. Since many hotels have WiFi that require you to log in, you couldn't set up your Chromecast on these networks.
Is this the case with the Nexus Player?

Not really sure, but I have a trick you can try with your Chromecast. Not sure if it will work, but we used to do it back when I was in college because the University network required a username/password login (which sucked if you wanted your XBOX on the network).
Figure out the MAC address of your Chromecast. Go to your laptop or PC, and spoof the mac address of your NIC (or wifi) to match the chromecast. You can usually do this through the device manager in Windows by going to the Properties for your NIC. After that, use your brower to sign in. Go back to Chromecast and see if it worked.
Usually they tie the authentication to your NIC's MAC address...so the theory is that as long as you authenticate the mac address somehow, then any device with that mac address will work. Things might have changed over the past 6 or 7 years though when we used to do that.

IBNobody said:
One of the biggest disappointments I had with Chromecast was that it was impossible to set the unit up in a hotel. Since many hotels have WiFi that require you to log in, you couldn't set up your Chromecast on these networks.
Is this the case with the Nexus Player?
Click to expand...
Click to collapse
Another option if you are a frequent traveler is a portable travel router like the D-Link DIR-510L. This tiny router easily fits in your briefcase yet can turn any wifi network into your own personal wifi hotspot. Basically it connects to a hotel wifi and through your phone, tablet or pc you can log in with your hotel credentials. It then creates a separate wifi network for your own use, one that you control for all your devices (including your chromecast) without having to pay the hotel more for multiple device connections, etc. It even has a built in battery to either run without power or to charge your devices and, with its 3 usb ports, can share a USB drive full of media with all your wireless devices. I know I sound like a commercial here, but I simply couldn't live without this tiny little beauty on the road.

Nexus 6P Acts as Rogue DHCP Server

At work i was playing around with some networking and noticed some weird things. I kept seeing a rogue DHCP server coming up from an IP that I traced to Taiwan. After some time on Wireshark and using this tool I found that every time my Nexus 6P connected to our WiFi it would for a split second send out a DHCP offer to the network on behalf of that Taiwan IP. I thought "Oh My, did I get some malware?". So I reformatted the phone and with a fresh install of the latest Pure Nexus, sure enough on the Setup screen (not even booted all the way into the ROM yet) when I put in the WiFi credentials for the first time, the same broadcast goes out over my LAN. WTF. Is this some sort of phone home backdoor from Huawei or what? I know some phone malware can get in below the ROM level and basically turn your phone into a hypervisor. Hopefully that is not the case or I'll have to toss it in the trash...
Any help is appreciated.

Any easy way for non-techie users like myself to check and verify this?

Bump
Sent from my Nexus 6P using XDA-Developers Legacy app

treesurf said:
Any easy way for non-techie users like myself to check and verify this?
Click to expand...
Click to collapse
Download the dhcp find program and run it from your workstation.
https://www.symantec.com/connect/downloads/detect-rogue-dhcp-servers-network
When it runs it broadcasts a request over your network as if it were a device needing an IP address. Your router or server that controls your DHCP will respond with an offer IP to hand out. A common malware attack is a DHCP man in the middle attack where the rogue DHCP server sends the response before your DHCP server does and it then gives the client machine a different DNS server that is usually some sort of proxy for showing you ads or changing your internet experience for the worse etc. If the wifi hotspot was enabled you'd expect this because the phone does indeed become a DHCP server in order to hand out an IP to your leeching device to tether with. But I have that turned off so that is not the case unless there's a bug in the software.
Once you run that program (your phone needs to be connected to your same network), then turn the wifi off on your phone and then back on again. For me when it joins my Wifi it pings out a DHCP broadcast as shown in my screenshot. It's from an outside IP, originating in Taiwan if you trace it. I have geographic location blocking on my router so its impossible for traffic to actually get to me from that IP but that is what the phone is broadcasting out. I'm a long time sysadmin so I pay pretty close attention to these things i guess.

@Budwise, can you fish flash factory images and check to see it if happens on stock? If not I would definitely report this in the Pure Nexus thread.

I found that I was seeing some odd behavior even when it wasnt connected via WiFi so I believe it happening when it connects is a side effect of something else going on. I think this can be closed.

Note 3 problems with OpenDNS

Can someone help?
I am trying to have my kids Note 3 to go through the OpenDNS service for parental control, specifically, Youtube blocking.
I subscribed to the free OpenDNS service and tested it with WIndows 10 computers, Galaxy S7, Ipnone 4 and Ipod 4 devices. It works great. But my kids have each a Galaxy Note 3 on Android 5 (not rooted) and it doesn't work. Here is what it does:
I put the OpenDNS ip addresses in my DD-WRT router.
I attempt to connect to the WIFI, the connection is established.
A prompt asks me if I want to open the application with Internet or Google Chrome (makes no difference which one i choose)
Once I made a choice, a Google search page opens up, just like a portal page when you connect to a hotel WIFI network.
Leaving the page openbed or closing it won't make a difference, I will loose connectivity to the WIFI within minutes and it will not reconnect automatically.
Putting the DNS addresses on the Device connection or on the router will do the same problem.
I am in Canada and my ISP is Videotron, the Notes 3 are Bell Canada provided but they have no SIM card inside, the kids only use WIFI.
I tried putting the Norton ConnectSafe DNS IPs and it worked fine. The problemis that I want OpenDNS because it's more customizable.
What is it with these Notes 3 that causes a problem with OpenDNS?
Let me know if you need more info.
Thank you.

How do I assign a permanent static IP address to hotspot in Android 10

I would like to assign a permanent static IP address to hotspot in Android 10 (Unofficial LineageOS 17.1 for Natrium by LuK1337, rooted with Magisk v20.3 and updated to Jan 11, 2020 build).
Now whenever I turn on the hotspot, it assigns a different IP to hotspot, 192.168.43.xxx (this will be the gateway IP to other devices that connects to this hotspot).
Note: For simplicity, instead of connecting other devices to this hotspot, I'm just gonna find hotspot IP by running "ip r" on the phone itself.
On the phone, when I open Termux (have tried other Terminal app with the same results), and run, "ip r" and "ip a", I get:
Code:
:/ $ ip r
192.168.43.0/24 dev wlan0 proto kernel scope link [B]src 192.168.43.100[/B]
:/ $
:/ $ ip a
25: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 3000
link/ether 78:02:f8:f0:4d:87 brd ff:ff:ff:ff:ff:ff
inet 192.168.43.[B]100[/B]/24 brd 192.168.43.255 scope global wlan0
valid_lft forever preferred_lft forever
inet6 fe80::7a02:f8ff:fef0:4d87/64 scope link
valid_lft forever preferred_lft forever
:/ $
Now this "src 192.168.43.100" will be different (e.g: 192.168.43.101, 192.169.43.102 etc) everytime I turn hotspot on and off... and I would like to assign a permanent static IP like ".100"
In LineageOS 16 I used the following workaround, which is no longer working in Android 10 (Unofficial LineageOS 17.1):
Code:
In the Termux (have tried other Terminal app with the same results):
(1)
su
mount -o rw,remount /vendor
nano /vendor/etc/init/hostapd.android.rc
and add:
on property:init.svc.hostapd=running
exec - -- /system/bin/sleep 2
exec u:r:magisk:s0 -- /system/bin/ip address add 192.168.43.[B]100[/B]/24 dev wlan0
Save the file.
mount -o ro,remount /vendor
and
(2)
su
mount -o rw,remount /
nano /etc/dnsmasq.conf
and add:
dhcp-host=78:02:f8:f0:4d:87,192.168.43.[B]100[/B]
Save the file.
Then set the permissions:
chown 0.0 /etc/dnsmasq.conf
chmod 0644 /etc/dnsmasq.conf
chcon u:object_r:system_file:s0 /etc/dnsmasq.conf
magiskpolicy "allow dnsmasq system_file file { read getattr open }"
magiskpolicy "allow dnsmasq system_file dir { search }"
mount -o ro,remount /
Any help is greatly appreciated, many thanks in advance.

I've got the same problem with my Pixel 3 running Android 10, also using Termux.
My use case is SSHing into the phone from my iPad to use VIM.
Previously, I used PDANet for its hotspot functionality, but it doesn't work anymore on my Pixel. Depending on your phone, you could give that a shot.

Unfortunately, starting with Android 9, the gateway is always set randomly. You cannot change it without editing the source code and building the firmware, but you can assign an additional static IP address through which you can connect to the phone. I'm not sure that this will help you, but you can see here three methods to solve this problem:
android.stackexchange.com/questions/213514/how-can-i-permanently-change-my-hotspot-tethering-ip-address
Personally, I use the first method and it is enough for my needs.

It got even worse. I'm not sure this is a thing since Android 11, but whenever I turn my Hotspot off and on again, it changes the last two segments of my gateway IP, so it's always 192.168.x.x. This sucks even twice, because now all static IPs of all clients need to be updated to get in the right scope for the subnet mask that is still 255.255.255.0.
Pretty ****ty move by Google. I wish there was a solution to this nonsense. I want a static gateway IP without root ... (I know, impossible)

Cis# said:
It got even worse. I'm not sure this is a thing since Android 11, but whenever I turn my Hotspot off and on again, it changes the last two segments of my gateway IP, so it's always 192.168.x.x. This sucks even twice, because now all static IPs of all clients need to be updated to get in the right scope for the subnet mask that is still 255.255.255.0.
Pretty ****ty move by Google. I wish there was a solution to this nonsense. I want a static gateway IP without root ... (I know, impossible)
Click to expand...
Click to collapse
You said without root it's impossible but can we do something with root so that we don't have to update gateway ip everytime hotspot is restarted?

Cis# said:
It got even worse. I'm not sure this is a thing since Android 11, but whenever I turn my Hotspot off and on again, it changes the last two segments of my gateway IP, so it's always 192.168.x.x. This sucks even twice, because now all static IPs of all clients need to be updated to get in the right scope for the subnet mask that is still 255.255.255.0.
Pretty ****ty move by Google. I wish there was a solution to this nonsense. I want a static gateway IP without root ... (I know, impossible)
Click to expand...
Click to collapse
Faced the same problem after my mobile got an update to Android 11.
Please let me know if you found any solution.

byquip said:
Faced the same problem after my mobile got an update to Android 11.
Please let me know if you found any solution.
Click to expand...
Click to collapse
legendofrj10 said:
You said without root it's impossible but can we do something with root so that we don't have to update gateway ip everytime hotspot is restarted?
Click to expand...
Click to collapse
I got close...used MacroDroid with root (Magisk) and I was able to create a macro that started the hotspot and then used secure settings to set the wlan0 IP to what I wanted using ifconfig. Using both ifconfig and a network scanner I confirmed the hotspot had the ip I wanted, but I was not able to actually use it for a stable connection - clients constantly dropped the connection.

I'm still on Android 8.1 beacause of this random hotspot IP address issue.
Is there any recent phone or ROM with a static IP address for its hotspot?

Not really THE solution, but I've had pretty good results serving data thru the phones hotspot to an old dd wrt router (set up as a "repeater bridge"). The router/repeater handles all traffic on a local network then looks to the hotspot for data. Basically, just like your home wifi, but swap your modem with the phone.
Behind the router, it functions like a "real" connection. All apps function, push notices come thru, smart TVs, and even Chromecast works! You can assign static IP on the virtual network.
Devices don't seem to notice the random IP changes between the hotspot and router. At the most, you may lose data for a second or two while it .. switches stuff? Idk... but other than a quick lag in chat, if that, you won't even notice anything happened.
A couple sidebars:
The old wifi b/g routers with ddwrt are cheap on ebay. Although, router throughput could be a limiting factor on network speeds. Not just the older wifi protocols, but running repeater mode sets router to half duplex.
With a lot of the older routers, a USB-to-5v cable works to power it from any USB port (charger, battery pack, accessory port). Ideal for hotel/dorm, work, rural or mobile living. Wherever you need a private, fully functional wifi connection.
In dd wrt setup, follow tutorials for repeater bridge setup, but leave the gateway and dns ip blank (all zeros).
Naturally, speed and ping depends on the cellphones signal strength.

I don’t have an Android phone any more, but I noticed on my family’s Pixels, PDANet gave gives out a consistent 192.168.1.XXX address. PDANet hotspots work like regular hotspots as far as I know, so it might be worth a shot for when you’re on the go without a router to use.

DMechnikov said:
I don’t have an Android phone any more, but I noticed on my family’s Pixels, PDANet gave gives out a consistent 192.168.1.XXX address. PDANet hotspots work like regular hotspots as far as I know, so it might be worth a shot for when you’re on the go without a router to use.
Click to expand...
Click to collapse
Good to know. I didn't even know pdanet was still around. I'll have to mess with it sometime and see what's up. It would be nice to have a static IP coming from the phone, just cause.
Are you talking about the free or a paid version (if there are still two versions)??
Right now I'm using a rooted Umidigi A7 Pro with a 'hotspot unlock' magisk module, coupled with the VPN Hotspot app. This setup allows me to have unlimited hotspot data, I believe stops reporting of hotspot activity back to the ISP, while tunneling the hotspot data thru my phone's VPN connection.
I live waaay out in the sticks of West Virginia. My only ISP option at this time is Hughesnet satellite, which is just THE worst connection on the face of the planet, not to mention pricey. Speeds is so slow, and ping so high, you can't stream media, play games, or use it for voice or FaceTime chats. Instead, I use the phone setup mentioned above.
Luckily, there is a sprint tower (now T-Mobile) near enough to get a bar or two in the window. I picked up an 850mhz band5 cell booster / repeater (actually on band 26, which is a subsection if band 5). Got it set up, now can use the device in-hand throughout my home and out on the porches. Also helped improve speeds, reduce ping, and stabilize jitter on the LAN.
Call of duty mobile pings around 60-80ms
My Metro by T-Mobile plan is $40 per month, no data caps, but no hotspot allotment either. With the rooted device, I routinely use 200+ gb per month of hotspot data on devices connected via the router/repeater in my home.
I've been running this setup for nearly a year now and not had any problems from my ISP.

OP, you might want to look at this solution.

Still having the same issue in 2023 on LineageOS 18.1 (Android 11).
Can't find out which of these classes in sources is responsible for address allocation.

cilyrik said:
OP, you might want to look at this solution.
Click to expand...
Click to collapse
Hi,
After two days of trouble, (and multiples flahing operations, and many other concerns, I found a compromise with the solutions given in your link. Only the first one worked on my rooted smartphone (magisk + rom stock doogee s86pro). I did not manage to remount in rw my partitions to modify the hostapd.android.rc file. So I decided to use the automation (MacroDroid in my case) of the first solution. It works perfectly with 2 macros :
macro #1
trigger = hospot on
action = ip address add 192.168.43.1/24 dev wlan0
and
macro #2
trigger = hospot off
action = ip address del 192.168.43.1/24 dev wlan0
That's all. ^^
* rooted phone required *