Mark Knecht wrote: > <SNIP> > > > > 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 > > > > :-) :-) > > If you're running a VPN then you'll need someone at a higher pay grade > than me, but packetizing TCP packets into and out of VPN security is > certainly going to use CPU cycles and slow things down, at least a > little. No idea if that's what caused your gkrellm pictures. Also, any > network heavy apps, like playing video from the NAS or from the > Internet is also going to slow file transfers down. > > Your error message is telling you that something is in the way. > > Can you ping the NAS box? > > ping 10.0.0.7 > > Can you tracepath the NAS box? > > tracepath 10.0.0.7 > > Are you sure that 10.0.0.7 is the address of the NAS box? > > Do you have a /etc/hosts file to keep the names straight? > > HTH, > Mark > >
Sorry so long. I was working in the garden some when my neighbor called and wanted to move his mailbox. He got one of those pre-made things a long time ago and it is really to short. I dug a new hole, put in a piece of tubing that the mailbox post would slip over and then poured concrete around it. Should hold up now. Can't move it and the concrete isn't even dry yet. I really like a auger that fits on the back of a tractor especially when the road used to be a gravel road. Post hole diggers are a TON of hard work. Auger took less than a minute, with tractor at idle. LOL Anyway, mailbox is up and I got some sore joints. I sense meds coming pretty soon. :/ I can ping it. I always have the VPN running and believe it or not, I can connect to the NAS box, ping, transfer files and everything with it running. I just thought the VPN might affect that one thing for some reason. Anytime something odd is going on network wise, I stop the VPN first and test again. I rule that out first thing. I read the other replies and I think it is caching the data, the drives writes and catches up and then it asks for more data again. I can't imagine anything to do with the NAS box given it did the exact same thing with Truenas. If anything, I'd expect it to be on my main rig but the main rig has a lot more power and memory than the NAS box does. I suspect between the cache thing and encryption, that is the bottleneck. I also replaced the network card a week or so ago. Turned out it was a setting I needed to change. So, not a bad card either. I got to cool off and rest a bit. I may read some more replies later or again, after I get my wits back. :/ Dale :-) :-)
