[SOLVED] Fedora 19 and networking

Galaxy_Stranger · 08-22-2013, 07:16 PM

I just installed Fedora 19 the other day. It installed fine, but I'm having network problems.

I'm not getting any network connection at all. It sees the network adapters, but the one that's plugged-in says it's "not connected". I figured this might be a common issue, so I poked around the ethernets and started going through the steps on this page. Then I found I had no /etc/sysconfig/network-scripts/ifcfg-ens33 file at all and don't know how to generate one.

Ultimately, I'd like to just configure it with an IPv4 static IP. What should I do to troubleshoot this?

TIA.

lleb · 08-22-2013, 07:42 PM

hello, simple enough. manually create it, but this is really odd for F19.

Code:

DEVICE="eth4"
TYPE="Ethernet"
NAME="System eth4"
ONBOOT="yes"
#BOOTPROTO="dhcp"
BOOTPROTO="static"
NM_CONTROLLED="no"
IPADDR=192.168.222.222
NETMASK=255.255.255.0
USERCTL="no"
IPV4_FAILURE_FATAL=yes
IPV6INIT=no

This is for my 5th NIC on my server, but the basic layout is the same no matter what for any RH distro, that includes F19.

you can use gedit, nano, vi, what ever to edit the file and poof off you go.

you might also want to try the GUI configuration tool for Gnome and manually configure the static there as it will create the ifcfg-eth# file for you as well as restart the network service:

Code:

#systemclt network restart

i believe is the new command, but you can also use the older

Code:

# service network restart

just as well for now at least.

Galaxy_Stranger · 08-22-2013, 09:37 PM

ooookeeeeee...

First of all - thanks for the reply and info. Everything works so far. This is what happened:

I'm using KDE and had originaly clicked on the GUI app to configure the network adapter. There were zero options for configuring either of my on-board ethernet chipsets. That's what I've done in the past when Fedora decides not to play nice and it usually works. This time I had to poke around and start this post.

IFCONFIG looks thus:

Code:

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 0  (Local Loopback)
        RX packets 856  bytes 68368 (66.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 856  bytes 68368 (66.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

p12p1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 00:22:6b:c4:58:cd  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

p7p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet6 fe80::1e6f:65ff:fe96:a28a  prefixlen 64  scopeid 0x20<link>
        ether 1c:6f:65:96:a2:8a  txqueuelen 1000  (Ethernet)
        RX packets 26444  bytes 38089094 (36.3 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 14189  bytes 979173 (956.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

p9p1: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 1c:6f:65:95:a8:df  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

So, I started creating the file as described and began puting in the info. At this point, I decided to look at the gui again, so I clicked on the ethernet port icon and noticed that it had listed an item that was labeled "enp4so". I was intrigued. I clicked it. BOOM - I have network access...

I stopped creating the file and looked in the directory - and "ifcfg-ens33" had not been created. Then I noticed that there was a big, fat "ifcfg-enp4s0" file... So I opened it up and looked at it and it said, "ONBOOT=no". So, I change this to "yes" and reboot to check - and I have network access. Ifconfig modifies this:

Code:

p7p1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.113  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::1e6f:65ff:fe96:a28a  prefixlen 64  scopeid 0x20<link>
        ether 1c:6f:65:96:a2:8a  txqueuelen 1000  (Ethernet)
        RX packets 26426  bytes 38087958 (36.3 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 14180  bytes 978459 (955.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

I presume "ifcfg-ens33" describes a specific network adapter. I have no idea what these different files are used for, but whatever - I'll take it. This is not the first time Fedora has decided not to activate my network adapter on boot and this really honks me off. The live CD was fine - why would the installation do this?

Anyway, thanks for the help.

lleb · 08-23-2013, 08:57 AM

nice glad that worked. for some reason if during the install Anaconda can not detect your NIC it will set all the configuration files to ONBOOT="no" last i read this was resolved back in F17, so it might not be a bad idea to file a bug report to the fedora team making sure to mention with as much detail as you can what caused the problem as well as the GUI/kernel/etc... and how you resolved the issue.