All;
I have 2 new laptops, with new installs of Fedora 33
On both laptops I have run:
# systemctl start sshd
# systemctl stop firewalld
They are both on the same wifi network
a ping from either laptop to the IP of the other one produces "Destination Host Unreachable"
Is there something else in Fedora 33 I need to do?
Thanks in advance
S Bob writes:
All;
I have 2 new laptops, with new installs of Fedora 33
On both laptops I have run:
# systemctl start sshd
# systemctl stop firewalld
They are both on the same wifi network
a ping from either laptop to the IP of the other one produces "Destination Host Unreachable"
Is there something else in Fedora 33 I need to do?
Some Wifi access points block clients from connecting to each other by default. Poke around your router for some setting to that effect.
On 2/15/21 4:09 PM, S Bob wrote:
I have 2 new laptops, with new installs of Fedora 33
On both laptops I have run:
# systemctl start sshd
# systemctl stop firewalld
They are both on the same wifi network
a ping from either laptop to the IP of the other one produces "Destination Host Unreachable"
That indicates that there's some sort of networking issue unrelated to ssh. Check your routes and make sure that your wifi router doesn't block client to client communication.
On 16/02/2021 08:09, S Bob wrote:
All;
I have 2 new laptops, with new installs of Fedora 33
On both laptops I have run:
# systemctl start sshd
# systemctl stop firewalld
They are both on the same wifi network
a ping from either laptop to the IP of the other one produces "Destination Host Unreachable"
Is there something else in Fedora 33 I need to do?
Sounds more like an issue external to the laptops. But you don't give much info on the network side. What kind of WiFi router or access point are the systems connected to? Does "traceroute" return the same message?
I have a comcast router and an untangle firewall setup, all laptops are behind the firewall. I also have 2 laptops running Fedora 32, I can ssh to/from the Fedora 32 laptops without any issues
So, here's my attempts to ssh:
F32 = the old Fedora 32 laptop (IP = 10.16.0.101)
F33a is one of the new Fedora 33 laptops (IP = 10.16.0.195)
F33b is one of the new Fedora 33 laptops (IP = 10.16.0.158)
From F32, ssh to F33a (success)
From F33a to F32 (success)
From F32 to F33b (success)
From F33b to F32 (success)
From F33a to F33b (fail)
From F33b to F33a (fail)
I'm stumped, I've been running Fedora laptops in this network for years and never had this issue.
Thoughts?
On 2/15/21 5:24 PM, Ed Greshko wrote:
On 16/02/2021 08:09, S Bob wrote:
All;
I have 2 new laptops, with new installs of Fedora 33
On both laptops I have run:
# systemctl start sshd
# systemctl stop firewalld
They are both on the same wifi network
a ping from either laptop to the IP of the other one produces "Destination Host Unreachable"
Is there something else in Fedora 33 I need to do?
Sounds more like an issue external to the laptops. But you don't give much info on the network side. What kind of WiFi router or access point are the systems connected to? Does "traceroute" return the same message?
It was SELINUX
On 2/15/21 6:05 PM, S Bob wrote:
I have a comcast router and an untangle firewall setup, all laptops are behind the firewall. I also have 2 laptops running Fedora 32, I can ssh to/from the Fedora 32 laptops without any issues
So, here's my attempts to ssh:
F32 = the old Fedora 32 laptop (IP = 10.16.0.101)
F33a is one of the new Fedora 33 laptops (IP = 10.16.0.195)
F33b is one of the new Fedora 33 laptops (IP = 10.16.0.158)
From F32, ssh to F33a (success)
From F33a to F32 (success)
From F32 to F33b (success)
From F33b to F32 (success)
From F33a to F33b (fail)
From F33b to F33a (fail)
I'm stumped, I've been running Fedora laptops in this network for years and never had this issue.
Thoughts?
On 2/15/21 5:24 PM, Ed Greshko wrote:
On 16/02/2021 08:09, S Bob wrote:
All;
I have 2 new laptops, with new installs of Fedora 33
On both laptops I have run:
# systemctl start sshd
# systemctl stop firewalld
They are both on the same wifi network
a ping from either laptop to the IP of the other one produces "Destination Host Unreachable"
Is there something else in Fedora 33 I need to do?
Sounds more like an issue external to the laptops. But you don't give much info on the network side. What kind of WiFi router or access point are the systems connected to? Does "traceroute" return the same message?
I disabled SELINUX on the new laptops (dont need it here) and everything works
On 2/15/21 6:22 PM, Samuel Sieb wrote:
On 2/15/21 5:16 PM, S Bob wrote:
It was SELINUX
Can you provide more details? _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Mon, 15 Feb 2021 18:58:29 -0700 S Bob wrote:
I disabled SELINUX on the new laptops (dont need it here) and everything works
I've never had selinux screw up ssh, it usually installs all the right file labels to allow it to work. (Now "rsh" is a different matter).
Of course when I install a system by copying the root and boot from another system, I need to force everything to get relabeled if I want to enable selinux (but that usually screams long before I try ssh).
On Feb 15, 2021, at 20:59, S Bob sbob@quadratum-braccas.com wrote:
I disabled SELINUX on the new laptops (dont need it here) and everything works
Are you running sshd on a port other than 22? What AVCs were generated when SELinux is in permissive mode?
SELinux should absolutely not block ssh from working in a standard config.
— Jonathan Billings
I was using the default port (22). I did a standard install and did not change anything in the ssh config
On 2/15/21 7:13 PM, Jonathan Billings wrote:
On Feb 15, 2021, at 20:59, S Bob sbob@quadratum-braccas.com wrote:
I disabled SELINUX on the new laptops (dont need it here) and everything works
Are you running sshd on a port other than 22? What AVCs were generated when SELinux is in permissive mode?
SELinux should absolutely not block ssh from working in a standard config.
— Jonathan Billings _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On 2/15/21 8:25 PM, S Bob wrote:
I was using the default port (22). I did a standard install and did not change anything in the ssh config
Then it's extremely unlikely that it was an selinux issue. As Gordon said, I don't know of any way to block a ping with selinux.
On 2/15/21 5:58 PM, S Bob wrote:
I disabled SELINUX on the new laptops (dont need it here) and everything works
I don't believe there's any mechanism by which SELinux can result in ping indicating "destination host unreachable."
Can you reproduce the problem by turning SELinux back on? If not, then the problem was something else.
On 2/15/21 7:21 PM, Gordon Messmer wrote:
On 2/15/21 5:58 PM, S Bob wrote:
I disabled SELINUX on the new laptops (dont need it here) and everything works
I don't believe there's any mechanism by which SELinux can result in ping indicating "destination host unreachable."
Can you reproduce the problem by turning SELinux back on? If not, then the problem was something else.
I'll check and report back
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Mon, Feb 15, 2021 at 06:05:42PM -0700, S Bob wrote:
F32 = the old Fedora 32 laptop (IP = 10.16.0.101) F33a is one of the new Fedora 33 laptops (IP = 10.16.0.195) F33b is one of the new Fedora 33 laptops (IP = 10.16.0.158)
Let's go down a layer -- what happens when you ping each of these from the other?