Ask Your Question
0

Fedora 24 doesn't work network connection

asked 2016-10-05 19:13:35 -0500

krchat gravatar image

updated 2016-10-05 21:37:32 -0500

http://www.forums.fedoraforum.org/sho...

Use static IP, mask/24 192.168.0.2 gateway - 192.168.0.1 DNS servers - OpenDNS servers - manual Don't pass ping from host to gateway. 192.168.0.2 - 192.168.0.1 systemctl status; start; enable network - OK Ip addr - OK; Ifup ifdown - OK systemctl status; start; enable NetworkManager - OK But network doesn't work. What's wrong? How does check it?

Just fancy, I don't know what's the matter. I downloaded Fedora Live CD - the net connection wasn't too. Then I decided to check up my network card and run Windows 10. OS updated a little bit and network run well. So, I downloaded into Fedora again. Now network works well. That's very strange situation. I made some settings in Windows OS. I set network doesn't wake up system, but I don't know if soft or hardware problem in Windows OS switch off Ethernet card for Linux OS

edit retag flag offensive close merge delete

Comments

First, check the physical connection on both ends of the cable, there should be a static green and a blinking orange light somewhere near the RJ45 port of your ethernet adapter, then post your output of ifconfig -a

jake gravatar imagejake ( 2016-10-06 00:56:51 -0500 )edit

Also show output from ethtool *interface*. Direct connection to gateway or through a switch?

raconteur gravatar imageraconteur ( 2016-10-06 10:28:02 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2016-10-06 06:55:58 -0500

krchat gravatar image

updated 2016-10-07 02:54:00 -0500

I don't know what was it, but now is all work right. Yes, physical connection was OK, Router and Ethernet card was a static green.

The problem was in network card settings. And today it repeated. So, I went to Windows 10 and set my Ethernet card setting - not allowed sleep, and wake up. I'd like to know how can I turn my network card in Linix without setting in Windows?

There are two logins, 1 before enter to Windows and set my Ethernet card and the another one is after relog in Linux

`--- 192.168.0.1 ping statistics --- 3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2000ms pipe 3 [stan@localhost ~]$ [stan@localhost ~]$ ifconfig -a enp3s1: flags=4163<up,broadcast,running,multicast> mtu 1500 inet 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::eade:27ff:fe03:63c prefixlen 64 scopeid 0x20<link> ether e8:de:27:03:06:3c txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 295 bytes 15238 (14.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<up,loopback,running> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 283 bytes 27800 (27.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 283 bytes 27800 (27.1 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

the Second log:

stan@localhost ~]$ ifconfig -a enp3s1: flags=4163<up,broadcast,running,multicast> mtu 1500 inet 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::eade:27ff:fe03:63c prefixlen 64 scopeid 0x20<link> ether e8:de:27:03:06:3c txqueuelen 1000 (Ethernet) RX packets 160 bytes 15342 (14.9 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 151 bytes 13622 (13.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<up,loopback,running> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1 (Local Loopback) RX packets 16 bytes 1392 (1.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 16 bytes 1392 (1.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0`

That's answer for this problem:

Realtek no link / WOL problem

Users with Realtek 8168 8169 8101 8111(C) based NICs (cards / and on-board) may notice a problem where the NIC seems to be disabled on boot and has no Link light. This can usually be found on a dual boot system where Windows is also installed. It seems that using the offical Realtek drivers (dated anything after May 2007) under Windows is the cause. These newer ... (more)

edit flag offensive delete link more

Comments

Those log excerpts you included are very hard to read. Consider using a fixed formatting when attaching log or terminal output.

raconteur gravatar imageraconteur ( 2016-10-12 21:34:05 -0500 )edit

Question Tools

Stats

Asked: 2016-10-05 19:13:35 -0500

Seen: 642 times

Last updated: Oct 07 '16