wlan0 always selects same IP regardless of Router Assignment

[sun-tracker]

Hello all.

Having a strange issue with my wireless connection.

Upon first boot and rpi-config, the dongle I have connected just fine to my wifi network and (for whatever reason) chose the IP of 192.168.1.245. Connectivity is fine (eg web browsing).

I want to give it a static IP of 192.168.1.177, though, BUT I want to do it through my wifi router (Asus RT-N66U). Using the MAC address, I tell the router to assign the Pi a static IP of .177. The router accepts this command and upon reboot of both the router and the pi, the pi will ALWAYS take .245.
With any other mac/device on my network, static assignments work fine. I believe the problem is on the Pi's end -- what am I doing wrong and how can I get the pi to release it's obsession with the .245 IP?

Thanks.

-ST

[kusti8]

Post the contents of /etc/network/interfaces and /etc/wpa_supplicant/wpa_supplicant.conf

Remember to take out info like the SSID and the password.

[sun-tracker]

/etc/network/interfaces:

Code: Select all

auto lo

iface lo inet loopback
iface eth0 inet dhcp

allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp

/etc/wpa_supplicant/wpa_supplicant.conf:

Code: Select all

ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1

network={
ssid="OMITTED"
psk="OMITTED"
proto=RSN
key_mgmt=WPA-PSK
pairwise=TKIP
auth_alg=OPEN
}

Thanks for your help!
EDIT: I should add that all of the above was auto-generated by the wireless config GUI in Raspbian. I've not made any changes at all - I wanted the router to assign the IP instead of declaring it within the Pi.

[DougieLawson]

What range of addresses are defined as your DHCP pool on your router? Trim the range down so that it ends at 192.168.1.160 (that means 192.168.1.161 through to 192.168.1.254 can be assigned as static).

On my network I have the following

• xxx.yyy.1.1 to xxx.yyy.1.29 as static.
• xxx.yyy.1.30 to xxx.yyy.1.99 as DHCP
• xxx.yyy.1.100 to xxx.yyy.1.229 & xxx.yyy.1.231 to xxx.yyy.1.248 as unassigned
• xxx.yyy.1.230 & xxx.yyy.1.249 to xxx.yyy.1.252 are assigned for servers (WiFi AP, WiFi printer, NAS box, etc.).
• My router/gateway is at xxx.yyy.1.1.
• My Ubuntu server is xxx.yyy.1.4
• My RPi (called Pi) is at xxx.yyy.1.7, My 2nd RPi (called Raspberry) is at xxx.yyy.1.27
• My smart-tv is at xxx.yyy.1.5

The only time my DHCP range was exhausted was when I discovered a bug in isc-dhcp-client when you disconnect the ethernet cable from the Raspberry Pi. Seventy addresses is more than enough for the laptops, tablets and smart phones.

If you come and visit you can have my WiFi password (I can give you a QR code to scan) after I've read out the rules.

[emgi]

Hello all.

Having a strange issue with my wireless connection.

Upon first boot and rpi-config, the dongle I have connected just fine to my wifi network and (for whatever reason) chose the IP of 192.168.1.245. Connectivity is fine (eg web browsing).

I want to give it a static IP of 192.168.1.177, though, BUT I want to do it through my wifi router (Asus RT-N66U). Using the MAC address, I tell the router to assign the Pi a static IP of .177. The router accepts this command and upon reboot of both the router and the pi, the pi will ALWAYS take .245.
With any other mac/device on my network, static assignments work fine. I believe the problem is on the Pi's end -- what am I doing wrong and how can I get the pi to release it's obsession with the .245 IP?

Thanks.

-ST

This is a typical DHCP issue and I do not believe this problem to be with the Pi.
Please verify that you are indeed using the correct mac address for the static entry in your router.
You know wlan0 has a different mac than eth0 .
Of course a typo is also possible.

/emgi

[sun-tracker]

I did ensure the MAC addresses were correct.
Due to another unrelated problem, I ended up having to reflash a clean copy of Raspbian and so also resolved the issue I was having with IP assignment. As soon as the refreshed pi connected to my network on its first boot, it was assigned the right IP.. so I think there was something screwy going on with the Pi, but I'll never know for sure. Thanks for the help anyway!

[rpdom]

When the dchp client gets given an IP address it logs it in /var/lib/dhcp/dhclient.wlan0.leases (for wlan0). You can look at the contents of this file, it is plain text, and look at the "expire" time and date of the current lease. If that time is in the future, the dhcp client will say to the server "Hey, I had this IP last time, can I have it again?". The server will see that no one else is using it and say "OK", as it know things don't always like their IP address changing all the time.

At least, that is what I have seen happen on occasions.

If you stop the interface then delete that file and restart the interface it should pick up the new IP.

[Cancelor]

/etc/network/interfaces:

Code: Select all

auto lo

iface lo inet loopback
iface eth0 inet dhcp

allow-hotplug wlan0
iface wlan0 inet manual
wpa-roam /etc/wpa_supplicant/wpa_supplicant.conf
iface default inet dhcp

......

What does the 'iface wlan0 inet manual' do?

[DougieLawson]

iface wlan inet manual
means that some external process (external to network-manager) will set up the interface. In this case it's wpa_supplicant that does that.

wpa_supplicant does the association with the access point and the WEP, WPA, WPA2 security handshake. When that is complete the network interface is marked UP and it will do a DHCPDISCOVER to get an address assigned from the DHCP server.

[pluggy]

I never understood the fascination with using DHCP and wanting a static IP address, just give it a static IP and stuff the router....

[rpdom]

I never understood the fascination with using DHCP and wanting a static IP address, just give it a static IP and stuff the router....

Well, for one thing when at home I always get the same IP address, which allows me certain access levels to things on my network that other IP addresses don't have.

Yes, I could do that with a static IP, but when I'm not at home, using someone else's network, my static address would be wrong for their network. For that I need DHCP. After all, it's not just the IP address, it's also the nameserver, gateway, ntp server and maybe more.

My DHCP server (I don't use the one in the router) works on hostname instead of MAC, which is handy when I just grab the nearest network adaptor and plug it in to whichever computer I'm using at the time