Re: Network entanglement

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 11/05/2021 12:52, Robert McBroom via users wrote:
Installed Arch Linux on my Goflex Home NAS. I see it on the router from my ISP. It is connected through an access point to have a sufficient number of ethernet ports. I can't ping it using the ipv4 address I see on the router. There are two ipv6 addresses shown. One declares a lifetime of 3600s and the other says forever. ping and ssh work using the ipv6 address with a declared lifetime but not the "forever"

Could you elaborate on what "Installed Arch Linux on my Goflex Home NAS" means?
Does it mean you replaced the normal O/S of the NAS or does the NAS support running VM's?


Using a system that is connected to the wireless on the ISP router can ping the Arch system with the ipv4 address.

You mean "can not" ping, yes?

What is the supposed IPv4 address of the Arch Linux, 192.168.1.112? And what has the IP address of
192.168.1.185?


ping 192.168.1.112
PING 192.168.1.112 (192.168.1.112) 56(84) bytes of data.
From 192.168.1.185 icmp_seq=1 Destination Host Unreachable
From 192.168.1.185 icmp_seq=2 Destination Host Unreachable
From 192.168.1.185 icmp_seq=3 Destination Host Unreachable
From 192.168.1.185 icmp_seq=4 Destination Host Unreachable
From 192.168.1.185 icmp_seq=5 Destination Host Unreachable
From 192.168.1.185 icmp_seq=6 Destination Host Unreachable
^

PING 2600:1702:4860:9dd0:210:75ff:fe28:5e30(2600:1702:4860:9dd0:210:75ff:fe28:5e30) 56 data bytes
64 bytes from 2600:1702:4860:9dd0:210:75ff:fe28:5e30: icmp_seq=1 ttl=64 time=0.301 ms
64 bytes from 2600:1702:4860:9dd0:210:75ff:fe28:5e30: icmp_seq=2 ttl=64 time=0.292 ms
64 bytes from 2600:1702:4860:9dd0:210:75ff:fe28:5e30: icmp_seq=3 ttl=64 time=0.298 ms
64 bytes from 2600:1702:4860:9dd0:210:75ff:fe28:5e30: icmp_seq=4 ttl=64 time=0.288 ms

Knew just enough of ipv4 to almost get around but this is beating me.




--
Remind me to ignore comments which aren't germane to the thread.

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux