You are not logged in.

#1 2017-01-16 14:41:13

ntldr
Member
Registered: 2017-01-04
Posts: 65

Strange network speed issue?

Hey

I've strange network issue. In torrent, wget, browser downloads my speeds are as they should be. When looking at youtube video with VPN it stays at 1.2mbps usually and uploads are 200kbps at the max. I know that VPN causes slow downs in connection but it shouldn't be this bad it wasn't before. But what's more interesting is that when not connected to VPN download speeds are same but youtube videos buffer at much faster rate 5-7mbps but upload is still bad 200-500kbps while it should be 1mbps+

I'm using wired connection and setup is done by following the wiki. Otherwise it's working just fine.. can't figure this one out.

Offline

#2 2017-01-17 09:32:18

xvzf
Member
Registered: 2014-05-18
Posts: 86

Re: Strange network speed issue?

This sounds a lot like Kabel Deutschland or Telekom in Germany - They limit the speed after 10Gbyte file transfers a day to like 5mbit, but VOD and normal browsing is still at full speed.

Offline

#3 2017-01-17 13:18:53

ntldr
Member
Registered: 2017-01-04
Posts: 65

Re: Strange network speed issue?

xvzf wrote:

This sounds a lot like Kabel Deutschland or Telekom in Germany - They limit the speed after 10Gbyte file transfers a day to like 5mbit, but VOD and normal browsing is still at full speed.

It shouldn't be the case tho.. I can go all day without VPN just fine get full speeds as usual but upload for some reason on arch linux is limited to 200-500kbps at tops. When switching over to windows it goes 1-1.5mbps instantly in same website. But I find it strange when using VPN and browsing youtube videos it's now limited to 1mbps or so which doesn't happen if I use raw connection.

ethtool  eno1
Settings for eno1:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full 
                                100baseT/Half 100baseT/Full 
                                1000baseT/Full 
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 1
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: on (auto)
Cannot get wake-on-lan settings: Operation not permitted
        Current message level: 0x00000007 (7)
                               drv probe link
        Link detected: yes

I don't know what else info to give..

Offline

#4 2017-01-23 07:51:38

ntldr
Member
Registered: 2017-01-04
Posts: 65

Re: Strange network speed issue?

Since none seems to know how to help I decided to add some info now then.. that might help? hopefully

~ » journalctl -b | grep eno1
Jan 23 09:34:04 Darknet kernel: e1000e 0000:00:19.0 eno1: renamed from eth0
Jan 23 09:34:04 Darknet systemd-udevd[266]: Process '/usr/lib/systemd/systemd-sysctl --prefix=/net/ipv4/conf/eno1 --prefix=/net/ipv4/neigh/eno1 --prefix=/net/ipv6/conf/eno1 --prefix=/net/ipv6/neigh/eno1' failed with exit code 1.
Jan 23 09:34:08 Darknet NetworkManager[361]: <info>  [1485156848.2667] manager: (eno1): new Ethernet device (/org/freedesktop/NetworkManager/Devices/1)
Jan 23 09:34:08 Darknet NetworkManager[361]: <info>  [1485156848.2673] device (eno1): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Jan 23 09:34:08 Darknet kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
Jan 23 09:34:08 Darknet kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
Jan 23 09:34:11 Darknet NetworkManager[361]: <info>  [1485156851.4627] device (eno1): link connected
Jan 23 09:34:11 Darknet NetworkManager[361]: <info>  [1485156851.4633] device (eno1): state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Jan 23 09:34:11 Darknet kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Jan 23 09:34:11 Darknet kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
Jan 23 09:34:11 Darknet NetworkManager[361]: <info>  [1485156851.4656] device (eno1): Activation: starting connection 'Wired connection 1' (5e64c811-1b64-3759-839a-a4433c45cee8)
Jan 23 09:34:11 Darknet NetworkManager[361]: <info>  [1485156851.4658] device (eno1): state change: disconnected -> prepare (reason 'none') [30 40 0]
Jan 23 09:34:11 Darknet NetworkManager[361]: <info>  [1485156851.5692] device (eno1): set-hw-addr: set-cloned MAC address to BE:30:E2:F9:39:93 (BE:30:E2:F9:39:93)
Jan 23 09:34:11 Darknet kernel: e1000e: eno1 NIC Link is Down
Jan 23 09:34:11 Darknet NetworkManager[361]: <info>  [1485156851.7806] device (eno1): state change: prepare -> config (reason 'none') [40 50 0]
Jan 23 09:34:11 Darknet NetworkManager[361]: <info>  [1485156851.7808] device (eno1): state change: config -> ip-config (reason 'none') [50 70 0]
Jan 23 09:34:11 Darknet NetworkManager[361]: <info>  [1485156851.7828] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Jan 23 09:34:11 Darknet kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
Jan 23 09:34:11 Darknet NetworkManager[361]: <info>  [1485156851.7867] dhcp4 (eno1): dhclient started with pid 437
Jan 23 09:34:11 Darknet dhclient[437]: DHCPREQUEST on eno1 to 255.255.255.255 port 67
Jan 23 09:34:15 Darknet NetworkManager[361]: <info>  [1485156855.1594] device (eno1): link connected
Jan 23 09:34:15 Darknet kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Jan 23 09:34:18 Darknet dhclient[437]: DHCPREQUEST on eno1 to 255.255.255.255 port 67
Jan 23 09:34:18 Darknet NetworkManager[361]: <info>  [1485156858.4474] dhcp4 (eno1):   address 192.168.100.10
Jan 23 09:34:18 Darknet NetworkManager[361]: <info>  [1485156858.4475] dhcp4 (eno1):   plen 24 (255.255.255.0)
Jan 23 09:34:18 Darknet NetworkManager[361]: <info>  [1485156858.4475] dhcp4 (eno1):   gateway 192.168.100.1
Jan 23 09:34:18 Darknet NetworkManager[361]: <info>  [1485156858.4475] dhcp4 (eno1):   server identifier 192.168.100.1
Jan 23 09:34:18 Darknet NetworkManager[361]: <info>  [1485156858.4475] dhcp4 (eno1):   lease time 86400
Jan 23 09:34:18 Darknet NetworkManager[361]: <info>  [1485156858.4476] dhcp4 (eno1):   nameserver '192.168.100.1'
Jan 23 09:34:18 Darknet NetworkManager[361]: <info>  [1485156858.4476] dhcp4 (eno1):   nameserver '192.168.100.1'
Jan 23 09:34:18 Darknet NetworkManager[361]: <info>  [1485156858.4476] dhcp4 (eno1): state changed unknown -> bound
Jan 23 09:34:18 Darknet NetworkManager[361]: <info>  [1485156858.4493] device (eno1): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Jan 23 09:34:18 Darknet NetworkManager[361]: <info>  [1485156858.4505] device (eno1): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Jan 23 09:34:18 Darknet NetworkManager[361]: <info>  [1485156858.4511] device (eno1): state change: secondaries -> activated (reason 'none') [90 100 0]
Jan 23 09:34:18 Darknet NetworkManager[361]: <info>  [1485156858.4559] policy: set 'Wired connection 1' (eno1) as default for IPv4 routing and DNS
Jan 23 09:34:18 Darknet NetworkManager[361]: <info>  [1485156858.4995] device (eno1): Activation: successful, device activated.
Jan 23 09:34:18 Darknet nm-dispatcher[373]: req:3 'up' [eno1]: new request (0 scripts)
Jan 23 09:34:18 Darknet nm-dispatcher[373]: req:3 'up' [eno1]: completed: no scripts
Jan 23 09:37:16 Darknet NetworkManager[361]: <info>  [1485157036.0708] policy: set 'Wired connection 1' (eno1) as default for IPv4 routing and DNS
Jan 23 09:37:20 Darknet kernel: e1000e: eno1 NIC Link is Down
Jan 23 09:37:24 Darknet NetworkManager[361]: <info>  [1485157044.5358] device (eno1): state change: activated -> unavailable (reason 'carrier-changed') [100 20 40]
Jan 23 09:37:24 Darknet NetworkManager[361]: <info>  [1485157044.5682] dhcp4 (eno1): canceled DHCP transaction, DHCP client pid 437
Jan 23 09:37:24 Darknet NetworkManager[361]: <info>  [1485157044.5682] dhcp4 (eno1): state changed bound -> done
Jan 23 09:37:24 Darknet NetworkManager[361]: <info>  [1485157044.6724] device (eno1): set-hw-addr: reset MAC address to F0:79:59:8E:15:CA (deactivate)
Jan 23 09:37:24 Darknet kernel: e1000e: eno1 NIC Link is Down
Jan 23 09:37:24 Darknet nm-dispatcher[1640]: req:4 'down' [eno1]: new request (0 scripts)
Jan 23 09:37:24 Darknet nm-dispatcher[1640]: req:4 'down' [eno1]: completed: no scripts
Jan 23 09:37:32 Darknet NetworkManager[361]: <info>  [1485157052.5728] device (eno1): link connected
Jan 23 09:37:32 Darknet NetworkManager[361]: <info>  [1485157052.5734] device (eno1): state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Jan 23 09:37:32 Darknet kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Jan 23 09:37:32 Darknet NetworkManager[361]: <info>  [1485157052.5776] device (eno1): Activation: starting connection 'Wired connection 1' (5e64c811-1b64-3759-839a-a4433c45cee8)
Jan 23 09:37:32 Darknet NetworkManager[361]: <info>  [1485157052.5785] device (eno1): state change: disconnected -> prepare (reason 'none') [30 40 0]
Jan 23 09:37:32 Darknet NetworkManager[361]: <info>  [1485157052.6728] device (eno1): set-hw-addr: set-cloned MAC address to BE:30:E2:F9:39:93 (BE:30:E2:F9:39:93)
Jan 23 09:37:32 Darknet kernel: e1000e: eno1 NIC Link is Down
Jan 23 09:37:32 Darknet NetworkManager[361]: <info>  [1485157052.8852] device (eno1): state change: prepare -> config (reason 'none') [40 50 0]
Jan 23 09:37:32 Darknet NetworkManager[361]: <info>  [1485157052.8859] device (eno1): state change: config -> ip-config (reason 'none') [50 70 0]
Jan 23 09:37:32 Darknet NetworkManager[361]: <info>  [1485157052.8864] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Jan 23 09:37:32 Darknet kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
Jan 23 09:37:32 Darknet NetworkManager[361]: <info>  [1485157052.8880] dhcp4 (eno1): dhclient started with pid 1770
Jan 23 09:37:32 Darknet dhclient[1770]: DHCPREQUEST on eno1 to 255.255.255.255 port 67
Jan 23 09:37:36 Darknet NetworkManager[361]: <info>  [1485157056.0959] device (eno1): link connected
Jan 23 09:37:36 Darknet kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Jan 23 09:37:39 Darknet dhclient[1770]: DHCPREQUEST on eno1 to 255.255.255.255 port 67
Jan 23 09:37:39 Darknet NetworkManager[361]: <info>  [1485157059.4024] dhcp4 (eno1):   address 192.168.100.10
Jan 23 09:37:39 Darknet NetworkManager[361]: <info>  [1485157059.4024] dhcp4 (eno1):   plen 24 (255.255.255.0)
Jan 23 09:37:39 Darknet NetworkManager[361]: <info>  [1485157059.4024] dhcp4 (eno1):   gateway 192.168.100.1
Jan 23 09:37:39 Darknet NetworkManager[361]: <info>  [1485157059.4025] dhcp4 (eno1):   server identifier 192.168.100.1
Jan 23 09:37:39 Darknet NetworkManager[361]: <info>  [1485157059.4025] dhcp4 (eno1):   lease time 86400
Jan 23 09:37:39 Darknet NetworkManager[361]: <info>  [1485157059.4025] dhcp4 (eno1):   nameserver '192.168.100.1'
Jan 23 09:37:39 Darknet NetworkManager[361]: <info>  [1485157059.4025] dhcp4 (eno1):   nameserver '192.168.100.1'
Jan 23 09:37:39 Darknet NetworkManager[361]: <info>  [1485157059.4025] dhcp4 (eno1): state changed unknown -> bound
Jan 23 09:37:39 Darknet NetworkManager[361]: <info>  [1485157059.4031] device (eno1): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Jan 23 09:37:39 Darknet NetworkManager[361]: <info>  [1485157059.4036] device (eno1): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Jan 23 09:37:39 Darknet NetworkManager[361]: <info>  [1485157059.4039] device (eno1): state change: secondaries -> activated (reason 'none') [90 100 0]
Jan 23 09:37:39 Darknet NetworkManager[361]: <info>  [1485157059.4066] policy: set 'Wired connection 1' (eno1) as default for IPv4 routing and DNS
Jan 23 09:37:39 Darknet NetworkManager[361]: <info>  [1485157059.4259] device (eno1): Activation: successful, device activated.
Jan 23 09:37:39 Darknet nm-dispatcher[1783]: req:2 'up' [eno1]: new request (0 scripts)
Jan 23 09:37:39 Darknet nm-dispatcher[1783]: req:2 'up' [eno1]: completed: no scripts
Jan 23 09:40:41 Darknet NetworkManager[361]: <info>  [1485157241.7817] device (eno1): state change: activated -> deactivating (reason 'user-requested') [100 110 39]
Jan 23 09:40:41 Darknet NetworkManager[361]: <info>  [1485157241.7898] audit: op="device-disconnect" interface="eno1" ifindex=2 pid=603 uid=1000 result="success"
Jan 23 09:40:41 Darknet NetworkManager[361]: <info>  [1485157241.7901] device (eno1): state change: deactivating -> disconnected (reason 'user-requested') [110 30 39]
Jan 23 09:40:41 Darknet NetworkManager[361]: <info>  [1485157241.8543] dhcp4 (eno1): canceled DHCP transaction, DHCP client pid 1770
Jan 23 09:40:41 Darknet NetworkManager[361]: <info>  [1485157241.8543] dhcp4 (eno1): state changed bound -> done
Jan 23 09:40:41 Darknet NetworkManager[361]: <info>  [1485157241.9590] device (eno1): set-hw-addr: reset MAC address to F0:79:59:8E:15:CA (deactivate)
Jan 23 09:40:41 Darknet kernel: e1000e: eno1 NIC Link is Down
Jan 23 09:40:42 Darknet kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
Jan 23 09:40:42 Darknet nm-dispatcher[4951]: req:2 'down' [eno1]: new request (0 scripts)
Jan 23 09:40:42 Darknet nm-dispatcher[4951]: req:2 'down' [eno1]: completed: no scripts
Jan 23 09:40:42 Darknet NetworkManager[361]: <info>  [1485157242.1906] device (eno1): state change: disconnected -> unavailable (reason 'carrier-changed') [30 20 40]
Jan 23 09:40:45 Darknet NetworkManager[361]: <info>  [1485157245.5492] device (eno1): link connected
Jan 23 09:40:45 Darknet NetworkManager[361]: <info>  [1485157245.5494] device (eno1): state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Jan 23 09:40:45 Darknet kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Jan 23 09:40:45 Darknet kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
Jan 23 09:40:48 Darknet NetworkManager[361]: <info>  [1485157248.3344] device (eno1): Activation: starting connection 'Wired connection 1' (5e64c811-1b64-3759-839a-a4433c45cee8)
Jan 23 09:40:48 Darknet NetworkManager[361]: <info>  [1485157248.3345] device (eno1): state change: disconnected -> prepare (reason 'none') [30 40 0]
Jan 23 09:40:48 Darknet NetworkManager[361]: <info>  [1485157248.4390] device (eno1): set-hw-addr: set-cloned MAC address to BE:30:E2:F9:39:93 (BE:30:E2:F9:39:93)
Jan 23 09:40:48 Darknet kernel: e1000e: eno1 NIC Link is Down
Jan 23 09:40:48 Darknet NetworkManager[361]: <info>  [1485157248.6511] device (eno1): state change: prepare -> config (reason 'none') [40 50 0]
Jan 23 09:40:48 Darknet NetworkManager[361]: <info>  [1485157248.6514] device (eno1): state change: config -> ip-config (reason 'none') [50 70 0]
Jan 23 09:40:48 Darknet NetworkManager[361]: <info>  [1485157248.6516] dhcp4 (eno1): activation: beginning transaction (timeout in 45 seconds)
Jan 23 09:40:48 Darknet kernel: IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
Jan 23 09:40:48 Darknet NetworkManager[361]: <info>  [1485157248.6526] dhcp4 (eno1): dhclient started with pid 5006
Jan 23 09:40:48 Darknet dhclient[5006]: DHCPREQUEST on eno1 to 255.255.255.255 port 67
Jan 23 09:40:52 Darknet NetworkManager[361]: <info>  [1485157252.0159] device (eno1): link connected
Jan 23 09:40:52 Darknet kernel: e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
Jan 23 09:40:52 Darknet dhclient[5006]: DHCPREQUEST on eno1 to 255.255.255.255 port 67
Jan 23 09:40:58 Darknet dhclient[5006]: DHCPREQUEST on eno1 to 255.255.255.255 port 67
Jan 23 09:40:58 Darknet NetworkManager[361]: <info>  [1485157258.2397] dhcp4 (eno1):   address 192.168.100.10
Jan 23 09:40:58 Darknet NetworkManager[361]: <info>  [1485157258.2397] dhcp4 (eno1):   plen 24 (255.255.255.0)
Jan 23 09:40:58 Darknet NetworkManager[361]: <info>  [1485157258.2397] dhcp4 (eno1):   gateway 192.168.100.1
Jan 23 09:40:58 Darknet NetworkManager[361]: <info>  [1485157258.2397] dhcp4 (eno1):   server identifier 192.168.100.1
Jan 23 09:40:58 Darknet NetworkManager[361]: <info>  [1485157258.2397] dhcp4 (eno1):   lease time 86400
Jan 23 09:40:58 Darknet NetworkManager[361]: <info>  [1485157258.2397] dhcp4 (eno1):   nameserver '192.168.100.1'
Jan 23 09:40:58 Darknet NetworkManager[361]: <info>  [1485157258.2397] dhcp4 (eno1):   nameserver '192.168.100.1'
Jan 23 09:40:58 Darknet NetworkManager[361]: <info>  [1485157258.2397] dhcp4 (eno1): state changed unknown -> bound
Jan 23 09:40:58 Darknet NetworkManager[361]: <info>  [1485157258.2402] device (eno1): state change: ip-config -> ip-check (reason 'none') [70 80 0]
Jan 23 09:40:58 Darknet NetworkManager[361]: <info>  [1485157258.2405] device (eno1): state change: ip-check -> secondaries (reason 'none') [80 90 0]
Jan 23 09:40:58 Darknet NetworkManager[361]: <info>  [1485157258.2407] device (eno1): state change: secondaries -> activated (reason 'none') [90 100 0]
Jan 23 09:40:58 Darknet NetworkManager[361]: <info>  [1485157258.2439] policy: set 'Wired connection 1' (eno1) as default for IPv4 routing and DNS
Jan 23 09:40:58 Darknet NetworkManager[361]: <info>  [1485157258.2631] device (eno1): Activation: successful, device activated.
Jan 23 09:40:58 Darknet nm-dispatcher[5020]: req:2 'up' [eno1]: new request (0 scripts)
Jan 23 09:40:58 Darknet nm-dispatcher[5020]: req:2 'up' [eno1]: completed: no scripts
Jan 23 09:42:46 Darknet NetworkManager[361]: <info>  [1485157366.5638] policy: set 'Wired connection 1' (eno1) as default for IPv4 routing and DNS
Jan 23 09:45:43 Darknet NetworkManager[361]: <info>  [1485157543.9359] policy: set 'Wired connection 1' (eno1) as default for IPv4 routing and DNS
systemctl list-unit-files --state=enabled
UNIT FILE                                   STATE  
autovt@.service                             enabled
dbus-org.freedesktop.NetworkManager.service enabled
dbus-org.freedesktop.nm-dispatcher.service  enabled
display-manager.service                     enabled
getty@.service                              enabled
lightdm.service                             enabled
NetworkManager-dispatcher.service           enabled
NetworkManager.service                      enabled
systemd-timesyncd.service                   enabled
remote-fs.target                            enabled

10 unit files listed.
systemd-analyze {blame,critical-chain}
           929ms run-media-ntldr-Uusi\x20asema1.mount
           374ms run-media-ntldr-Uusi\x20asema.mount
           196ms run-media-ntldr-78D4E28FD4E24EC6.mount
           142ms systemd-timesyncd.service
           114ms dev-sda3.device
            50ms udisks2.service
            49ms systemd-journald.service
            42ms systemd-journal-flush.service
            41ms upower.service
            39ms NetworkManager.service
            39ms accounts-daemon.service
            27ms systemd-udevd.service
            25ms polkit.service
            21ms systemd-logind.service
            21ms systemd-sysctl.service
            20ms systemd-tmpfiles-setup-dev.service
            19ms systemd-udev-trigger.service
            17ms user@1000.service
            13ms systemd-tmpfiles-clean.service
            11ms lightdm.service
             9ms tmp.mount
             7ms systemd-tmpfiles-setup.service
             6ms boot.mount
             6ms systemd-binfmt.service
             5ms dev-sda2.swap
             4ms dev-hugepages.mount
             4ms systemd-random-seed.service
             4ms sys-kernel-debug.mount
             4ms kmod-static-nodes.service
             3ms sys-kernel-config.mount
             2ms proc-sys-fs-binfmt_misc.mount
             2ms systemd-remount-fs.service
             2ms systemd-update-utmp.service
             2ms dev-mqueue.mount
             1ms rtkit-daemon.service
             1ms systemd-user-sessions.service
             1ms sys-fs-fuse-connections.mount

Offline

Board footer

Powered by FluxBB