My GL-MT6000 router sees the PC as a wired client and issued its static IP, but I cannot ping the PC from any other computer on the same network.

If Fedora sets up some kind of firewall by default, might eat pings, dunno.

I can’t diagnose this from just that, but sounds like you may be familiar enough with networking and just need the Linux commands to gather data and affect the system. This isn’t just a list of commands to run, and then report back, but a small toolbox of network diagnostic tools that I’ve used over the years:

Useful commands:

$ nmcli

I don’t know if this is installed on Fedora by default, but it talks to the “high level” NetworkManager system, displays information about the current network status.

$ ip link

Show list of network interfaces your computer recognizes. If it wasn’t able to recognize and set up your hardware, it’ll be missing here.

$ ip addr

See the addresses on those interfaces. If you were able to get a DHCP address from the router, it should show up here, it should show up here.

$ ip route

Shows your routing table, normally set up after the DHCP server on the router gives you an IP address. Should probably have an entry for your router, a “default route” via the IP of your router and via the interface connected to it.

$ ip stats

Shows statistics on your network interfaces. The packet counters here (“RX” for received, “TX” for transmitted) will let you see whether your interfaces are having packets being sent and received.

$ ping 8.8.8.8

Try to ping Google’s nameserver. If you get a response, you’ve got network access. If it says something like “no route”, then your desktop doesn’t believe it has an IP.

After pinging (or doing anything else that tries to use the network), as root:

# arp -an

Run this one as root. Dumps the ARP cache. When trying to talk to another device on the Ethernet, the first step is to send out an ARP request for that IP address, then populate the ARP cache with the response. When talking to the Internet, you normally contact your next-too router via IP. If you can do any IP traffic at all, you should have an entry here for your router showing its IP address.

# iptables -L

Run this one as root. Dumps your iptables rules. If you have some kind of firewall in place, it’ll be using iptables rules internally to tell the kernel what to let through.

# iptables -F

Run this one as root. Wipes out all the iptables rules (this is a transient change, will be reapplied when you next boot or run software that creates them or whatever). If a firewall is blocking anything, this’ll get it out of the way temporarily. Keep in mind that if your router is set up to forward any non-NATted Internet traffic directly to your desktop (not normally how things work), this will expose an unfirewalled system to the Internet.

# dhclient <interface name>

Run as root. This will run a common — and I think what Fedora uses — DHCP client to obtain an IP address and set up the routing tables. Shouldn’t normally need to run this directly, won’t coordinate with NetworkManager which will itself try to run dhclient, but if NetworkManager is totally hosed, this can get you a usable network.

# journalctl -kb

Run as root. Show all the kernel log messages for the current boot. You might find interesting errors.

# tcpdump -i <interface name>

Run as root. Will show you each packet arriving on a given interface. Not sure if installed by default on Fedora.

# service networking restart

Run as root. I’m very out of date on Fedora, but if it provides SysV init compatibility commands, I believe that this should try to shut down and bring up all of the networking stuff using your config. Might be “network” instead of “networking” on Fedora.

# ethtool -i <interface name>

Run as root. Lists some information about network interfaces. Mostly interesting, in my experience, to grab the “driver”, the associated kernel module that drives the interface.

# lsmod

Run as root. Shows loaded kernel drivers.

# lspci -v

Run as root. Shows technical information about your NICs. Useful for identifying which driver should be used. If you were using a USB NIC, lsusb instead.

Stuff under /sys/class/net

Information about your network interfaces.