I think you misunderstood. I used simple IP addressess and it worked.
10.0.0.1
10.0.0.2
10.0.0.3
etc…
I think you misunderstood. I used simple IP addressess and it worked.
10.0.0.1
10.0.0.2
10.0.0.3
etc…
I can now ping each machine and the NAS.
From here I’m hoping to figure out how to access the files.
Is samba the best option?
You did already create a thread for that. I did answer there: Connect vs mount - terminology question - #2 by jlehtone
The WAN IP address to your Synology NAS is assigned to US Army, Fort Huachuca, Arizona. Why are you not asking for help from their IT Staff?
It looks like the Synology NAS was probably setup by their staff as a gateway/DHCP/file server using Synology’s operating system, “DSM”, is a GNU/Linux distro. Synology Inc.
NetRange: 155.155.0.0 - 155.155.255.255
CIDR: 155.155.0.0/16
NetName: USAREUR2
NetHandle: NET-155-155-0-0-1
Parent: NET155 (NET-155-0-0-0-0)
NetType: Direct Allocation
OriginAS:
Organization: Headquarters, USAISC (HEADQU-3)
RegDate: 1991-12-16
Updated: 2021-12-14
Ref: https://rdap.arin.net/registry/ip/155.155.0.0
OrgName: Headquarters, USAISC
OrgId: HEADQU-3
Address: NETC-ANC CONUS TNOSC
City: Fort Huachuca
StateProv: AZ
PostalCode: 85613
Country: US
RegDate: 1990-03-26
Updated: 2011-08-17
When pinging, preceed the command with sudo
sudo ping IPAddress.
I would also rather setup the router’s DHCP server to reserve the address of the devices you want to connect to, based on their MAC address, rather than setting up every PC manually. You then have everything at a central location & can’t make the mistake of using the same IP twice.
Completely unnecessary. The normal use of ping
does not require special privileges.
On the use of DHCP I do completely agree. It has not been made clear whether there are any routers on OP setup.
Sorry, my bad. I usually use Debian & there a ping does need special privilege. Older versions didn’t but current versions do.
I use Debian and never need sudo for ping. By default it should work, unless someone has configured sudoers to block ping for normal users (which sounds like your situation is due to yours or someone else modification). But that is definitely not the default behaviour.
Never seen a ping work without privileges on RedHat, Fedora or Centos.
Here ya go, just for you:
[rhel9@rhel9 ~]$ id
uid=1001(rhel9) gid=1001(rhel9) groups=1001(rhel9) context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
[rhel9@rhel9 ~]$ cat /etc/redhat-release
Red Hat Enterprise Linux release 9.4 (Plow)
[rhel9@rhel9 ~]$ ping -c1 google.com
PING google.com (142.250.203.206) 56(84) bytes of data.
64 bytes from waw02s22-in-f14.1e100.net (142.250.203.206): icmp_seq=1 ttl=119 time=18.8 ms
--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 18.793/18.793/18.793/0.000 ms
I can even repeat this on Fedora, CentOS, Rocky using standard user accounts lol
Here we go. It is not so general you think.
[Tower Cen6]/home/antoine $ ping -c1 google.com
PING google.com (142.250.201.174) 56(84) bytes of data.
64 bytes from par21s23-in-f14.1e100.net (142.250.201.174): icmp_seq=1 ttl=117 time=4.52 ms
— google.com ping statistics —
1 packets transmitted, 1 received, 0% packet loss, time 9ms
rtt min/avg/max/mdev = 4.527/4.527/4.527/0.000 ms[Tower Centos8]/home/antoine $ ping -c1 google.com
ping: socket: Opération non permise
[Tower Centos8]/home/antoine $[Tower Rocky9]/home/antoine $ ping -c1 google.com
PING google.com(par21s23-in-x0e.1e100.net (2a00:1450:4007:81a::200e)) 56 octets de données
64 octets de par21s23-in-x0e.1e100.net (2a00:1450:4007:81a::200e) : icmp_seq=1 ttl=118 temps=8.05 ms
— statistiques ping google.com —
1 paquets transmis, 1 reçus, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 8.049/8.049/8.049/0.000 ms[Tower F25]/home/antoine $ uname -a
Linux becane2.becane.com 4.13.16-100.fc25.i686+PAE #1 SMP Mon Nov 27 20:26:05 UTC 2017 i686 i686 i386 GNU/Linux
[Tower F25]/home/antoine $ ping -c1 google.com
ping: socket: Operation not permitted[Tower F27]/home/antoine $ uname -a
Linux becane2.becane.com 4.18.19-100.fc27.x86_64 #1 SMP Wed Nov 14 22:04:34 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
[Tower F27]/home/antoine $ ping -c1 google.com
ping: socket: Operation not permitted[Tower F29]/home/antoine $ uname -a
Linux becane2.becane.com 5.3.11-100.fc29.x86_64 #1 SMP Tue Nov 12 20:41:25 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[Tower F29]/home/antoine $ ping google.com
ping: socket: Opération non permise[Tower F34]/home/antoine $ uname -a
Linux becane2.becane.com 5.17.12-100.fc34.x86_64 #1 SMP PREEMPT Mon May 30 17:47:02 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
[Tower F34]/home/antoine $ ping -c1 google.com
PING google.com(par21s03-in-x0e.1e100.net (2a00:1450:4007:810::200e)) 56 octets de données
64 octets de par21s03-in-x0e.1e100.net (2a00:1450:4007:810::200e) : icmp_seq=1 ttl=119 temps=5.47 ms
— statistiques ping google.com —
1 paquets transmis, 1 reçus, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 5.465/5.465/5.465/0.000 ms[Tower F38]/home/antoine $ uname -a
Linux becane2.becane.com 6.8.9-100.fc38.x86_64 #1 SMP PREEMPT_DYNAMIC Thu May 2 18:50:49 UTC 2024 x86_64 GNU/Linux
[Tower F38]/home/antoine $ ping -c1 google.com
PING google.com (172.217.20.206) 56(84) octets de données.
64 octets de waw02s08-in-f14.1e100.net (172.217.20.206) : icmp_seq=1 ttl=117 temps=3.76 ms
— statistiques ping google.com —
1 paquets transmis, 1 reçus, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 3.756/3.756/3.756/0.000 ms
[Tower F38]/home/antoine $
That would suggest, most likely a security profile was applied during installation that is blocking it or something else has been done to restrict a normal user from using it.
A default installation with no special config or security profiles allows ping to work as a normal user without restrictions. In your instance, something additional has been done to these machines that restricts it.