Ok, kinda dumb question.. I'm TRYING to learn about networks more as tons of things I'm doing kinda require it.

I have SMBs, SSH and backups all working on my NAS. [Open Media Vault]

I'm trying to switch over to NFS's, tho.. as they're a bit faster since I'm fully on Linux here. When I add it, I need to set my client IP range.

While I'm not totally dumb on network stuff... I almost am. An ifconfig is here:
inet 10.0.0.16 netmask 255.255.255.0 broadcast 10.0.0.255
inet6 2601:1c0:6703:3370::2391 prefixlen 128 scopeid 0x0<global>
inet6 fe80::ba27:ebff:fe7d:695b prefixlen 64 scopeid 0x20<link>
inet6 2601:1c0:6703:3370:ba27:ebff:fe7d:695b prefixlen 64 scopeid 0x0<
global>
ether b8:27:eb:7d:69:5b txqueuelen 1000 (Ethernet)
RX packets 1632476 bytes 166918960 (159.1 MiB)
RX errors 0 dropped 9166 overruns 0 frame 0
TX packets 3061617 bytes 126864686 (120.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 6281 bytes 2822139 (2.6 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 6281 bytes 2822139 (2.6 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
-----
Do I set my range with the '127.0.0.1/24' or do I use my wifi '10.0.0.1/24'?

I know that I connect locally to all my Pi's and laptops using the 10.0.0.x... I'm not grasping what the NFS is asking me for and what I suppply it with. You know, I have like 10.0.0.178 - so 1/24, does that cover the 178???

Or am I fully off?



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2020/11/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (1337:3/129)

I'm trying to switch over to NFS's, tho.. as they're a bit faster since I'mfully on Linux here. When I add it, I need to set my client IP range.

inet 10.0.0.16 netmask 255.255.255.0 broadcast 10.0.0.255
inet 127.0.0.1 netmask 255.0.0.0

So... I *think* my two scopes are 10.0.0.16/24 & 127.0.0.1/8.

And I think that would cover my LAN and my WiFi. Does any of that sound right?



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2020/11/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (1337:3/129)

Do I set my range with the '127.0.0.1/24' or do I use my wifi '10.0.0.1/24'?

I know that I connect locally to all my Pi's and laptops using the 10.0.0.x... I'm not grasping what the NFS is asking me for and what I suppply it with. You know, I have like 10.0.0.178 - so 1/24, does that cover the 178???

Hey Paulie, I'm not really following what you're trying to do, but if it is what I think you're trying to do, then maybe you're way off.

127.0.0.1 is just the loopback device IP, i.e. localhost. Every machine has that and it's only addressable by the machine itself, not anything else.

10.0.0.1/24 is one IP address, in a /24 subnet, that is 1 of 254 possible IP addresses.

The actual network address would in this case be 10.0.0.0/24, and 10.0.0.1 would likely be your router, although some are configured to use the last usable IP so 10.0.0.254.

To explain what a /24 subnet means, think of it like this;

A subnet mask typically for a home network (254 hosts) would be 255.255.255.0 Each quad is 255 except the last which is 0, 255 is 8bits, so 3x8 bits = 24.

In Binary, this would be;
11111111.11111111.11111111.00000000

the reason why you see 255 is because in binary 11111111 is 255. To understand binary, reading right to left the value of each bit (1) is;
1, 2, 4, 8, 16, 32, 64, and 128.

Anyway, this is way off scope for what you asked, just thought I'd delve a little in to how IP addressing works. =)

Your NFS server will be the IP address of your NAS device, and you would access it in Linux on your client machine using the NAS's IP address.

Hope this isn't too confusing lol, ultimately, your client PC would just connect to the NFS server (your nas in this case) via it's IP (not your client pc's IP).

---
|14Best regards,
|11Ch|03rist|11ia|15n |11a|03ka |11Me|03aTLoT|11io|15N

|07── |08[|10eml|08] |15ml@erb.pw |07── |08[|10web|08] |15www.erb.pw |07───┐ |07── |08[|09fsx|08] |1521:1/158 |07── |08[|11tqw|08] |151337:1/101 |07┬──┘ |07── |08[|12rtn|08] |1580:774/81 |07─┬ |08[|14fdn|08] |152:250/5 |07───┘
|07── |08[|10ark|08] |1510:104/2 |07─┘

--- Mystic BBS v1.12 A47 2020/12/04 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (1337:1/101)

Re: NFS on a NAS; Need For Speed!
By: paulie420 to All on Wed Dec 23 2020 06:12 am

Howdy,

While I'm not totally dumb on network stuff... I almost am. An ifconfig is here:
inet 10.0.0.16 netmask 255.255.255.0 broadcast 10.0.0.255
Do I set my range with the '127.0.0.1/24' or do I use my wifi '10.0.0.1/24'?
I know that I connect locally to all my Pi's and laptops using the 10.0.0.x... I'm not grasping what the NFS is asking me for and what I suppply
it with. You know, I have like 10.0.0.178 - so 1/24, does that cover the 178???

Based on the information you provided, your "clients" fit in 10.0.0.0/24. I'm not sure what you are asking, but if you are wanting to limit your NFS access to clients within your LAN, then 10.0.0.0/24 will cover it.

127.0.0.1 wouldnt be used for NFS - since packets do not leave a system that are addressed to 127.0.0.1

...δεσ∩

... Another dream that failed. There's nothing sadder. Kirk, stardate 3417.3. --- SBBSecho 3.11-Linux
* Origin: I'm playing with ANSI+videotex - wanna play too? (1337:2/101)

10.0.0.1/24 is one IP address, in a /24 subnet, that is 1 of 254
possible IPaddresses.

The actual network address would in this case be 10.0.0.0/24, and 10.0.0.1would likely be your router, although some are configured to use the lastusable IP so 10.0.0.254.

First, thank you for all the information you the laid down. I extracted it and am appreciative!! I did figure out the correct range for my network... it was 10.0.0.1/24, and I learned all about CIDR notation while doing so. However, your explanation of subnets and why they work like they do is just as good as your explanation about gigabits vs gigabytes. :P

Thank you, again!



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2020/11/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (1337:3/129)

Based on the information you provided, your "clients" fit in
10.0.0.0/24. I'mnot sure what you are asking, but if you are wanting to limit your NFS accessto clients within your LAN, then 10.0.0.0/24 will cover it.

127.0.0.1 wouldnt be used for NFS - since packets do not leave a system thatare addressed to 127.0.0.1

Yes Deon... lol; most of my problem is not knowing how nets work. I'm quickly buttoning up my network and - don't laugh at me YET - am going to figure out a pfSense box... after gaining the specialized knowledge needed. :P

Working on just connecting TO this NFS first. Thanks.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2020/11/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (1337:3/129)

Am 23.12.20 schrieb paulie420@1337:3/129 in TQW_LINUX:

Hallo paulie420,

I have SMBs, SSH and backups all working on my NAS. [Open Media Vault]

Nice, I'm also using OMV in my home network, although an older version.

I'm trying to switch over to NFS's, tho.. as they're a bit faster since I'm fully on Linux here. When I add it, I need to set my client IP range.

Yes, you have to tell the NFS server which clients are allowed to connect
to the NFS shares.

Your provided ifconfig output shows this line:

inet 10.0.0.16 netmask 255.255.255.0 broadcast 10.0.0.255

So this computer is in the network 10.0.0.0/24 (/24 is equivalent to the netmask 255.255.255.0).

The "lo" address 127.0.0.1 is only reachable on this specific computer and applies to itself, it is the "loopback device" -- so it is not relevant
for your question.

Do I set my range with the '127.0.0.1/24' or do I use my wifi
'10.0.0.1/24'?

You have to use 10.0.0.0/24 (and not 10.0.0.1/24) in OMV.
"10.0.0.0" defines the whole network "10.x.x.x" and "/24" selects the part
of "10.x.x.x" according to the netmask 255.255.255.0, this results in: 10.0.0.1-10.0.0.254 as usable addresses.

So, enter 10.0.0.0/24 in OMV for your NFS share :)

Another hint on NFS: It can be a bit tricky regarding the user/group
access rights -- make sure your user(s) have the same user ID (UID) and
the groups have the same group ID (GID) on all your machines.
That's because NFS (in the default configuration) relies on the UID+GID
and not on the real username (unlike eg. SMB shares).

Regards,
Anna

--- OpenXP 5.0.46
* Origin: Imzadi Box Point (1337:1/108.1)

So, enter 10.0.0.0/24 in OMV for your NFS share :)

Thanks so much, I did get this earlier and it works perfectly..

Another hint on NFS: It can be a bit tricky regarding the user/group access rights -- make sure your user(s) have the same user ID (UID) and the groups have the same group ID (GID) on all your machines.
That's because NFS (in the default configuration) relies on the UID+GID and not on the real username (unlike eg. SMB shares).

OK. This will be my next issue, I'm sure... I'm having a problem prior to getting to that point, tho:

On my BBS Raspberry Pi box, I added the NFS info to /etc/fstab and mounted the NFS perfectly... now when I reboot, the NFS automatically mounts. [This user is named differently so I'll have to add a user on OMV for it.] So anyway, the BBS box mounts the NFS no problem.

However... on a Manjaro install on a laptop, I can manually mount the NFS with sudo mount 10.0.0.16:/export/Backup8TB... but when I add the NFS info to /etc/fstab, when I try to mount /var/Backup8TB I get:

mount.nfs failed to prepare mount operation not permitted.

And I can only mount the NFS manually.. I want it to just mount at boot, like normal. Any thoughts??? I read somewhere that you had to rollback nfs-utils to an earlier release but... that didn't sound right.

This IS the reason I like to tinker with Raspberry Pi's - the let ou learn LOADS about linux, networks and more with minimal risk at all... love it; learning NAS software slowly.
:P



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A47 2020/11/23 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (1337:3/129)

Am 24.12.20 schrieb paulie420@1337:3/129 in TQW_LINUX:

Hallo paulie420,

However... on a Manjaro install on a laptop, I can manually mount the NFS with sudo mount 10.0.0.16:/export/Backup8TB... but when I add the NFS info to /etc/fstab, when I try to mount /var/Backup8TB I get:

mount.nfs failed to prepare mount operation not permitted.

Have you looked at the output of "dmesg"? Maybe here you can get more information on this problem.
Does the directory, where you want to mount the NFS share to, exist?
Could you post the fstab line?

And I can only mount the NFS manually.. I want it to just mount at boot, like normal. Any thoughts??? I read somewhere that you had to rollback nfs-utils to an earlier release but... that didn't sound right.

I'm only using Debian/Devuan-based systems, so I don't know much about Manjaro. But in Devuan/Ubuntu/... I usually forget installing the package nfs-common - but without it, mounting NFS does not work manually as well
as via fstab...

This IS the reason I like to tinker with Raspberry Pi's - the let ou learn LOADS about linux, networks and more with minimal risk at all... love it; learning NAS software slowly. :P

Have fun with it!

Have some nice holidays!

Regards,
Anna

--- OpenXP 5.0.46
* Origin: Imzadi Box Point (1337:1/108.1)