Just as the title says. I'm constantly running anywhere from 80 to 120 kb/s even with all relevant programs closed and dropbox/ubuntu one paused. This is a problem for me as I'm running on dorm internet, and this makes online games unplayable. Anyone have a sollution for a newbie user?
Announcement
Collapse
No announcement yet.
I just upgraded, and now my network is constantly in use
Collapse
This topic is closed.
X
X
-
this is what I'm seeing:
Code:Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:8089 0.0.0.0:* LISTEN 32548/banshee tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 1236/smbd tcp 0 0 127.0.0.1:28129 0.0.0.0:* LISTEN 14149/wineserver tcp 0 0 127.0.0.1:13666 0.0.0.0:* LISTEN 1337/LCDd tcp 0 0 127.0.0.1:9481 0.0.0.0:* LISTEN 1244/java tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 1236/smbd tcp 0 0 0.0.0.0:51695 0.0.0.0:* LISTEN 1347/Plex DLNA Serv tcp 0 0 127.0.0.1:30000 0.0.0.0:* LISTEN 14142/bash tcp 0 0 0.0.0.0:32400 0.0.0.0:* LISTEN 987/Plex Media Serv tcp 0 0 0.0.0.0:32469 0.0.0.0:* LISTEN 1347/Plex DLNA Serv tcp 0 0 127.0.1.1:53 0.0.0.0:* LISTEN 1274/dnsmasq tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 990/sshd tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 897/cupsd tcp 0 0 127.0.0.1:8888 0.0.0.0:* LISTEN 1244/java tcp 0 0 10.10.20.56:39572 209.84.29.126:80 TIME_WAIT - tcp 0 0 10.10.20.56:57004 173.255.193.141:80 ESTABLISHED 16900/firefox tcp 0 0 10.10.20.56:39551 199.27.73.129:80 TIME_WAIT - tcp 0 0 10.10.20.56:56708 50.18.175.22:80 TIME_WAIT - tcp 0 0 10.10.20.56:53619 108.160.163.41:80 FIN_WAIT2 - tcp 0 0 10.10.20.56:57007 173.255.193.141:80 ESTABLISHED 16900/firefox tcp 0 0 10.10.20.56:43382 74.125.225.134:443 ESTABLISHED 16900/firefox tcp 0 0 10.10.20.56:34669 23.0.165.97:80 ESTABLISHED 14149/wineserver tcp 0 0 10.10.20.56:57026 173.255.193.141:80 ESTABLISHED 16900/firefox tcp 0 0 10.10.20.56:57006 173.255.193.141:80 ESTABLISHED 16900/firefox tcp 0 0 10.10.20.56:57027 173.255.193.141:80 ESTABLISHED 16900/firefox tcp 0 0 127.0.0.1:40939 127.0.0.1:28129 ESTABLISHED 14149/wineserver tcp 0 0 10.10.20.56:55188 108.160.162.76:443 TIME_WAIT - tcp 0 0 10.10.20.56:57025 173.255.193.141:80 ESTABLISHED 16900/firefox tcp 0 0 127.0.0.1:28129 127.0.0.1:40939 ESTABLISHED 14149/wineserver tcp6 0 0 :::445 :::* LISTEN 1236/smbd tcp6 0 0 :::139 :::* LISTEN 1236/smbd tcp6 0 0 :::22 :::* LISTEN 990/sshd tcp6 0 0 ::1:631 :::* LISTEN 897/cupsd tcp6 1 0 ::1:46513 ::1:631 CLOSE_WAIT 993/cups-browsed udp 0 0 0.0.0.0:54243 0.0.0.0:* 1347/Plex DLNA Serv udp 0 0 127.0.0.1:56551 0.0.0.0:* 987/Plex Media Serv udp 0 0 0.0.0.0:5353 0.0.0.0:* 869/avahi-daemon: r udp 0 0 0.0.0.0:26005 0.0.0.0:* 3605/dhclient udp 0 0 0.0.0.0:5553 0.0.0.0:* 1347/Plex DLNA Serv udp 0 0 0.0.0.0:32410 0.0.0.0:* 987/Plex Media Serv udp 0 0 0.0.0.0:32413 0.0.0.0:* 987/Plex Media Serv udp 0 0 0.0.0.0:32414 0.0.0.0:* 987/Plex Media Serv udp 0 0 10.10.20.56:46815 0.0.0.0:* 987/Plex Media Serv udp 0 0 0.0.0.0:1900 0.0.0.0:* 1347/Plex DLNA Serv udp 0 0 127.0.1.1:53 0.0.0.0:* 1274/dnsmasq udp 0 0 0.0.0.0:68 0.0.0.0:* 3605/dhclient udp 0 0 0.0.0.0:36936 0.0.0.0:* 1347/Plex DLNA Serv udp 0 0 10.10.20.255:137 0.0.0.0:* 1604/nmbd udp 0 0 10.10.20.56:137 0.0.0.0:* 1604/nmbd udp 0 0 0.0.0.0:137 0.0.0.0:* 1604/nmbd udp 0 0 10.10.20.255:138 0.0.0.0:* 1604/nmbd udp 0 0 10.10.20.56:138 0.0.0.0:* 1604/nmbd udp 0 0 0.0.0.0:138 0.0.0.0:* 1604/nmbd udp 0 0 0.0.0.0:37155 0.0.0.0:* 869/avahi-daemon: r udp 0 0 0.0.0.0:41321 0.0.0.0:* 1244/java udp 0 0 0.0.0.0:45448 0.0.0.0:* 1244/java udp 0 0 0.0.0.0:4493 0.0.0.0:* 1347/Plex DLNA Serv udp 0 0 127.0.0.1:47615 0.0.0.0:* 987/Plex Media Serv udp 0 0 10.10.20.56:39424 0.0.0.0:* 987/Plex Media Serv udp 0 0 0.0.0.0:631 0.0.0.0:* 993/cups-browsed udp6 0 0 :::5353 :::* 869/avahi-daemon: r udp6 0 0 :::57130 :::* 869/avahi-daemon: r udp6 0 0 :::36776 :::* 3605/dhclient
Edit: I should note that, even with plex running in the background, before the upgrade, I didn't have this problem.
- Top
- Bottom
Comment
-
I think, that that's an "hidden" apt-update, running in the background - it seems that this is running multiple times (especially after using muon discover).
update-apt-xapi is running and apt is locked (/var/cache/apt/archives/lock) while network is in use - strange behaviour of kubuntu 13.10 (Never happened on 13.04)
- Top
- Bottom
Comment
-
Originally posted by mrboese View PostI think, that that's an "hidden" apt-update, running in the background - it seems that this is running multiple times (especially after using muon discover).
update-apt-xapi is running and apt is locked (/var/cache/apt/archives/lock) while network is in use - strange behaviour of kubuntu 13.10 (Never happened on 13.04)
VINNYi7 4core HT 8MB L3 2.9GHz
16GB RAM
Nvidia GTX 860M 4GB RAM 1152 cuda cores
- Top
- Bottom
Comment
-
Pan-Galactic QuordlepleenSo Long, and Thanks for All the Fish
- Jul 2011
- 9524
- Seattle, WA, USA
- Send PM
Try this:
Code:sudo apt-get install nethogs sudo nethogs [i]device[/i]
- Top
- Bottom
Comment
Comment