Starquest321
asked on
IP ADDR
I tried to change to a static IP address from working DHCP model. When I do a network restart I get the following:
service network restart
Restarting network (via systemctl): Job for network.service failed. See 'systemctl status network.service' and 'journalctl -xn' for details.
When I look for details:
Failed to start LSB: Bring up/down networking.
In my IP settings I have:
TYPE=Ethernet
BOOTPROTO=static
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=eno16777736
UUID=a68ce778-9b60-4ec5-a2 96-eb9ec2f e471a
ONBOOT=yes
HWADDR=00:0C:29:92:73:39
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPADDR=192.168.0.136
NETMASK=255.255.255.0
GATEWAY=192.168.0.1
If I reboot ... seems like I can SSH so somehow its getting the network IP right.
service network restart
Restarting network (via systemctl): Job for network.service failed. See 'systemctl status network.service' and 'journalctl -xn' for details.
When I look for details:
Failed to start LSB: Bring up/down networking.
In my IP settings I have:
TYPE=Ethernet
BOOTPROTO=static
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=eno16777736
UUID=a68ce778-9b60-4ec5-a2
ONBOOT=yes
HWADDR=00:0C:29:92:73:39
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPADDR=192.168.0.136
NETMASK=255.255.255.0
GATEWAY=192.168.0.1
If I reboot ... seems like I can SSH so somehow its getting the network IP right.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Now I updated:
Still error:
DEVICE="eno16777736"
TYPE=Ethernet
BOOTPROTO=NONE
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=eno16777736
UUID=a68ce778-9b60-4ec5-a2 96-eb9ec2f e471a
ONBOOT=yes
HWADDR=00:0C:29:92:73:39
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPADDR=192.168.0.136
NETMASK=255.255.255.0
GATEWAY=192.168.0.1
NM_CONTROLLED="no"
Still error:
DEVICE="eno16777736"
TYPE=Ethernet
BOOTPROTO=NONE
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
NAME=eno16777736
UUID=a68ce778-9b60-4ec5-a2
ONBOOT=yes
HWADDR=00:0C:29:92:73:39
PEERDNS=yes
PEERROUTES=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPADDR=192.168.0.136
NETMASK=255.255.255.0
GATEWAY=192.168.0.1
NM_CONTROLLED="no"
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
My device name is eno16777736 . . .so how can I just change to eno0?
Don't I need some other setup?
ifconfig
eno16777736: flags=4163<UP,BROADCAST,RU NNING,MULT ICAST> mtu 1500
inet 192.168.0.136 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fdbc:f108:fdb1:0:20c:29ff: fe95:4e17 prefixlen 64 scopeid 0x0<global>
inet6 fe80::20c:29ff:fe95:4e17 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:95:4e:17 txqueuelen 1000 (Ethernet)
RX packets 5101 bytes 2403674 (2.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3489 bytes 628597 (613.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNI NG> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 8 bytes 660 (660.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 660 (660.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Don't I need some other setup?
ifconfig
eno16777736: flags=4163<UP,BROADCAST,RU
inet 192.168.0.136 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fdbc:f108:fdb1:0:20c:29ff:
inet6 fe80::20c:29ff:fe95:4e17 prefixlen 64 scopeid 0x20<link>
ether 00:0c:29:95:4e:17 txqueuelen 1000 (Ethernet)
RX packets 5101 bytes 2403674 (2.2 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3489 bytes 628597 (613.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNI
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 8 bytes 660 (660.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 660 (660.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I followed this:
I hope NetworkManager is enabled
systemctl status NetworkManager.service
ps aux | grep -I net # will probably find NetworkManager still running.
chkconfig NetworkManager off
Then I did:
ifdown eno16777736
and then:
ifup eno16777736
Now I messed everything up:
I get on the ifup command:
The device eno16777736 has a different MAC address than expected, ignoring.
And I cannot SSH....
Urgent help
I hope NetworkManager is enabled
systemctl status NetworkManager.service
ps aux | grep -I net # will probably find NetworkManager still running.
chkconfig NetworkManager off
Then I did:
ifdown eno16777736
and then:
ifup eno16777736
Now I messed everything up:
I get on the ifup command:
The device eno16777736 has a different MAC address than expected, ignoring.
And I cannot SSH....
Urgent help
ASKER
This command messed me up:
chkconfig NetworkManager off
I had to turn it back on and revert changes...
But I am still on dynmic
chkconfig NetworkManager off
I had to turn it back on and revert changes...
But I am still on dynmic
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
service network restart
I get the error:
Failed to start LSB: Bring up/down networking.