Wired Network excessively slow

Issues related to configuring your network
Post Reply
ctwomey
Posts: 4
Joined: 2014/08/28 15:05:49

Wired Network excessively slow

Post by ctwomey » 2014/08/28 15:18:48

I have installed Centos7 on a spare box i had to use as a home server. This is a minimal install that so far has only a few utilities, plex media server, and samba installed. Since the first install i've noticed my download speeds are excessively slow at an average of 250 kb/s. I have run the command line speed test and it's reporting 1.7 Mbit for my download speed, when i run speed test on my windows machines i get 25+ consistently. I'm at a bit of a loss on what to do now, i've tried turning off ipv6 and that didn't seem to make any difference. I don't think this is an issue with the firewall because i'd expect to have no traffic period, SELinux does not appear to be reporting any messages either.

What can i do further to try and trouble shoot the problem?

My Network is:
Generic 2wire modem from isp
Asus RT-n66u router

Centos7 network config is:
Network adapters, i have disabled the wireless adapter and am using the ethernet adapter

Code: Select all

lspci -nn | grep -i net
02:00.0 Network controller [0280]: Qualcomm Atheros AR93xx Wireless Network Adapter [168c:0030] (rev 01)
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller 
nmcli output

Code: Select all

nmcli c show 9e5034b2-16c2-4989-86e8-c2345146aa73
connection.id:                          enp4s0
connection.uuid:                        9e5034b2-16c2-4989-86e8-c2345146aa73
connection.interface-name:              --
connection.type:                        802-3-ethernet
connection.autoconnect:                 yes
connection.timestamp:                   1409240347
connection.read-only:                   no
connection.permissions:
connection.zone:                        --
connection.master:                      --
connection.slave-type:                  --
connection.secondaries:
connection.gateway-ping-timeout:        0
802-3-ethernet.port:                    --
802-3-ethernet.speed:                   0
802-3-ethernet.duplex:                  --
802-3-ethernet.auto-negotiate:          yes
802-3-ethernet.mac-address:             1C:6F:65:A9:81:0B
802-3-ethernet.cloned-mac-address:      --
802-3-ethernet.mac-address-blacklist:
802-3-ethernet.mtu:                     auto
802-3-ethernet.s390-subchannels:
802-3-ethernet.s390-nettype:            --
802-3-ethernet.s390-options:
ipv4.method:                            auto
ipv4.dns:
ipv4.dns-search:
ipv4.addresses:
ipv4.routes:
ipv4.ignore-auto-routes:                no
ipv4.ignore-auto-dns:                   no
ipv4.dhcp-client-id:                    --
ipv4.dhcp-send-hostname:                yes
ipv4.dhcp-hostname:                     homeserver
ipv4.never-default:                     no
ipv4.may-fail:                          yes
ipv6.method:                            auto
ipv6.dns:
ipv6.dns-search:
ipv6.addresses:
ipv6.routes:
ipv6.ignore-auto-routes:                no
ipv6.ignore-auto-dns:                   no
ipv6.never-default:                     no
ipv6.may-fail:                          yes
ipv6.ip6-privacy:                       -1 (unknown)
ipv6.dhcp-hostname:                     homeserver
GENERAL.NAME:                           enp4s0
GENERAL.UUID:                           9e5034b2-16c2-4989-86e8-c2345146aa73
GENERAL.DEVICES:                        enp4s0
GENERAL.STATE:                          activated
GENERAL.DEFAULT:                        yes
GENERAL.DEFAULT6:                       no
GENERAL.VPN:                            no
GENERAL.ZONE:                           --
GENERAL.DBUS-PATH:                      /org/freedesktop/NetworkManager/ActiveCo                                                                          nnection/0
GENERAL.CON-PATH:                       /org/freedesktop/NetworkManager/Settings                                                                          /1
GENERAL.SPEC-OBJECT:                    --
GENERAL.MASTER-PATH:                    --
IP4.ADDRESS[1]:                         ip = 192.168.1.92/24, gw = 192.168.1.1
IP4.DNS[1]:                             192.168.1.1
DHCP4.OPTION[1]:                        requested_classless_static_routes = 1
DHCP4.OPTION[2]:                        requested_rfc3442_classless_static_route                                                                          s = 1
DHCP4.OPTION[3]:                        subnet_mask = 255.255.255.0
DHCP4.OPTION[4]:                        requested_subnet_mask = 1
DHCP4.OPTION[5]:                        domain_name_servers = 192.168.1.1
DHCP4.OPTION[6]:                        ip_address = 192.168.1.92
DHCP4.OPTION[7]:                        requested_static_routes = 1
DHCP4.OPTION[8]:                        dhcp_server_identifier = 192.168.1.1
DHCP4.OPTION[9]:                        requested_nis_servers = 1
DHCP4.OPTION[10]:                       requested_time_offset = 1
DHCP4.OPTION[11]:                       broadcast_address = 192.168.1.255
DHCP4.OPTION[12]:                       requested_interface_mtu = 1
DHCP4.OPTION[13]:                       dhcp_rebinding_time = 71342
DHCP4.OPTION[14]:                       requested_domain_name_servers = 1
DHCP4.OPTION[15]:                       dhcp_message_type = 5
DHCP4.OPTION[16]:                       requested_broadcast_address = 1
DHCP4.OPTION[17]:                       routers = 192.168.1.1
DHCP4.OPTION[18]:                       wpad = a
DHCP4.OPTION[19]:                       dhcp_renewal_time = 38942
DHCP4.OPTION[20]:                       requested_domain_name = 1
DHCP4.OPTION[21]:                       requested_routers = 1
DHCP4.OPTION[22]:                       expiry = 1409300087
DHCP4.OPTION[23]:                       requested_wpad = 1
DHCP4.OPTION[24]:                       host_name = homeserver
DHCP4.OPTION[25]:                       requested_nis_domain = 1
DHCP4.OPTION[26]:                       requested_ms_classless_static_routes = 1
DHCP4.OPTION[27]:                       network_number = 192.168.1.0
DHCP4.OPTION[28]:                       requested_domain_search = 1
DHCP4.OPTION[29]:                       next_server = 192.168.1.1
DHCP4.OPTION[30]:                       requested_ntp_servers = 1
DHCP4.OPTION[31]:                       dhcp_lease_time = 86400
DHCP4.OPTION[32]:                       requested_host_name = 1
IP6.ADDRESS[1]:                         ip = fe80::1e6f:65ff:fea9:810b/64, gw =                                                                           ::
Thank you

UPDATE:
Just tried realteks r8168 drivers(was using r8169) and there's no change.

ctwomey
Posts: 4
Joined: 2014/08/28 15:05:49

Re: Wired Network excessively slow

Post by ctwomey » 2014/09/12 00:15:14

From my reading it looks like the realtek drivers are riddled with problems with centos... Does anyone have suggestions for a different nic? or things i can try?

User avatar
TrevorH
Site Admin
Posts: 33220
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Wired Network excessively slow

Post by TrevorH » 2014/09/12 09:40:48

You might check the ELRepo repository using your current PCI device vendor/device id pairing and see if they have a kmod driver of a more recent vintage to replace the stock one. If you want a replacement card then Intel are usually good.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

ctwomey
Posts: 4
Joined: 2014/08/28 15:05:49

Re: Wired Network excessively slow

Post by ctwomey » 2015/02/17 00:07:52

I've been using the wireless card for a few months now and it works at the correct speeds. However since i'd prefer it to be wired (i'm streaming video and hosting some content on this computer) i purchased an intel card. It's using the e1000e driver and i'm getting the same speeds as the realtek!

Is there some sort of configuration i'm missing?

here's the lspci out put for the network cards now.

Code: Select all

02:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network Adapter (rev 01)
        Subsystem: Qualcomm Atheros Device 3112
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at fd6c0000 (64-bit, non-prefetchable) [size=128K]
        [virtual] Expansion ROM at fdf00000 [disabled] [size=64K]
        Capabilities: <access denied>
        Kernel driver in use: ath9k

03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
        Subsystem: Intel Corporation Gigabit CT Desktop Adapter
        Flags: bus master, fast devsel, latency 0, IRQ 17
        Memory at fdec0000 (32-bit, non-prefetchable) [size=128K]
        Memory at fde00000 (32-bit, non-prefetchable) [size=512K]
        I/O ports at df00 [size=32]
        Memory at fdefc000 (32-bit, non-prefetchable) [size=16K]
        [virtual] Expansion ROM at fdd00000 [disabled] [size=256K]
        Capabilities: <access denied>
        Kernel driver in use: e1000e


05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
        Subsystem: Gigabyte Technology Co., Ltd Motherboard
        Flags: bus master, fast devsel, latency 0, IRQ 50
        I/O ports at be00 [size=256]
        Memory at fd9ff000 (64-bit, prefetchable) [size=4K]
        Memory at fd9f8000 (64-bit, prefetchable) [size=16K]
        [virtual] Expansion ROM at fd900000 [disabled] [size=128K]
        Capabilities: <access denied>
        Kernel driver in use: r8168

ctwomey
Posts: 4
Joined: 2014/08/28 15:05:49

Re: Wired Network excessively slow

Post by ctwomey » 2015/02/17 13:26:34

Turns out the router with QOS on was restricting bandwidth. Very strange since i had tested a wired connection with my laptop. It seems to be humming along now though

jimbo8098
Posts: 12
Joined: 2015/01/30 03:06:11

Re: Wired Network excessively slow

Post by jimbo8098 » 2015/02/21 16:11:09

Good to hear you fixed it!

The router might have limited you due to the content steaming you mentioned earlier. I was going to suggest checking the duplexing on the card before you mentioned that.

I'd recommend checking up on your bandwidth usage just to make sure since it might re-occur unless you've just turned off the feature. Still, always good to minimise bandwidth where possible!

-Jim

Post Reply