On 8/16/20 11:32 PM, Ed Greshko wrote:
On 2020-08-17 11:30, Robert Moskowitz wrote:
On 8/16/20 11:25 PM, Ed Greshko wrote:
On 2020-08-17 11:18, Robert Moskowitz wrote:
On 8/16/20 10:50 PM, Sam Varshavchik wrote:
Robert Moskowitz writes:
I am trying to SSH from my virtual image to the host system and
get connection refused.
I have tried connecting to the systems' IP addr and the gateway
IP addr for the virtual host. Still connection refused.
I can SSH to my host from another with no trouble.
What am I missing?
1) Ping your host's IP address from the VM.
Pinging works fine.
2) Assuming it's pingable, look into what firewalld says, about
the ssh port, and what IP addresses it's accessible from.
# firewall-cmd --list-all
public (active)
target: default
icmp-block-inversion: no
interfaces: wlp1s0
sources:
services: dhcpv6-client ipp ipp-client mdns
ports: 745/tcp
protocols:
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:
SSH is on port 745 (well not 745, but off 22). I did the selinux
command to allow ssh on this port and I can access from another
system no trouble.
What is the output of "firewall-cmd --get-active-zones"
# firewall-cmd --get-active-zones
libvirt
interfaces: virbr0
public
interfaces: wlp1s0
And virbr0 is the one used for the QEMU.
So, if you do "firewall-cmd --info-zone=libvirt" do you have port 745
enabled?
No I don't
# firewall-cmd --info-zone=libvirt
libvirt (active)
target: ACCEPT
icmp-block-inversion: no
interfaces: virbr0
sources:
services: dhcp dhcpv6 dns ssh tftp
ports:
protocols: icmp ipv6-icmp
masquerade: no
forward-ports:
source-ports:
icmp-blocks:
rich rules:
rule priority="32767" reject
_______________________________________________
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
