I typed: https://ifconfig.co
I got:
| IP address | 2600:1004:a121:a337:1af0:baa9:2538:de2c |
|---|---|
| IP address (decimal) | 50510988725160863549661529129533103660 |
Is there something else you add to the address line? I thought by typing that from the computer (in my case Fedora sever) you wanted info about it gives you that computer’s info.
Thanks,
Sheila
That’s an IPv6 address.
All the computers inside your firewall / router would appear to come from the same IP address. In your case that IP address is an IPv6 address. On the inside you appear to use IPv4 like 192.168.1.x/24.
That’s pretty normal these days. My ISP does not appear to use IPv6 just yet. At least not on my segment of the network.
Hi Sheila, 
Sorry, I´m (too) late for the discussion.
But I´m glad there are a lot of kind and knowledgeable people avialable here to help you.
I even think they can help you in a much better way than I can. 
Cheers from Rosika 
Yes, at least it has 2 LAN ports. Not cheap… about the price
of a lowend laptop.,
Interesting… Reckon I’d probably opt to pay a bit less and get something 2nd hand… Actually - I could probably use my Gigabyte Brix - all it does is run RHEL 8 as a sandpit for trying stuff out… dual core celeron with 16 GB of DD3 and I think I’ve got a 256 GB M2 and a 512 GB spinner in it… All I’d have to do is add a USB3 gigabit dongle onto it to have 2 NICs…
BUT - this is a BIG BUT - I really can’t be bothered either to setup a WiFi AP on it - having a separate firewall - when most of my home devices use WiFi straight to the router - it would be redundant - I’d rather just keep using TP-Link as an ethernet switch, WiFi AP, and modem/router…
I have a gigabit switch in my home office, that connects to a Powerline (ethernet over power) wall wart, to my kitchen and another Powerline wall wart, into the gigabit switch in my router… But I sometimes use WiFi for some devices in my home office - especially if I take one of my MacBooks or my Thinkpad to somewhere else in the house…
No - I don’t think that’s related to Address Reservation or “Static Lease” in DHCP. I suspect that’s just some sort of abstraction - so you can do sophisticated NAT stuff (e.g. allow port 22 incoming to go to an “object” instead of an IP address - maybe - I’m just guessing).
Most routers - I’ve had Netgear, Netcomm, and now TP-Link - the “Address Reservation” or “Static IP address” are in the LAN settings under DHCP or something - that’s where you’d set it.
I said one address higher than your router suggests.
As a RULE I NEVER use the .1 or the .254 - as either could be used for a gateway on that LAN - some goes for .255 - that’s reserved for broadcast.
So - you could reserve ANY of those addresses between “192.168.1.2 - 192.168.1.254” - THAT IS the router’s range for assigning DYNAMIC and STATIC DHCP leases to computers. This is why I’d suggest you CHANGE that range to a smaller number e.g. 192.168.1.100 - 192.168.1.199 - that way you can statically (i.e. on the computer) assign addresses outside of your router’s DHCP range - and - avoid conflicts…
Also - if I manually set e.g. my Pop!_OS desktop machine’s IP address - I STILL reserve that in my router’s DHCP “Address Reservation” ANYWAY. In actual fact - my desktop machine does have an IP address in the range my router’s DHCP server assigns - so I’ve set an “Address Reservation” for it - even though I don’t use DHCP on it. e.g. my desktop machine is assigned .162 (manually/static on the machine) - but I also reserve that .162 in the router (the range is x.x.x.100-199) - so NOTHING else could get that IP address and use it…
Just some points to clarify
Well this new router does not have anything for DHCP in the top level menus. Options under Network Settings:
However, under IPv4 Address Distribution, the preset configuration can be edited and shows the following:
So this is where I would change the range to a smaller number? (using your example, say .100 - .199)
Then I not only assign a static IP in the machine, but I also reserve that on the router and you actually use one (.162) that is within the router’s range of addresses.
Okay. I’ll see if I can get this done. Husband was out of town for a week and I have been swamped running everything myself.
Thanks,
Sheila
I need to try this experiment myself… a learning experience.
Thanks for the tutorial.
I dont need it to do NFS, because I have a local private net, but most people seem to go the way you intend and use the modem settings.
Neither does mine (TP-Link Archer VR2100) - I have to dig deeper, go into advanced mode, then LAN settings - and that’s where I see my DHCP settings - and - that’s where I can use “Address Reservation” (and that’s below the “Client List” which shows WiFi and ethernet connections).
If your router cannot do FIXED DHCP lease (dedicated lease, or address reservation) - then you might be better off restricting the range of IP addresses your router distributes (e.g. 192.168.1.100-199) - and then to avoid conflicts - on your host machine that you want to have a fixed IP address, set the IP address on that machine to something OUTSIDE of that range - to avoid potential clashes…
So - for example - your Fedora machine - give it IP address 192.168.1.90 (but still use the same netmask and gateway IP address [i.e. the LAN IP address of your Verizon device - I’m assuming 192.168.1.1]).
So, if I set a restricted range of IP addresses in the modem, then set a computer NIC to a fixed address outside that range, but in the same network, will it route properly? … important because that seems an obvious way to go?
Essentially - correct…
You should know all your details - e.g. what DNS servers to use, IP address of your router/gateway :
Here’s my Gnome NetworkManager applet front end to configure my ethernet (Wired\ Connection\ 1.nmconnection) :
Note : I’m using Google’s DNS servers… I can’t even remember what my ISP suggests… These are nearly exactly what I set in my DHCP scope in my router config :
But even though I set my IP address on this Pop!_OS desktop machine manually (on the machine) I also set a DHCP lease “Address Reservation” for it in the DHCP scope :
Yes, all the things needed to configure an NIC in the computer,
and do it by hand, instead of letting dhcp take over.
Lesson for me is… I dont have to let the modem control IP number allocation… I can override it… I just gave to stay within the
192.168.1.0 network or whatever it is.
The modem will receive packets from a fixed IP PC just as easily as from a dhcp PC, because the modem listens to the network , not individual PC’s.
Sorry, my education in this area has been neglected. Thanks… it helps me to write it out.
Right on brother. We are both using Pop!_OS and both using TP-Link. Hmmm.
I am pretty sure that when I used Netgear I could put in a reservation for something outside of the scope. That doesn’t make much sense.
If you limit the scope to 100-199 and then hard code an IP at 90 for your Pop!_OS machine there will never be anything that conflicts with it. If you try to make a reservation for 90 it won’t let you because that’s outside the scope.
I know because I tried to make a reservation when my TP-Link was new and it refused.
It does make sense that you can’t make that reservation because it’s outside the scope. I could just swear I did that on my Netgear. I must have included the lower IPs in the scope too and made the reservation I guess. It’s still in the closet. I could probably fire it up and check the config. 
Well that’s odd - my TP-Link Archer VR2100 DOES allow me to reserve addresses outside of the defined DHCP scope range 100-199
e.g. my DHCP “scope” is x.x.x.100-199… Inside that scope I reserve .162 - only 'cause I know my main machine gets that - it’s easy to remember (I was born in 62 and I could just use .62 I guess - but I’ve been using .162 for this machine for 3-4 years now, and before that on a different desktop machine that’s been superceded). But - I’ve also reserved .77, which is outside of the DHCP scope, I use that for my phone - when it connects to my WiFi - DHCP gives it that .77 address (and avahi/zeroconf doesn’t work well on Android - and I like to SSH to my phone running TermUX [e.g. to get photos off it using rsync over TCP 22])…
I can’t remember what .65 or .64 were for, .33 is my Pi3 that runs TVHeadend, I know what 113 and 146 are (my TP-Link cameras).
Although we solved this and I have now sucessfully gotten all machines and server setup with NFS (and I was able to use hostnames YAY), I now need to transfer all the home folder contents to that nfs share.
Question, does it affect anything or take any longer to rsync if symlinks to an ext HDD are used? In other words, should I just rsync from the ext HDD path where the /home folders reside to copy them to the nfs server?
So if the symlink for /Documents is:
/media/myviolinsings/Linux Home Data3/Linux Mint/Home/Documents
Can I just use mint-desktop/myviolinsings/home/documents?
Just trying to think out the command wording for such long location names…lol.
Thanks,
Sheila
I’m pretty sure you need to tell rsync to follow symlinks if they are in the path or to not follow them if that’s what you want.
If you use the real path to the data rather than the symlink that would avoid the issue.
$ rsync --help | grep -i sym
socketpairs, symlinks, symtimes, hardlinks, hardlink-specials,
hardlink-symlinks, IPv6, atimes, batchfiles, inplace, append, ACLs,
--links, -l copy symlinks as symlinks
--copy-links, -L transform symlink into referent file/dir
--copy-unsafe-links only "unsafe" symlinks are transformed
--safe-links ignore symlinks that point outside the tree
--munge-links munge symlinks to make them safe & unusable
--copy-dirlinks, -k transform symlink to dir into referent dir
--keep-dirlinks, -K treat symlinked dir on receiver as dir
--omit-link-times, -J omit symlinks from --times
That would be the long name. I just wasn’t sure if rsync automatically followed the symlink when you designate the link vs the actual path.
Thanks,
Sheila
It looks like if you do not specify, depending on type of symlink, it will either skip it or only copy the symlink as a symlink, which I do not want.
Thanks,
Sheila
Let me take a step back and be sure what you want.
You are shifting data to the server, so you can share the
data filesystem with NFS ? Right?
So, do you want to NFS to export the filezystem containig the
symlinks, or the filesystem containg the data they point to , or both?
Think carefully… the symlinks apply to the computer they are in. Will they do the right thing when/if you shift them to the server?
Otherwise, @pdecker has answered your query.
If you want rsync to follow links, you have to tell it. Follow links means turn them into the data they point to. It sounds like that is what you need… at the server copy there will be no links, just data.
@nevj yes, I am trying to copy the home folders from LM machine to the server, since the bulk of my data is generated from that computer. Minimal files will be shifted from other machines.
Since the LM data resides on an ext HDD with symlinks pointing to it there, I just wanted to be sure that if I use rsync to copy the files from there, that it did not just put symlinks on the server, but the actual data.
At this point, I am only copying to the nfs-server. I will decide whether or not to remove them from my LM machine later.
Of course, once on the nfs-server, they will be backed up 2 ways.
Thanks,
Sheila
Whenever I use symlinks in a command or a shell script - if it’s a symlink to a folder, I terminate the end of the name of the symlink with “/.”…
e.g. My $HOME/Documents is actually a symlink to my ResilioSync share $HOME/ResilioSync/bigshit/Document - so if I’m going to rsync that somewhere else :
rsync -av ~/Documents/. $DESTINATION/.
I’ve just gotten into the habit of padding “/.” onto the end of stuff…