Static IP for a wireless box

NotionCommotion · 07-30-2017, 11:10 AM

Desire a static IP on a wireless Centos6 box. I set it up as such, and it sticks for a while, then I get up in the morning and it has reverted back to another IP. How can I prevent it from changing? Thanks

Code:

[Michael@devserver ~]$ ifconfig
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:42164 errors:0 dropped:0 overruns:0 frame:0
          TX packets:42164 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:9035715 (8.6 MiB)  TX bytes:9035715 (8.6 MiB)

wlan0     Link encap:Ethernet  HWaddr B8:76:3F:69:31:95
          inet addr:192.168.1.140  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::ba76:3fff:fe69:3195/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2569632 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1948026 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:293819716 (280.2 MiB)  TX bytes:225579123 (215.1 MiB)

[Michael@devserver ~]$ cat /etc/sysconfig/network
NETWORKING=yes
HOSTNAME=devserver.michaels.lan
[Michael@devserver ~]$ cat /etc/resolv.conf
search michaels.lan hsd1.wa.comcast.net
nameserver 192.168.1.1
nameserver 8.8.8.8
nameserver 8.8.4.4
[Michael@devserver ~]$ cat /etc/hosts
127.0.0.1       localhost.localdomain   localhost.localdomain   localhost4      localhost4.localdomain4 localhost       devserver
::1     localhost.localdomain   localhost.localdomain   localhost6      localhost6.localdomain6 localhost       devserver
[Michael@devserver ~]$ cat /etc/sysconfig/network-scripts/ifcfg-wlan0
# Please read /usr/share/doc/initscripts-*/sysconfig.txt
# for the documentation of these parameters.
GATEWAY=192.168.1.1
DEVICE=wlan0
BOOTPROTO=none
NETMASK=255.255.255.0
#TYPE=Ethernet
TYPE=wireless
HWADDR=b8:76:3f:69:31:95
IPADDR=192.168.1.10
NM_CONTROLLED=no
ONBOOT=yes
PEERDNS=no
IPV6INIT=no
USERCTL=no
DNS2=8.8.4.4
DNS1=8.8.8.8
[Michael@devserver ~]$

beachboy2 · 07-30-2017, 11:19 AM

NotionCommotion,

https://unix.stackexchange.com/quest...-wifi-centos-7

NotionCommotion · 07-30-2017, 11:58 AM

Thanks beachboy2, but as shown in my original post, I've already done so. Note that my /etc/sysconfig/network-scripts/ifcfg-wlan0 additionally includes the following:

Code:

GATEWAY=192.168.1.1
TYPE=wireless
HWADDR=b8:76:3f:69:31:95
NM_CONTROLLED=no
PEERDNS=no
IPV6INIT=no
USERCTL=no
DNS2=8.8.4.4
DNS1=8.8.8.8

I think the issue might have nothing to do with the centos machine, but I think I forgot to setup my router with an IP range where it will accept self assigned IPs, and centos is forgoing its static ip to use a dhcp ip.. Strange though how centos will ignore its own static ip config to adapt to the routers assignment.

beachboy2 · 07-30-2017, 12:10 PM

NotionCommotion,

I must get my money back on that speed-reading course!

NotionCommotion · 07-30-2017, 12:25 PM

@Beachboy2, No worries, and thanks! One of the comments reminded me about dhcp reservations. Now, 192.168.1.10 sticks! Funny though, my router shows it having two IPs now where one is 192.168.1.140. Guess that is what I get for using static ips on wireless devices!

malekmustaq · 07-30-2017, 12:55 PM

___

NotionCommotion:

Should the problem recur, take this note.

-----
1. NM must control the IP to peg it in one static IP value, to avoid the manager behaving like an idiot

on-call it follows whatever the dhcp entices it to accept.
2. Control the IPs from the dhcp side (usually the router) login to it and bind
HWADDR=b8:76:3f:69:31:95 to IP # 192.168.1.xxx (whatever you like.)
Refresh the network script (restart)
Refresh the dhcp as well.

Hope that helps. Good luck.

m.m.

NotionCommotion · 07-30-2017, 10:46 PM

Yes helpful, nm is network manager? How do I keep behaving like a whore?

rtmistler · 07-31-2017, 07:34 AM

NotionCommotion:

malekmustag:

Per the LQ Rules, Do not post any messages that are obscene, vulgar, sexually-orientated, hateful, threatening, hostile or insulting.

While I realize there are worse words for one to post, I also fail to see any reference towards this subject.

Please stay on topic and even if self admonishing yourself, please do not bring the conversation to a level violating the LQ rule cited.

EDIT: I incorrectly noted NotionCommotion's comment failing to realize malekmustag's comment. Apologies.

NotionCommotion · 07-31-2017, 09:03 AM

@rtmistler, Understood. And while I fully agree LQ Rules are appropriate and I would never wish to promote any of the negative qualities which they are meant to prevent, I must say the use of the word does have reference.

rtmistler · 07-31-2017, 09:10 AM

Quote:

Originally Posted by NotionCommotion

@rtmistler, Understood. And while I fully agree LQ Rules are appropriate and I would never wish to promote any of the negative qualities which they are meant to prevent, I must say the use of the word does have reference.

You are quite correct, apologies.

malekmustag:

Please find more appropriate means to describe software behavior.

As you can see, another member possibly felt that this comment was personally directed versus meant to describe software.

malekmustaq · 08-01-2017, 08:53 AM

Quote:

As you can see, another member possibly felt that this comment was personally directed versus meant to describe software.

Yes Mod. My sincere apology.

I really had that same problem once and I yelled at my NM (Network Manager) for behaving that way, it follows whatever wherever the dhcp took it. After a sober moment I realized it was my mistake for letting her be.

Again, NotionCommotion my post was about the "NM" network manager. There is no way a good english user shall mistake the subject and predicate.

Did it help? Please post freely again. Everyone here is eager to help.

Good luck.

m.m.

Rickkkk · 08-01-2017, 03:49 PM

I second the recommendation to use DHCP reservations for assigning specific IP addresses. It centralizes management, making it a lot simpler to make changes.

Cheers :-)