[olug] NFS & @Home Networking

Jon thechunk at thechunk.dhs.org
Tue Aug 7 00:26:25 UTC 2001


route add -host <other ip> gw <this ip> on both machines.

I don't know all the implecations of doing this ( I am not a network guy ) but this works.

root at cx241544-e:~# route add -host teklady.dhs.org gw thechunk.dhs.org
root at cx241544-e:~# ping teklady.dhs.org
PING teklady.dhs.org (24.22.143.107): 56 octets data
64 octets from 24.22.143.107: icmp_seq=0 ttl=127 time=22.1 ms
64 octets from 24.22.143.107: icmp_seq=1 ttl=127 time=9.1 ms
64 octets from 24.22.143.107: icmp_seq=2 ttl=127 time=17.5 ms
64 octets from 24.22.143.107: icmp_seq=3 ttl=127 time=9.9 ms
64 octets from 24.22.143.107: icmp_seq=4 ttl=127 time=62.9 ms
64 octets from 24.22.143.107: icmp_seq=5 ttl=127 time=11.8 ms
64 octets from 24.22.143.107: icmp_seq=6 ttl=127 time=9.2 ms
64 octets from 24.22.143.107: icmp_seq=7 ttl=127 time=12.6 ms
64 octets from 24.22.143.107: icmp_seq=8 ttl=127 time=9.0 ms
64 octets from 24.22.143.107: icmp_seq=9 ttl=127 time=10.2 ms
64 octets from 24.22.143.107: icmp_seq=10 ttl=127 time=8.8 ms
64 octets from 24.22.143.107: icmp_seq=11 ttl=127 time=9.2 ms
64 octets from 24.22.143.107: icmp_seq=12 ttl=127 time=9.6 ms
64 octets from 24.22.143.107: icmp_seq=13 ttl=127 time=18.8 ms
64 octets from 24.22.143.107: icmp_seq=14 ttl=127 time=12.3 ms
64 octets from 24.22.143.107: icmp_seq=15 ttl=127 time=18.0 ms

--- teklady.dhs.org ping statistics ---
16 packets transmitted, 16 packets received, 0% packet loss
round-trip min/avg/max = 8.8/15.6/62.9 ms
root at cx241544-e:~# route del teklady.dhs.org
root at cx241544-e:~# ping teklady.dhs.org
PING teklady.dhs.org (24.22.143.107): 56 octets data
64 octets from 24.22.143.107: icmp_seq=0 ttl=127 time=36.0 ms
64 octets from 24.22.143.107: icmp_seq=1 ttl=127 time=34.4 ms
64 octets from 24.22.143.107: icmp_seq=2 ttl=127 time=68.1 ms
64 octets from 24.22.143.107: icmp_seq=3 ttl=127 time=104.2 ms
64 octets from 24.22.143.107: icmp_seq=4 ttl=127 time=35.3 ms
64 octets from 24.22.143.107: icmp_seq=5 ttl=127 time=33.1 ms
64 octets from 24.22.143.107: icmp_seq=6 ttl=127 time=49.9 ms
64 octets from 24.22.143.107: icmp_seq=7 ttl=127 time=45.2 ms
64 octets from 24.22.143.107: icmp_seq=8 ttl=127 time=59.0 ms
64 octets from 24.22.143.107: icmp_seq=9 ttl=127 time=26.4 ms
64 octets from 24.22.143.107: icmp_seq=10 ttl=127 time=85.8 ms
^[64 octets from 24.22.143.107: icmp_seq=11 ttl=127 time=22.9 ms
^H64 octets from 24.22.143.107: icmp_seq=12 ttl=127 time=95.6 ms

A noticable change in ping times.

On Mon, Aug 06, 2001 at 06:44:16PM +0000, Joe Vernon wrote:
> I've been using Linux for about 2 years now, but I don't have very much 
> experience with networking, mainly because I only had one computer. Recently 
> I did pick up a second PC. Setting up @Home was a breeze. I purchased a 
> second IP address from Cox, I got an old 10 MBit hub from a friend who 
> didn't need it, and I had it working very quickly. I then wanted to set up 
> some NFS shares between the 2 machines. I read the NFS howto and I managed 
> to set everything up without much trouble. My problem is that whenever I 
> send anything back and forth with NFS it seems to be going through the 
> internet as I am getting stuck with @Home's 256 Kbit upload cap which is 
> painfully slow for large files. How do I make this NFS traffic stay local 
> and use the full 10 Mbit transfer speed? I would imagine this involves 
> setting up some type of local IP addresses. Can this be done without adding 
> more NIC cards? I know the cards are cheap but I would really like to avoid 
> adding any new hardware if possible.
> 
> Thanks in advance for any help
> 
> _________________________________________________________________
> Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: olug-unsubscribe at bstc.net
> For additional commands, e-mail: olug-help at bstc.net

---------------------------------------------------------------------
To unsubscribe, e-mail: olug-unsubscribe at bstc.net
For additional commands, e-mail: olug-help at bstc.net



More information about the OLUG mailing list