First, the last question - yes, someone decided it was better to not have eth0 
any more, so now they are those weird enp4s1 names.

It’s ok once you get used to it, I guess, but it’s a small pain getting used 
to.  (There are things you can do to make it go back to eth0, but that may 
cause more issues than just living with it).

My first thought was - does he have a 100MBs port in there somewhere.  E.g. 
someone installed a 10/100 switch or hub between your computer and your Comcast 
DSL (I assume) line - and that includes the modem.  (I had mine increased over 
100 a while back, but only got 100 until I got a new modem that wasn’t 10/100! 
… oops)

There are ways in Linux to force the speed lower, but that’s unlikely to be 
your issue.  Did someone come in to the house and add a hub so they can capture 
all your traffic?  (Yes, that’s somewhat on the paranoid side, but it WOULD 
explain the sudden 100MBs limit)


From: PLUG-discuss [mailto:plug-discuss-boun...@lists.phxlinux.org] On Behalf 
Of Jim
Sent: Wednesday, September 05, 2018 1:13 PM
To: plug-discuss@lists.phxlinux.org
Subject: networking question

Back in June comcast raised my connection speed to 150Mbps.  Two weeks ago it 
went back down to 100.  I called to complain and was told I was supposed to be  
getting 100Mbps.  I finally got someone to admit that my connection speed 
should be 150, but I'm still getting 100.

I didn't make any changes to the network, but something could have gotten 
changed.  Is there anything i can look in network settings to determine if 
something could be tweaked for a faster connection?

I have an Arris SB6141 modem and an ASUS RT-ACRH13 gigabit router.  The modem 
(SB6141) supports speeds up to 343Mbps down.  KDE's network manager shows the 
MTU setting is set to Automatic and the box is checked to allow auto 
negotiation.

I did install Kubuntu 18 after the increase to 150Mbps.  The speed did not drop 
until a month or so after Kubuntu 18 was installed.

Since the installation, the ethernet connection is no longer called eth0.  Now 
it's called enp4s1.  Is that some new way of naming network devices?  I don't 
really care what it calls the parts as long as they work.  I can still use 
netwatch, but I have to give it the enp4s1 string as it expects eth0 unless  
told differently.

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss

Reply via email to