From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-user+bounces-201954-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (2048 bits))
(No client certificate requested)
by finch.gentoo.org (Postfix) with ESMTPS id 3825A158089
for <garchives@archives.gentoo.org>; Sat, 23 Sep 2023 14:49:03 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 617DA2BC097;
Sat, 23 Sep 2023 14:48:59 +0000 (UTC)
Received: from mail-ot1-x335.google.com (mail-ot1-x335.google.com [IPv6:2607:f8b0:4864:20::335])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id E28952BC01B
for <gentoo-user@lists.gentoo.org>; Sat, 23 Sep 2023 14:48:58 +0000 (UTC)
Received: by mail-ot1-x335.google.com with SMTP id 46e09a7af769-6bf2427b947so1998624a34.3
for <gentoo-user@lists.gentoo.org>; Sat, 23 Sep 2023 07:48:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20230601; t=1695480538; x=1696085338; darn=lists.gentoo.org;
h=in-reply-to:mime-version:user-agent:date:message-id:autocrypt:from
:references:to:subject:from:to:cc:subject:date:message-id:reply-to;
bh=jfr29FQJm+/OWUfrsDykMaQeCsddB/LgH3+N2W62bF4=;
b=nccTrzyKSBfbTCyB0jGP4WZVW+lgOyl4RShi1wptiNBB9U/DSFylPpw0P3bmB/4fFg
XZtoohn8sqgF8bvmMkvo3DW/vaVf4jVqmm75pGikoYcW9EfCTV4JIi04EdTccJdb8qEd
mjQV/dvuZ9O2oY8Wtgq3CAK/q3ifwQFB1VZBwISa/ezyXz4A3ZDO9A360fEd7yBIeayV
RFd/VTSny/AtnkAZydbGw1edA4LgQtcC4z64TeCN4mb1Vbipomwk3QDiSgf8RMc5V8DC
OUZpXEtKNZRRvTFfGTnZehCsdntMORGYQW4T8vpM6+WfLK066FyBaFoLtc7MdwpS9KeT
81xw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20230601; t=1695480538; x=1696085338;
h=in-reply-to:mime-version:user-agent:date:message-id:autocrypt:from
:references:to:subject:x-gm-message-state:from:to:cc:subject:date
:message-id:reply-to;
bh=jfr29FQJm+/OWUfrsDykMaQeCsddB/LgH3+N2W62bF4=;
b=qgV5O5lPH3OzsvDxSd12Ye+Zc2ifMYGWxvXb7eRodkF+d+4rujmn4VBUAkBm9bRTum
phOyRBBKelUlsqKY6uiTOG37cGvt8dnmvVkok2dqG4bHe5Isa1RpLNA8tO2ywrITT7yH
RIHtY25D4gJHPsIjvbumYWnUxrXWz1/wP69nKUDxV3JPCHQMQPjmFWMF4OYb+A1WKaNs
cZHyfiZxMnVyFU0yY5fq3P2SsPzPw/yhz6LtcAwM3XhR0S2UkLHIggsLibGd58lL6+H4
GwCm7hjk2o1n30cHxiclssiLVi3Tu6wdBBXSi/+PSeLND4lKJntE+hBYTL+3LQMjEWfS
/Lfw==
X-Gm-Message-State: AOJu0YwP/5fq1EUF/ZKB3YtIr4WoFUVbxO+joq9FuhrLdoRnisakjwQn
qCy46BmUkULKziCSp2/fEzaPfa1gqUo=
X-Google-Smtp-Source: AGHT+IELhyYc1RG9vCavY5b2P1r0r7QXuRY+O/9KVUNUI4uZnfEmMRlVa/MVDHZwvDA6A25+5Jrn6A==
X-Received: by 2002:a05:6830:1e64:b0:6b9:d224:1a1d with SMTP id m4-20020a0568301e6400b006b9d2241a1dmr2506866otr.19.1695480538066;
Sat, 23 Sep 2023 07:48:58 -0700 (PDT)
Received: from [10.0.0.4] ([207.244.201.197])
by smtp.gmail.com with ESMTPSA id f1-20020a4ac481000000b0057b643aa5d5sm906607ooq.35.2023.09.23.07.48.57
(version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
Sat, 23 Sep 2023 07:48:57 -0700 (PDT)
Subject: Re: [gentoo-user] Network throughput from main Gentoo rig to NAS box.
To: gentoo-user@lists.gentoo.org
References: <05110faf-6f58-e8f3-0a91-bc51922c8717@gmail.com>
<CAK2H+edGamLuVnPPs0xp8xa7EVugB787NFR_kyt30aEhq1P0Sg@mail.gmail.com>
<a4ccfb7c-d2c4-25ec-4547-68c431a2cdec@gmail.com>
<CAK2H+ee7TKZ5YzeWZ+Ps_2E6qY5xwAcirLp83oVy1L+jyz7j8w@mail.gmail.com>
From: Dale <rdalek1967@gmail.com>
Autocrypt: addr=rdalek1967@gmail.com; prefer-encrypt=mutual; keydata=
mQINBGFSciYBEADcEGMyJBSuavKO/XKUVvgkxck7Nl8Iuu8N2lcnRji/rSKg5c1Acix1ll9i
oW8JBCHwvn0+Xy60BvEsqcup3YSHw5STl/bR1ePEehtnYrg8FdjdS91+B805RfnKMm69rFVI
wLSBHQrSG1yxHd8CloWoEdhmVtP24buajbh114bgXd9ahtpZrCVMrWdWYUg2mEXguGV5uNAh
Rf8SWxDNc79w24JxsV34a8niMUYMjzWr0rafIbzk732X38vGjVMLo/2mMpkbp9mPp++LHoY+
0Pet8zxxdXPJSCd475kza1AD+hhSyBZXB9yknYWgyY3cZe1rGmooJSi2KX4QxO7npwLThcO1
be6KKRkd35+Fi/a1BzVOHsZMiK/gcwxEFoMd27gir4ehaeHJfFXl+65w4hj0EsOZSxrJrm2C
R50g5By2czSKP1bADEygFNpIJj51AR+wM88NImG2RPtlT2maYBzazvF05g65cdHXGp1C7W5P
wwwKU2DgABB2t7N7z5A69LnryBRw4zUYDRRYLTYlBlYgg+xILm2c0OrBdxJgLJa7JE50Eo25
d3PFwt9J0gYvqy6sPFLl9So0sDg9zm0hKQtXOP5kgropUFGrNoJI+mjwF4rYLRBVzZwNAvlO
OhEvHubBo3mEllv4x+FeptwXZxlk7gUsdqI8AxnFB8K9wi6FVQARAQABtBtEYWxlIDxyZGFs
ZWsxOTY3QGdtYWlsLmNvbT6JAk4EEwEIADgCGyMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AW
IQQSG1h01ruv/WNXc3Q3RqOgiQH1GwUCYVJy8gAKCRA3RqOgiQH1G+waEACeTZCt77jnRAmQ
AV7otKuZekDWiLi3Eig8tj5ZJiCNSYA/hIxzmexRP0GMqjitcXK1iGwWcvMzzvIq30GAjIfB
4BR38cnXbtBa6fNewiT7QaZe/Hn6yBRldXNQypzbHy+/o27bUEy+oX4rE7etUgEHQAjuw7xz
XFWg4tH1/KJvsOVY5upnWc5LdxYhsuQ3dQD4b22GsK0pOBDfb9PiirYM8eGKvrVuq4E/c75z
lDDFhINl18lNZ9D0ZFL3IkTjHsAAqFH9uhnnEB8CWdHbBewPEfRaOhBUYWZ3Q8uTkmDgZT8q
D9jlvLEdw7Nh2ApdxoepnI/4D+ql2Gr4DtH7SEPydr5gcf1Qr/2bXRb1hAYnIVcbncs/Bm3Z
bkRKPVWMfE3Fusa+p5hMzixk0YysMaTHlc7mYRYAEZGnPMXnmcCbetwARU7A0yz1M1kCMOAQ
Lsz8KH5kv3cRenMB6SFfjND2JfAK61H5TtnPq3L8noS2ZykRYxq9Nm3X64O1tJojIKBoZFr8
AwYNCvqC6puUyGMuzHPh7jPof8glfrrEKIYUvNPGMDoVX3IGetxh/9l6NcxgFA4JGoR+LS3C
zmeNrwlllAe3OEUfKoWVQ+pagpSdM+8hHolaSda4Ys66Z3fCR4ZvcTqfhTAVskpqdXa4isAk
7vTcXu3L499ttywEp7rJTbkCDQRhUnImARAAncUdVhmtRr59zqpTUppKroQYlzR0jv8oa7DG
K4gakTAT2N7evnI9wpssmzyVk8VEiLzhnFQ/Ol3FRt6hZCXDJt0clyHOyTfvz/MNFttWuZTc
mLpSvmRR6VRjAH+Tz3Eam2xUw3PGuH97BcXQ3NnX3msv1UDxtxxBu6e2YrdeOhrCUSgzokcJ
98ChUNy934cgepPybAI12lSWqVFQ1aG7jExZfiUk+333fPSDbpKoZbTW5YJLXbycmW/C1IWL
qYQyNjRWKaGoJtUWFhhmNiOQct7n90aKivNVPavmN+UQ9LlMaINtf9T6XCzLfogCFsulDCDJ
0yNQLDTurHaB4E71xoctgXmLLq9z1RQ0W2XiVAAOZQj6K3+d0AOUjDhCQ2QW8dUSq0ckkZXV
DKVJOGS8Nhf2eIWIqRnP3AcUiiaiFGqUaVUmUAZ6h/oJmgghEu/1S+pcuUKU5i69+XCZ3hH2
Jzwzbf7K+FAIkOhCfHncF8i1N1pk00pOVykNnqHTfFo3qFusHt0ZWgXVnnn4pYdXqZNoDhvF
BRE5Vm4k/k96Pw8HRx6Os6eFSRrlqGzRgqsu86FekxusXB9UGv4lJhtU/J+8MRWsh22K718s
DbQnABicGKFz1qQlWvcf59oTByhLINJCBt1WXl+TzJDXepr3QSkqmK41dO9Hob97C9dMiK8A
EQEAAYkCNgQYAQgAIAIbDBYhBBIbWHTWu6/9Y1dzdDdGo6CJAfUbBQJhUnLyAAoJEDdGo6CJ
AfUbVHIQAKSWw620vPhR3A/njU2z77F3z/Jk+HTKdE3fIyWSWdkYN7CBFL0NguOMP30WZ+qE
sJhZu7T5hf251MwQUUt27xlfnKYOmQs7CqONlXuXlGZI6WufrUjxNcVz+5gJsqvUWuuJWsgg
sDmE92IBnfG/f81fPHWQyfr/SF4wYDMyoFp5xCCQpp1zB63iuFvvrhxBkEHzmbRtVDOhl0Xp
BVEDR1w3QRACw9QJD/KM05Czv9JNQYlwinWO/OaQ9cMlUpKLgswUPg9IZ5vucxScfuAUA5uC
B1jlAQ8ZPlVukBmbEv5RGOv+lpuEbA3YDMVtEeH4YMFbjt/+vH3Cr2vTbp5JlpByLburJEH0
WXZLUawEfUsZvVwpOuJK75vaa2HYXee+Cb3iCIzwfIfctdlqzUcbGRczlRNM59hpvj4z29Gh
3kAxVHItAYq54ikxQ9l4hQ8s9sLYPbX/WtcBxNX8crBSw0FLnmzGleVEtBHyqtt5CLzQNgrj
GYWl1vKDUmRPw1CdZ1c+fMN9CY11jOM5B5ZnqZWfDeVYO2iJ5SuvTycChexCb8WYn1bdCBIo
bBtga2RBXbVt4Mh9E4owsszefn51MwfjXxB20Fc5k3GU1AVpTCMs3ayYCzo0b2pvEvdjtDcA
CYLEFPWgaFX9iQAM/CDfKvTtvgGWpqtCL2raq/mQoJEU
Message-ID: <63351d99-e387-0838-6f18-8a67ca8e5341@gmail.com>
Date: Sat, 23 Sep 2023 09:48:41 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
Firefox/91.0 SeaMonkey/2.53.17
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply
MIME-Version: 1.0
In-Reply-To: <CAK2H+ee7TKZ5YzeWZ+Ps_2E6qY5xwAcirLp83oVy1L+jyz7j8w@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="------------72D3B3E915EB0650D4D1B9E0"
X-Archives-Salt: 19e4552c-f8c4-4766-9b4e-ac8a9a96dcd4
X-Archives-Hash: 60f58e1a9afeaba53c70f7f629739854
This is a multi-part message in MIME format.
--------------72D3B3E915EB0650D4D1B9E0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Mark Knecht wrote:
>
>
> On Sat, Sep 23, 2023 at 6:41 AM Dale <rdalek1967@gmail.com
> <mailto:rdalek1967@gmail.com>> wrote:
> >
> > Mark Knecht wrote:
> >
> >
> >
> > On Sat, Sep 23, 2023 at 5:05 AM Dale <rdalek1967@gmail.com
> <mailto:rdalek1967@gmail.com>> wrote:
> > <SNIP>
> > > If you need more info, let me know. If you know the command, that
> might
> > > help too. Just in case it is a command I'm not familiar with.
> > >
> > > Thanks.
> > >
> > > Dale
> > >
> > > :-) :-)
> >
> > You can use the iperf command to do simple raw speed testing.
> >
> > For instance, on your server open a terminal through ssh and run
> >
> > iperf -s
> >
> > It should tell you the server is listening.
> >
> > On your desktop machine run
> >
> > iperf -c 192.168.86.119
> >
> > (replace with the IP of your server)
> >
> > It runs for 5-10 seconds and then reports what it sees
> > as throughput.
> >
> > Remember to Ctrl-C the server side when you're done.
> >
> > HTH,
> > Mark
> >
> >
> >
> > I had to install those. On Gentoo it's called iperf3 but it works.
> Anyway, this is what I get from running the command on the NAS box to
> my main rig.
> >
> >
> > root@nas:~# iperf -c 10.0.0.4
> > tcp connect failed: Connection refused
> > ------------------------------------------------------------
> > Client connecting to 10.0.0.4, TCP port 5001
> > TCP window size: -1.00 Byte (default)
> > ------------------------------------------------------------
> > [ 1] local 0.0.0.0 port 0 connected with 10.0.0.4 port 5001
> > root@nas:~#
> >
> >
> > This is when I try to run from my main rig to the NAS box.
> >
> >
> > root@fireball / # iperf3 -c 10.0.0.7
> > iperf3: error - unable to connect to server - server may have
> stopped running or use a different port, firewall issue, etc.:
> Connection refused
> > root@fireball / #
> >
> >
> > I took what you said to mean to run from the NAS box. I tried both
> just in case I misunderstood your meaning by server. ;-)
> >
> > Ideas?
> >
> > Dale
>
> I thought the instructions were clear but let's try again.
>
> When using iperf YOU have to set up BOTH ends of the path, so:
>
> 1) On one end - let's say it's your NAS server - open a terminal. In
> that terminal type
>
> mark@plex:~$ iperf -s
> ------------------------------------------------------------
> Server listening on TCP port 5001
> TCP window size: 128 KByte (default)
> ------------------------------------------------------------
>
> 2) Then, on your desktop machine that wants to talk to the NAS server
> type this command,
> replacing my service IP with your NAS server IP
>
> mark@science2:~$ iperf -c 192.168.86.119
> ------------------------------------------------------------
> Client connecting to 192.168.86.119, TCP port 5001
> TCP window size: 85.0 KByte (default)
> ------------------------------------------------------------
> [ 1] local 192.168.86.43 port 40320 connected with 192.168.86.119
> port 5001
> [ ID] Interval Transfer Bandwidth
> [ 1] 0.0000-10.0808 sec 426 MBytes 354 Mbits/sec
> mark@science2:~$
>
> In this case, over my wireless network, I'm getting about 354Mb/S.
> Last time
> I checked it I hooked a cable between the 2 rooms I got about 900Mb/s.
Oh. My pepper sauce was getting loud and my eyes were watery. Now that
I got that done, I can see better after opening the doors a few
minutes. This is what I get now. My NAS box, running it first:
root@nas:~# iperf -s
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size: 128 KByte (default)
------------------------------------------------------------
>From main rig, running NAS box command first and it appeared to be waiting.
root@fireball / # iperf3 -c 10.0.0.7
iperf3: error - unable to connect to server - server may have stopped
running or use a different port, firewall issue, etc.: Connection refused
root@fireball / #
So, it appears to be waiting but my main rig isn't getting it. Then it
occurred my VPN might be affecting this somehow. I stopped it just in
case. OK, same thing. I did run the one on the NAS box first, since I
assume it needs to be listening when I run the command on my main rig.
After stopping the VPN, I ran both again.
Just so you know the machine is reachable, I am ssh'd into the NAS box
and I also have it mounted and copying files over with rsync. Could my
router be blocking this connection? I kinda leave it at the default
settings. Read somewhere those are fairly secure.
I'm working in garden a bit so may come and go at times. I'm sure you
doing other things too. :-D
Dale
:-) :-)
--------------72D3B3E915EB0650D4D1B9E0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Mark Knecht wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAK2H+ee7TKZ5YzeWZ+Ps_2E6qY5xwAcirLp83oVy1L+jyz7j8w@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr"><br>
<br>
On Sat, Sep 23, 2023 at 6:41 AM Dale <<a
href="mailto:rdalek1967@gmail.com" moz-do-not-send="true">rdalek1967@gmail.com</a>>
wrote:<br>
><br>
> Mark Knecht wrote:<br>
><br>
><br>
><br>
> On Sat, Sep 23, 2023 at 5:05 AM Dale <<a
href="mailto:rdalek1967@gmail.com" moz-do-not-send="true">rdalek1967@gmail.com</a>>
wrote:<br>
> <SNIP><br>
> > If you need more info, let me know. If you know the
command, that might<br>
> > help too. Just in case it is a command I'm not
familiar with.<br>
> ><br>
> > Thanks.<br>
> ><br>
> > Dale<br>
> ><br>
> > :-) :-)<br>
><br>
> You can use the iperf command to do simple raw speed
testing.<br>
><br>
> For instance, on your server open a terminal through ssh
and run<br>
><br>
> iperf -s<br>
><br>
> It should tell you the server is listening.<br>
><br>
> On your desktop machine run<br>
><br>
> iperf -c 192.168.86.119<br>
><br>
> (replace with the IP of your server)<br>
><br>
> It runs for 5-10 seconds and then reports what it sees <br>
> as throughput.<br>
><br>
> Remember to Ctrl-C the server side when you're done.<br>
><br>
> HTH,<br>
> Mark<br>
><br>
><br>
><br>
> I had to install those. On Gentoo it's called iperf3 but
it works. Anyway, this is what I get from running the command
on the NAS box to my main rig. <br>
><br>
><br>
> root@nas:~# iperf -c 10.0.0.4<br>
> tcp connect failed: Connection refused<br>
>
------------------------------------------------------------<br>
> Client connecting to 10.0.0.4, TCP port 5001<br>
> TCP window size: -1.00 Byte (default)<br>
>
------------------------------------------------------------<br>
> [ 1] local 0.0.0.0 port 0 connected with 10.0.0.4 port
5001<br>
> root@nas:~#<br>
><br>
><br>
> This is when I try to run from my main rig to the NAS box.
<br>
><br>
><br>
> root@fireball / # iperf3 -c 10.0.0.7<br>
> iperf3: error - unable to connect to server - server may
have stopped running or use a different port, firewall issue,
etc.: Connection refused<br>
> root@fireball / #<br>
><br>
><br>
> I took what you said to mean to run from the NAS box. I
tried both just in case I misunderstood your meaning by server.
;-)<br>
><br>
> Ideas?<br>
><br>
> Dale<br>
<div><br>
</div>
<div>I thought the instructions were clear but let's try again.</div>
<div><br>
</div>
<div>When using iperf YOU have to set up BOTH ends of the path,
so:</div>
<div><br>
</div>
<div>1) On one end - let's say it's your NAS server - open a
terminal. In that terminal type</div>
<div><br>
</div>
<div><span style="font-family:monospace"><span
style="font-weight:bold;color:rgb(84,255,84)">mark@plex</span><span
style="color:rgb(0,0,0)">:</span><span
style="font-weight:bold;color:rgb(84,84,255)">~</span><span
style="color:rgb(0,0,0)">$ iperf -s
</span><br>
------------------------------------------------------------
<br>
Server listening on TCP port 5001
<br>
TCP window size: 128 KByte (default)
<br>
------------------------------------------------------------
<br>
</span><br>
2) Then, on your desktop machine that wants to talk to the NAS
server type this command,<br>
</div>
<div>replacing my service IP with your NAS server IP</div>
<div><br>
</div>
<div><span style="font-family:monospace"><span
style="font-weight:bold;color:rgb(84,255,84)">mark@science2</span><span
style="color:rgb(0,0,0)">:</span><span
style="font-weight:bold;color:rgb(84,84,255)">~</span><span
style="color:rgb(0,0,0)">$ iperf -c 192.168.86.119 </span><br>
------------------------------------------------------------
<br>
Client connecting to 192.168.86.119, TCP port 5001
<br>
TCP window size: 85.0 KByte (default)
<br>
------------------------------------------------------------
<br>
[ 1] local 192.168.86.43 port 40320 connected with
192.168.86.119 port 5001
<br>
[ ID] Interval Transfer Bandwidth
<br>
[ 1] 0.0000-10.0808 sec 426 MBytes 354 Mbits/sec
<br>
<span style="font-weight:bold;color:rgb(84,255,84)">mark@science2</span><span
style="color:rgb(0,0,0)">:</span><span
style="font-weight:bold;color:rgb(84,84,255)">~</span><span
style="color:rgb(0,0,0)">$ </span><br>
</span></div>
<div><span style="font-family:monospace"><span
style="color:rgb(0,0,0)"><br>
</span></span></div>
In this case, over my wireless network, I'm getting about
354Mb/S. Last time<br>
I checked it I hooked a cable between the 2 rooms I got about
900Mb/s. </div>
</blockquote>
<br>
<br>
Oh. My pepper sauce was getting loud and my eyes were watery. Now
that I got that done, I can see better after opening the doors a few
minutes. This is what I get now. My NAS box, running it first: <br>
<br>
root@nas:~# iperf -s<br>
------------------------------------------------------------<br>
Server listening on TCP port 5001<br>
TCP window size: 128 KByte (default)<br>
------------------------------------------------------------<br>
<br>
<br>
From main rig, running NAS box command first and it appeared to be
waiting. <br>
<br>
<br>
root@fireball / # iperf3 -c 10.0.0.7<br>
iperf3: error - unable to connect to server - server may have
stopped running or use a different port, firewall issue, etc.:
Connection refused<br>
root@fireball / # <br>
<br>
<br>
So, it appears to be waiting but my main rig isn't getting it. Then
it occurred my VPN might be affecting this somehow. I stopped it
just in case. OK, same thing. I did run the one on the NAS box
first, since I assume it needs to be listening when I run the
command on my main rig. After stopping the VPN, I ran both again.
<br>
<br>
Just so you know the machine is reachable, I am ssh'd into the NAS
box and I also have it mounted and copying files over with rsync.
Could my router be blocking this connection? I kinda leave it at
the default settings. Read somewhere those are fairly secure. <br>
<br>
I'm working in garden a bit so may come and go at times. I'm sure
you doing other things too. :-D <br>
<br>
Dale <br>
<br>
:-) :-) <br>
</body>
</html>
--------------72D3B3E915EB0650D4D1B9E0--