FC 25 , Can't start nework service
 

I am not able to start network service in Fedora 25
even I have disabled NetworkManager service but not yet starting
any clue ?
I am using a wireless network interface
The reason I am doing thais is that I am trying to give the wireless etwork card a fixed IP address and although I tried many times , it always ignores the fixed address and gets the one from the DHCP

What errors do you get? Not enough information in your post.
Maybe look at these:
https://forums.fedoraforum.org/showt...t-in-Fedora-24
https://ask.fedoraproject.org/en/que...art-fedora-29/
or FC25 docs?

Job for network.service failed because the control process exited with error code.
See "systemctl status network.service" and "journalctl -xe" for details.

This is the error that I get

Tried to kill dhcp process as described in this link https://forums.fedoraforum.org/showt...t-in-Fedora-24 , did not work

So, what is the output of those commands?

Apr 02 15:54:16 machine_name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine_name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine_name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine_name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine_name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine_name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine_name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine_name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine_name systemd-sysctl[9580]: Couldn't write '0' to 'net/bridge/bridge-nf-call-arptables', ignoring: No such file or directory
Apr 02 15:54:16 machine_name systemd-sysctl[9580]: Couldn't write '0' to 'net/bridge/bridge-nf-call-iptables', ignoring: No such file or directory
Apr 02 15:54:16 machine_name systemd-sysctl[9580]: Couldn't write '0' to 'net/bridge/bridge-nf-call-ip6tables', ignoring: No such file or directory
Apr 02 15:54:16 machine_name systemd[1]: network.service: Control process exited, code=exited status=1
Apr 02 15:54:16 machine_name systemd[1]: Failed to start LSB: Bring up/down networking.
-- Subject: Unit network.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman.../systemd-devel
--
-- Unit network.service has failed.
--
-- The result is failed.
Apr 02 15:54:16 machine_name audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=network comm="systemd" exe="/usr/lib/systemd/sy
Apr 02 15:54:16 machine_name systemd[1]: network.service: Unit entered failed state.


systemctl status network.service returns the following
"job for network.service failed because the control process exited with error code."

system staus network returns

Apr 02 15:54:16 machine-name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine-name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine-name network[9193]: RTNETLINK answers: File exists
Apr 02 15:54:16 machine-name systemd-sysctl[9580]: Couldn't write '0' to 'net/bridge/bridge-nf-call-arptables', ignoring: No such file or directory
Apr 02 15:54:16 machine-name systemd-sysctl[9580]: Couldn't write '0' to 'net/bridge/bridge-nf-call-iptables', ignoring: No such file or directory
Apr 02 15:54:16 machine-name systemd-sysctl[9580]: Couldn't write '0' to 'net/bridge/bridge-nf-call-ip6tables', ignoring: No such file or directory
Apr 02 15:54:16 machine-name systemd[1]: network.service: Control process exited, code=exited status=1
Apr 02 15:54:16 machine-name systemd[1]: Failed to start LSB: Bring up/down networking.
Apr 02 15:54:16 machine-name systemd[1]: network.service: Unit entered failed state.
Apr 02 15:54:16 machine-name systemd[1]: network.service: Failed with result 'exit-code'.

Did you manually changed/added a route?
https://www.linuxquestions.org/quest...-rhel5-710766/

Nop