You are not logged in.
i have a nfs drive set up on my server which i access from my laptop. well i copy a large file over to it and i only get about 50KB/s, which is my internet download speed. i have the sneaking suspicion it's going out to the internet first.. how can i test this and/or fix it? both computers are set up with static addresses on their own, do i have to disable DHCP on the router as well, or is it ok to leave that enabled for other machines in the house?
or, how do you set up NFS with dynamic IP addresses? thanks..
karsten
Offline
ok, I have no idea on how to solve your problem and maybe I'm totally wrong here, so it's just a thought: what is your upload speed? If the file's going through the internet the download speed can't be higher than your upload speed, maybe this could help to check it, if your on an asynchronous internet connection of course ....
Offline
do i have to disable DHCP on the router as well
I don't know if you "have" to, but, I do. Then I assign addresses to all the boxes in my network.
how do you set up NFS with dynamic IP addresses?
Use the hostname (in /etc/rc.conf) for your box instead of an address.
I have no idea re: the issue of speed of transfer.
Offline
Use
traceroute hostname or
traceroute ip-address
to check how if the connection stays local or not.
If you're doing it from the laptop , put in the ip-address of the nfs server.
Another possibility : a slow wireless connection between the laptop and your router.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
(A works at time B) && (time C > time B ) ≠ (A works at time C)
Offline
ok thanks for the help guys, really appreciate it. i've checked that there is just one hop between the client and server with
traceroute, and used both ifconfig and nfsstat to see if there were excessive packet errors going on, which there doesn't appear to be. what else could be causing the slowness? and yes bluepoet, upload speed is only ~11-14k so that would have ruled that out
maybe i need to test with a wired connection between the two systems and rule out the wireless issue.
edit -- i just ran a ping from the server to the client... does this look suspicious at all?
$ ping 192.168.1.104
PING 192.168.1.104 (192.168.1.104) 56(84) bytes of data.
64 bytes from 192.168.1.104: icmp_seq=1 ttl=64 time=5.58 ms
64 bytes from 192.168.1.104: icmp_seq=2 ttl=64 time=4.61 ms
64 bytes from 192.168.1.104: icmp_seq=2 ttl=64 time=7.61 ms (DUP!)
64 bytes from 192.168.1.104: icmp_seq=3 ttl=64 time=4.75 ms
64 bytes from 192.168.1.104: icmp_seq=3 ttl=64 time=7.75 ms (DUP!)
64 bytes from 192.168.1.104: icmp_seq=3 ttl=64 time=10.7 ms (DUP!)
64 bytes from 192.168.1.104: icmp_seq=4 ttl=64 time=9.83 ms
64 bytes from 192.168.1.104: icmp_seq=4 ttl=64 time=12.8 ms (DUP!)
64 bytes from 192.168.1.104: icmp_seq=5 ttl=64 time=6.83 ms
64 bytes from 192.168.1.104: icmp_seq=6 ttl=64 time=10.8 ms
64 bytes from 192.168.1.104: icmp_seq=7 ttl=64 time=6.83 ms
64 bytes from 192.168.1.104: icmp_seq=7 ttl=64 time=9.83 ms (DUP!)
64 bytes from 192.168.1.104: icmp_seq=7 ttl=64 time=14.8 ms (DUP!)
64 bytes from 192.168.1.104: icmp_seq=8 ttl=64 time=4.83 ms
64 bytes from 192.168.1.104: icmp_seq=9 ttl=64 time=10.4 ms
64 bytes from 192.168.1.104: icmp_seq=10 ttl=64 time=4.55 ms
64 bytes from 192.168.1.104: icmp_seq=10 ttl=64 time=7.55 ms (DUP!)
64 bytes from 192.168.1.104: icmp_seq=11 ttl=64 time=9.83 ms
64 bytes from 192.168.1.104: icmp_seq=11 ttl=64 time=12.8 ms (DUP!)
Offline
ok thanks for the help guys, really appreciate it. i've checked that there is just one hop between the client and server with
traceroute, and used both ifconfig and nfsstat to see if there were excessive packet errors going on, which there doesn't appear to be. what else could be causing the slowness? and yes bluepoet, upload speed is only ~11-14k so that would have ruled that outmaybe i need to test with a wired connection between the two systems and rule out the wireless issue.
edit -- i just ran a ping from the server to the client... does this look suspicious at all?
$ ping 192.168.1.104
PING 192.168.1.104 (192.168.1.104) 56(84) bytes of data.
64 bytes from 192.168.1.104: icmp_seq=1 ttl=64 time=5.58 ms
64 bytes from 192.168.1.104: icmp_seq=2 ttl=64 time=4.61 ms
64 bytes from 192.168.1.104: icmp_seq=2 ttl=64 time=7.61 ms (DUP!)
64 bytes from 192.168.1.104: icmp_seq=3 ttl=64 time=4.75 ms
64 bytes from 192.168.1.104: icmp_seq=3 ttl=64 time=7.75 ms (DUP!)
64 bytes from 192.168.1.104: icmp_seq=3 ttl=64 time=10.7 ms (DUP!)
64 bytes from 192.168.1.104: icmp_seq=4 ttl=64 time=9.83 ms
64 bytes from 192.168.1.104: icmp_seq=4 ttl=64 time=12.8 ms (DUP!)
64 bytes from 192.168.1.104: icmp_seq=5 ttl=64 time=6.83 ms
64 bytes from 192.168.1.104: icmp_seq=6 ttl=64 time=10.8 ms
64 bytes from 192.168.1.104: icmp_seq=7 ttl=64 time=6.83 ms
64 bytes from 192.168.1.104: icmp_seq=7 ttl=64 time=9.83 ms (DUP!)
64 bytes from 192.168.1.104: icmp_seq=7 ttl=64 time=14.8 ms (DUP!)
64 bytes from 192.168.1.104: icmp_seq=8 ttl=64 time=4.83 ms
64 bytes from 192.168.1.104: icmp_seq=9 ttl=64 time=10.4 ms
64 bytes from 192.168.1.104: icmp_seq=10 ttl=64 time=4.55 ms
64 bytes from 192.168.1.104: icmp_seq=10 ttl=64 time=7.55 ms (DUP!)
64 bytes from 192.168.1.104: icmp_seq=11 ttl=64 time=9.83 ms
64 bytes from 192.168.1.104: icmp_seq=11 ttl=64 time=12.8 ms (DUP!)
Maybe a foobar cable somewhere? These pingtimes look awefully high for a very small local network.
Just for reference, when I ping another computer, I get this:
[glenn@polaris ~]$ ping 192.168.0.254
PING 192.168.0.254 (192.168.0.254) 56(84) bytes of data.
64 bytes from 192.168.0.254: icmp_seq=1 ttl=255 time=0.408 ms
64 bytes from 192.168.0.254: icmp_seq=2 ttl=255 time=0.282 ms
64 bytes from 192.168.0.254: icmp_seq=3 ttl=255 time=0.299 ms
64 bytes from 192.168.0.254: icmp_seq=4 ttl=255 time=0.389 ms
:?
Offline