Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #207175

Re: putty go slow

From mick crane <mick.crane@gmail.com>
Newsgroups linux.debian.user
Subject Re: putty go slow
Date 2019-04-09 13:10 +0200
Message-ID <xKWNz-3m0-1@gated-at.bofh.it> (permalink)
References <xKJdE-32T-21@gated-at.bofh.it> <xKKCK-46w-13@gated-at.bofh.it> <xKL5L-4hu-3@gated-at.bofh.it> <xKSJX-GT-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 2019-04-09 07:46, Peter Wiersig wrote:
> mick crane <mick.crane@gmail.com> writes:
>> 
>> the PCs are physically adjacent connected with the RJ45 ( isn't it )
>> cables through what is supposed to be a switch I got in B&Q several
>> years ago.
> 
> Almost, RJ-45 is the specification for the plug and jacks, what you're
> having here is ethernet wiring in twisted pairs between client and
> server connected by a hub.  Or switch, please clarify that as that
> changes a lot.
> 
> Is anything else connected to this hub?  If your problems occur, is
> anything else using the hub concurrently?  Can you reduce the
> connections only to server and client and maybe a internet uplink?
> Network printers can do unimaginably bad things in regard to hubs, and
> even switches.
> 
> Can you change the hub to a real switch?
> 
>> but I think it might be a hub.
>> Perhaps that is the culprit ?
> 
> Perhaps. Check the "ifconfig" output on the Linux side, maybe reset the
> server, connect from windows and if you're having problems check the
> dmesg output regarding the interface.
> 
i
how do I tell if it's a switch or a hub ?
I thought a switch sends data over the required port but a hub sends 
over all the ports ?
It's got "8 port switch" printed on it but if there is network activity 
all the lights seem to flash.

/sbin/ifconfig
enp0s25: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
         inet 10.0.0.3  netmask 255.255.255.0  broadcast 10.0.0.255
         inet6 fe80::219:d1ff:fe41:c769  prefixlen 64  scopeid 0x20<link>
         ether 00:19:d1:41:c7:69  txqueuelen 1000  (Ethernet)
         RX packets 47732498  bytes 13998322190 (13.0 GiB)
         RX errors 0  dropped 5642  overruns 0  frame 0
         TX packets 73403188  bytes 102853469866 (95.7 GiB)
         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
         device interrupt 21  memory 0xdffe0000-e0000000

I've got a Buster PC with apache2, cups, dovecot, roundcube as mail and 
print server.
a Buster PC I mess about on, a win 10 PC and a printer all connected to 
the "switch"
the gateway is a PC with pfsense on it which is connected to "switch" 
and its other network card connected to ISP router thing.

Maybe the sluggishness I sometimes observed is Windows updating itself ?

mick


> For reference, here's my output:
> 
> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>         inet 217.172.177.159  netmask 255.255.255.0  broadcast 
> 217.172.177.255
>         ether 00:19:66:f1:43:9e  txqueuelen 1000  (Ethernet)
>         RX packets 81994186  bytes 14753508445 (13.7 GiB)
>         RX errors 14  dropped 0  overruns 14  frame 0
>         TX packets 107524155  bytes 14836289080 (13.8 GiB)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> 
> Take note of the 2nd line of RX and TX status lines, there should be no
> counters there, in my case 14 overruns in regard to 819 million packets
> is a very low error rate.  I suspect that if there's a network problem
> it would manifest in some higher relative values on your side.
> 
> If in doubt verify that both sides are set to auto-negotiate and 
> replace
> both wires from the machines to the hub with new cables.
> 
> Peter

-- 
Key ID    4BFEBB31

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

putty go slow mick crane <mick.crane@gmail.com> - 2019-04-08 22:40 +0200
  Re: putty go slow Peter Wiersig <peter@friesenpeter.de> - 2019-04-09 00:00 +0200
  Re: putty go slow lev@levlaz.org - 2019-04-09 00:10 +0200
    Re: putty go slow mick crane <mick.crane@gmail.com> - 2019-04-09 00:40 +0200
      Re: putty go slow lev@levlaz.org - 2019-04-09 06:00 +0200
      Re: putty go slow Peter Wiersig <peter@friesenpeter.de> - 2019-04-09 08:50 +0200
        Re: putty go slow mick crane <mick.crane@gmail.com> - 2019-04-09 13:10 +0200
          Re: putty go slow Dan Ritter <dsr@randomstring.org> - 2019-04-09 13:20 +0200
          Re: putty go slow Peter Wiersig <peter@friesenpeter.de> - 2019-04-10 12:10 +0200
            Re: putty go slow Michael Stone <mstone@debian.org> - 2019-04-10 14:10 +0200
              Re: putty go slow Peter Wiersig <peter@friesenpeter.de> - 2019-04-10 15:10 +0200
                Re: putty go slow mick crane <mick.crane@gmail.com> - 2019-04-10 15:30 +0200
                Re: putty go slow Peter Wiersig <peter@friesenpeter.de> - 2019-04-10 16:10 +0200
                Re: putty go slow Michael Stone <mstone@debian.org> - 2019-04-10 15:40 +0200
                Re: putty go slow Peter Wiersig <peter@friesenpeter.de> - 2019-04-10 16:40 +0200
            Re: putty go slow rhkramer@gmail.com - 2019-04-10 16:20 +0200
              Re: putty go slow rhkramer@gmail.com - 2019-04-10 16:30 +0200
                Re: putty go slow rhkramer@gmail.com - 2019-04-12 14:50 +0200
              Re: putty go slow Michael Stone <mstone@debian.org> - 2019-04-10 17:20 +0200
        Re: putty go slow Celejar <celejar@gmail.com> - 2019-04-09 19:50 +0200

csiph-web