[Mageia-discuss] home network using broadband router

[WALKER RICHARD]

Moving to the client machine and again using MCC to set up "Access NFS
shared drives and directories" you may again be prompted to install
some NFS client stuff and then you should see a disappointingly empty
server list.

Just click the Search Servers button on the right of the screen and
wait a wee while. With good luck and a following wind you should see
the address of your server PC appear with a little "expand me" arrow
beside it.

When you click on that you should see the name of your server's shared
directory/directories. Highlight the one you are setting up and go
through the buttons at the bottom of the screen.

Choose a mount point - for simplicity I let it use the default offered
of /mnt/Videos

Mount it.

Done. You will be asked if you want to save the changes to /etc/fstab.
Say yes and the next time you boot it will try to mount this share
again. If your server PC is always up first then that should be OK. If
you're like me then there is no guarantee it will be up. You might
prefer to be able to mount it yourself when you want it. That is what
the Options button will help you sort out.

If all of that has worked then you can restore the personal firewall
on each PC. First on the server, uncheck the Everything option and
make sure the NFS server box is ticked. On the client PC you should be
able just to restore whatever settings you had before.

If you got this far with no show-stopping errors then life will have
just got a little bit brighter.

If something went wrong then shout. I'll check back on Friday evening,
but you may find the answer before that.

good luck,

Richard

On 08/03/2012, WALKER RICHARD <richard.j.walker at ntlworld.com> wrote:
> Now back to the NFS problem. I have just gone through the procedure
> described in the draknfs.html guide you referenced in your original
> post elsewhere. I am using a Mageia 1 machine as the provider of the
> share (the server) and a Mandriva 2010.0 machine as the client.
>
> The first thing is to make sure the personal firewall does not get in
> the way so I disabled it on both PCs.
>
> Next, on the server PC I selected the "Share drives and directories
> using NFS" option on "Network Sharing" in MCC.
>
> As I hadn't done this before it prompted me to install some missing
> NFS packages and then presented me with the screen where I could "Add"
> a share. The resulting popup let me browse to a folder for sharing (I
> chose ~/Videos) .
>
> The next box on the form asks for information about which hosts I want
> to share with. There are a few options, but the simplest is to use the
> proffered 192.168.0.0/8 choice. You can maybe guess that the "/8"
> tells how many zero bits are in our net mask and as the last octet is
> zero then all bits are zero, so it is 8.
>
> The next box gives User ID Mapping options. I left that at "No user
> UID mapping". I have the same UID on all of my PCs so that works fine
> for me.
>
> The only other thing I changed was in the "Advanced" section (which
> expands) where I changed the "Read-Only share" from "yes" to "no".
>
> OK that and your entry appears in the left hand window. The actual
> configuration you have just completed can be found in /etc/exports -
> take a look if you like.
>
>
>
>
>
> On 08/03/2012, WALKER RICHARD <richard.j.walker at ntlworld.com> wrote:
>> Right then, I don't think we need to know any more. From here it looks
>> like your LAN should be fully functioning. Before we try setting up
>> your NFS shares it might be worthwhile to take a few moments clearing
>> up a couple of points about networking - things I learned the hard
>> way, and now so are you :-).
>>
>>> I do not think I am able to assign fixed IP addresses.
>>
>> Well, you can. Don't confuse fixed addresses with static addresses you
>> might get from an ISP. If you had chosen manual setup in MCC when
>> configuring your ethernet card you could have typed in a fixed address
>> of your own choosing. Of course you need to know what you are doing so
>> that you can avoid addresses which your router's DHCP could, in
>> theory, hand out to some later connected device. Then you would have
>> two hosts with the same address and all sorts of lost connection
>> issues!
>>
>>> The computers and router are connected via ethernet cables, within a
>>> house so I assume that is considered a "same" network.
>>
>> In fact it is possible to have multiple networks operating on one
>> common set of installed hardware, but this is seldom considered
>> necessary in a domestic setting. It is the addresses and network mask
>> which "define" separate logical networks within a single physical
>> network.
>> A quick example; on my 192.168.0.? network I have two PCs and a
>> firewall. My router, although wired in to the same network, has an
>> address of 192.168.1.1. That address does not exist in my LAN. If I
>> want to connect to my router I have to reconfigure a PC to have an
>> address in my router's network - 192.168.1.99 would do. It is the 1 in
>> the third octet which makes it a separate network. My LAN mask is 255
>> for that octet, which says all of the bits in this octet must match
>> for two addresses to be considered in the same net. (Same goes for the
>> 192 and the 168). Only the fourth octet (mask value 0) can be any 8
>> bit number.
>>
>>
>> On 08/03/2012, Florian Hubold <doktor5000 at arcor.de> wrote:
>>> Am 07.03.2012 14:04, schrieb Cazacu Bogdan:
>>>> Wont it be simpler to post the output from ifconfig here? And
>>>> aventually
>>>> a
>>>> traceroute output? :)
>>>> Honestly i've tried to understand what is the problem (i'm [still]
>>>> guessing it's dhcp related by the looks of the problem and replies) but
>>>> i'm not sure i got it...
>>> Yep, that would be rather helpful as a beginning.
>>> Unrelated: Top-posting is ugly ;)
>>>
>>> Some other notes, from what i read in the thread: most routers
>>> also allow for what is often referenced as "static DHCP" which means
>>> statically assigning specific IP adresses via DHCP, always to the
>>> same machine based on it's MAC adress, which is essentially
>>> the same as manually-configured static adresses, but
>>> with a lot less hassle and no manual setup required.
>>>
>>> Also one should not mangle the external IP adress (which is usually
>>> assigned by the ISP, under which your router is visible to the internet,
>>> and normally can't be changed manually) with your internal adresses.
>>>
>>> That other part are the IP adresses which you use on your local network,
>>> which you can setup any way you want, and that has nothing to do with
>>> your ISP.
>>>
>>> Another thing: When editing /etc/hosts, i wouldn't remove the loopback
>>> entries, but only add additional entries if you really need to.
>>> This is also another drawback if you manually assign IP adresses
>>> and can be easily avoided by properly configuring/using DHCP.
>>>>
>>>> -----Original Message-----
>>>> From: mageia-discuss-bounces at mageia.org
>>>> [mailto:mageia-discuss-bounces at mageia.org] On Behalf Of Florian Hubold
>>>> Sent: Wednesday, March 07, 2012 12:54 PM
>>>> To: mageia-discuss at mageia.org
>>>> Subject: Re: [Mageia-discuss] home network using broadband router
>>>>
>>>> Guys, remotely diagnosing networking problems without having all the
>>>> relevant information, like the exact IP adresses (if they are from any
>>>> private range of either class A, B or C networks, they're not even
>>>> routable over the internet, so don't need to be anonymized) the exact
>>>> internal routers adress, netmasks and maybe routing tables will just be
>>>> a
>>>> wild guessing back and forth.
>>>>
>>>> Also firewalls should be switched off at both client computers to rule
>>>> those out.
>>>>
>>>>
>>>
>>>
>>
>