[Sussex] Re: Setting up a simple home network

[Captain Redbeard]

 >Matthew Macdonald-Wallace wrote:
 >
 >My /etc/exports on my server looks like this:
 >
 >/mnt/files 192.168.0.1/255/255/255.0(sync) 
 >*(sync,no_subtree_check,rw)

OK, mine now reads:

/home/public 192.168.0.1/255/255/255.0(sync) 
*(sync,no_subtree_check,rw)

 >I've then edited my /etc/fstab on my laptop to contain:...

Don't think I need this, /etc/fstab is only used at boot-up 
time (?) and these computers are rarely ever turned off.

 >It seems to me that the main problem is the IP Addressing, 
 >try running
 >
 ># ifconfig eth0 192.168.1.x

Tried that and all that happened was that the command line 
came straight back, no output at all.

 >Steve Dobson wrote:
 >
 >Not quite right.  It should read something like this:...

I know, I know, see my revision posting.

 >If you try "ifconfig -a" you should see an entry for the 
 >NIC (eth0).

Did that and it does list an entry for eth0 on both machines.

 >If you see an entry then try this (on machine-name-1):
 >ifconfig eth0 192.168.0.1 netmask 255.255.0.0 broadcast 
 >192.168.255.255
 >
 >and this (on machine-name-1):
 >ifconfig eth0 192.168.0.2 netmask 255.255.0.0 broadcast 
 >192.168.255.255
 >
 >Then should then be able to talk to one another.
 >Try a broadcast ping which should get every machine on 
your >network to
 >respond:
 >
 >ping 192.168.255.255

My (slightly revised) commands were as follows:

On the server:
ifconfig eth0 192.168.0.1 netmask 255.255.255.0 broadcast 
192.168.255.255

On the client:
ifconfig eth0 192.168.0.2 netmask 255.255.255.0 broadcast 
192.168.255.255

And now on the client:
ping -b 192.168.255.255

Result:
PING 192.168.255.255 (192.168.255.255) 56(84) bytes of data.
64 bytes from 192.168.0.2: icmp_seq=1 ttl=64 time=0.206ms
64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=0.586ms (DUP!)
64 bytes from 192.168.0.2: icmp_seq=2 ttl=64 time=0.043ms
64 bytes from 192.168.0.1: icmp_seq=2 ttl=64 time=0.144ms (DUP!)
64 bytes from 192.168.0.2: icmp_seq=3 ttl=64 time=0.024ms
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=0.118ms (DUP!)
etc...

With similar output on the server.


IT WORKED!!!


 >This is advanced stuff.  If you can't get the two machine 
 >to ping each other, then don't worry yet about protocol 
and >remote mounting of files.  This maybe want you want, 
but >learn to stand up before you try and run.

OK, I'm standing up, now how do I run?  The mount command 
still doesn't work!

Thanks for your help so far though!



Captain Redbeard





===========================================================
Linux user number 388693.
v2sw5+8C+JGhw5ln4/5pr6/7Ock1ma6/8l6+8Sw3+2e4t2b9Hen4+6g5+3
RHaIr9 Hackerkey.com 
===========================================================