Can't assign a static IP to Pixel 3 - Android Q&A, Help & Troubleshooting

I want all devices on my home network to have static IPs. I entered my Pixel 3's wifi MAC address into the router settings to reserve an IP for it. However, the Pixel seems to ignore that assignment and just grabs the next available IP via DHCP using a different MAC address. I am guessing this has something to do with randomized MAC addresses turned on in Android settings.
Is it possible to keep randomized MAC addresses on and still have static IPs work correctly?

Related

DNS Problems After Bell 2.3.4 Update

So when I was using 2.2.2 my WIFI connection was working flawlessly with DHCP setting my wireless settings.
I flashed 2.3.4 using NFHimself's Gobstopper without any errors, did a factory reset afterwards and I get an internet connection over mobile with no problems, however on my home WIFI network w/ DHCP (on which 2.2.2 worked fine), it cannot resolve addresses past my router (can browse to the router config fine). Now if I set a static IP and the DNS servers manually, it works over WIFI, however when the WIFI radio turns back on from sleeping it gets stuck at obtaining an IP address.
So I tried leaving it with DHCP giving me an IP address, and then using Set DNS to use google's DNS servers instead of my router's IP, and it seems to work in all situations, however it leaves me unable to browse my LAN (even when one dns domain is left as my local domain server).
I installed Network Monitor II to watch my wireless settings for the three setups:
For just using DHCP, the DNS servers are both set to my router's IP
For static settings, the DNS servers are whatever i set them however i cannot browse my LAN when one is left as my router's IP
For DHCP w/ a custom DNS, it is the same as using static settings
Not sure whether to think this is a problem with the update, or a problem with my router (however no settings were changed before or after the update on it). Anyone have any ideas?
Router: Linksys WRT54GL running DD-WRT
I read somewhere that having the "Filter WAN NAT Redirection" setting enabled in DD-WRT causes this sort of behavior on some mobiles, it is not enabled.
Only thing I could find that I thought it might be is Android Bug Issue 10315 (to which I cannot post a link as I lack sufficient posts... so far), but am still unsure
I should also note that I have two routers (both identical), but only one deals with the DHCP and DNS, the other is more just a wireless AP. Thus, all of my lan is on 192.168.1.*, including both routers ( x.x.x.1 and x.x.x.2 ). uDHCPd is my DNS server on my router, but I might try dnsmasq in the next couple days.
Jiraffe said:
So when I was using 2.2.2 my WIFI connection was working flawlessly with DHCP setting my wireless settings.
I flashed 2.3.4 using NFHimself's Gobstopper without any errors, did a factory reset afterwards and I get an internet connection over mobile with no problems, however on my home WIFI network w/ DHCP (on which 2.2.2 worked fine), it cannot resolve addresses past my router (can browse to the router config fine). Now if I set a static IP and the DNS servers manually, it works over WIFI, however when the WIFI radio turns back on from sleeping it gets stuck at obtaining an IP address.
So I tried leaving it with DHCP giving me an IP address, and then using Set DNS to use google's DNS servers instead of my router's IP, and it seems to work in all situations, however it leaves me unable to browse my LAN (even when one dns domain is left as my local domain server).
I installed Network Monitor II to watch my wireless settings for the three setups:
For just using DHCP, the DNS servers are both set to my router's IP
For static settings, the DNS servers are whatever i set them however i cannot browse my LAN when one is left as my router's IP
For DHCP w/ a custom DNS, it is the same as using static settings
Not sure whether to think this is a problem with the update, or a problem with my router (however no settings were changed before or after the update on it). Anyone have any ideas?
Router: Linksys WRT54GL running DD-WRT
I read somewhere that having the "Filter WAN NAT Redirection" setting enabled in DD-WRT causes this sort of behavior on some mobiles, it is not enabled.
Only thing I could find that I thought it might be is Android Bug Issue 10315 (to which I cannot post a link as I lack sufficient posts... so far), but am still unsure
I should also note that I have two routers (both identical), but only one deals with the DHCP and DNS, the other is more just a wireless AP. Thus, all of my lan is on 192.168.1.*, including both routers ( x.x.x.1 and x.x.x.2 ). uDHCPd is my DNS server on my router, but I might try dnsmasq in the next couple days.
Click to expand...
Click to collapse
I did flash NFHimself's ROM without any issues. My wireless LAN was working fine. Did not noticed any issue on my side. Try with another Wireless router without all the setup you've done. Pretty sure the issue is with your routers.
I don't understand why you are not able to reach you LAN with google's DNS configured...? Do you have some sort of DNS entry specific to your LAN configured into your router?
the problem seemed to solve itself when i switched my router's DNS server daemon from UDHCPD to dnsmasq.
And I couldn't reach my lan when i had both dns servers forced to google's servers as google's servers don't know how to route to addresses inside my lan. But that's not a bug, that is how it is supposed to work.
Good !
Sent from my MB860 using xda premium

[Q] WiFi: DHCP request although static IP configured

I face a strange behavior while connecting to WiFi.
When I configure the WiFi settings to use a static IP at home with a Speedport router from Telekom everything works fine. I get a connection imediately. (Security credentials are WPA2-PSK/AES).
But when I try to connect to a Cisco environment (1142 access points with 5508 controller with the same security credentials as at home) after PSK authentication the phone start with DHCP requests instead of using the configured static IP and I don't get a connection.
First I thought it was of the ROM or the device but I tried different ROMs (stocks and customs) and different devices (Defy and Galaxy S). Everytime the same thing.
A laptop or an iPhone can connect without any problem using a static IP.
It seems that the controller or AP sends something to the phone telling it to ignore the staic IP settings...
Strange!!!

[Q] Droid X2 stuck on Obtaining Ip Address WIFI issue [SOLVED]

This has been plaguing me for a few days now and I just want to share the solution I found for you guys. Have you ever had this issue? Your selected wireless network has been working great for days and suddenly one day it refuses to connect anymore. I would hit connect and the phone would be stuck in a "Obtaining IP address from WIFINETWORK" "Disconnected" "Scanning" cycle and so forth. You can wait forever and the phone will never connect to wifi.
The first time this happened to me I did a hard reset. Worked like a charm, I was able to use the network again for a few days until it began happening again. I decided a reset was not the solution so I looked for an answer. I happened upon sites like this:
http://anxiousnut.wordpress.com/201...d-obtaining-ip-address-wifi-issue-workaround/
Where certain solutions were posted but none seemed to work for me. I decided that it definitely wasn't my router (although some said resetting your wireless router may also work sometimes).
I finally stumbled upon the answer. The solution is to use a static ip by going into to Settings>Wireless & Networks>Wi-Fi settings>Menu Click to Advanced and then check Use static IP. You must figure out these values: IP Address, Gateway, Netmask, DNS 1, DNS 2.... Luckily, it is pretty easy.
IP ADDRESS
To find this, go back and select your wifi network. Hit "Modify" and see the IP address listed. Copy that down, this is your IP Address.
GATEWAY
This is your router's IP address. You will need a computer that is connected to the network already. For Windows, run a command prompt and type ipconfig to show you the default gateway address. For Mac, go to the network preference pane in system preferences. Click advanced and go to TCP/IP tab.
NETMASK
You will find this in the previous step. Often it is 255.255.255.0.
DNS 1
Put in the same IP you found for the gateway box.
DNS 2
Same as above.
In the end it will look something like this:
IP Address: 192.168.1.107
Gateway: 192.168.1.1
Netmask: 255.255.255.0
DNS 1: 192.168.1.1
DNS 2: 192.168.1.1
Connect again and it works. No need to factory reset. Enjoy!
Update: After a few days, something in the phone's wifi settings seem to "correct" itself and your wifi will not work with this method anymore. Simply go back and disable static IP and your phone will be back to its old self again. If the symptoms appear again, you can follow these steps again.
I wonder if this will help with eclipse 2.0.3 disconnecting issues
Sent from X2 Eclipsed using xda app
I was having this problem with CM7 and this fixed it. Thanks!
thanks solved my problem i m so very grateful
Careful, this "fix" could be very temporary... If you set a static IP and do not configure your router to use static IPs you will at some point run into conflicting IPs if you have other devices on the network. The router is dynamically allocating IP addresses if you use a standard DHCP setup and can give your chosen IP for your phone to any device on the network, creating a situation when you cannot connect or you can connect but it does not work. If you want to use static ips on your phone with the router, you have to configure the router to understand this by disabling DHCP and setting up static IPs for all devices or by allocating fixed IP for certain MAC addresses. SO either setup both your phone and router to use a static IP or change the DHCP lease time to something other than "infinity" .
Most routers strart DHCP allocation at .100. Check with your particular routers manual. If you assign the IP less than .100 you should be fine as long as you don't assign another device with the same IP.
Sent from my MB870 using Tapatalk 2
A workaround != A fix.
DigitalMD said:
Careful, this "fix" could be very temporary... If you set a static IP and do not configure your router to use static IPs you will at some point run into conflicting IPs if you have other devices on the network.
Click to expand...
Click to collapse
I'm with DigitalMD - this is a very kludgy "fix" that will lead to trouble in the future. I am coming to believe there is a consistent interoperability issue between Android and some other systems (OS X and some routers??) that leads to issues - both my GN with 4.0.4 and my JetStream with 3.1 will routinely fail to connect both to my Mac (10.7) and the routers, primarily in a couple of particular offices - maybe it's just a high-noise area (one is an older building). The devices both connect fine to my home wifi (WRT54G) and most internet cafes.
Not a good fix
This isn't really a fix for the problem. I connect to multiple wireless networks, between work and home and friend's houses, and they all have different routers. Setting a static IP is impractical, because I have to turn it on with certain networks and off with other networks, or change the static IP from one router to another.
Why does this happen? It works fine for a while, then one day it just doesn't want to take an IP address from the router. For me, it works fine at home and at my parents, but at work, it doesn't want to connect anymore. It's been connecting fine for months, then yesterday it got stuck with obtaining IP.
Setting a static IP isn't a solution; it's a cop-out. Does anybody know why this happens? Does anybody know how to fix it?
I was experiencing this from past couple of days than I just put static IP works really great for me :laugh: it was a biggest headache, now past.

Changing Android i.p. address (Help)

My school recently blocked my i.p. address from trying too connect to the WiFi. Is thier any way to get back on or change my i.p.
My device is Lg Leon Android lollipop
Blocked not ip
They can not block IP address, because DHCP server give IP address to device, and you can always change your IP in WiFi settings. They block your MAC address. This is unique value on each WiFi device. So, you must change MAC address, but it is not possible for all device (my phone do not support).
Are you sure that they blocked you? May be DHCP server have not free IP addresses or Internet was disabled.
And... may be school enable MAC filtering and WiFi allows to connect only teacher's devices. So you must to know MAC address one of the teacher's devices. But this is another story with airmon and social engineering
If they are smart they will do what I did for my sons schools. And run a static ip on all approved devices and then make as stated above use Mac filtering. More and more schools are banning the use of personal devices and to be honest I agree with it.

Trying to understand the source of WiFi DNS

All,
I am aware of the various apps for changing DNS server settings - that is not the question. I would like someone to explain how the default values are being set.
My home wireless access point supports three SSIDs and I have SSID_1 bridged to my router. Within the router, I have defined 1.1.1.1 and 208.67.222.222 as my DNS servers. When my phone (Pixe3 3XL) is connected to SSID_1, however, it shows the DNS servers as being 8.8.8.8 and 64.6.64.6. (FYI - I just rebooted my router in case that might have an impact, but ti didn't.)
However, when my phone connects to SSID_2, which is not bridged to the router, the DNS shows up as 10.255.224.1, which is the gateway address.
Oddly, my desktop PC, which gets it IP via DHCP (the address is reserved) and was configured for automatic CNS, also showed the DNS servers as being 8.8.8.8 and 64.6.64.6.
I logged into my cable modem, but there are no user adjustable settings there.
So, from whence come these DNS IP addresses?

Categories

Resources