On 09/06/2018 03:06 PM, Patrick O'Callaghan wrote:
On Thu, 2018-09-06 at 10:54 -0700, Rick Stevens wrote:
On 09/06/2018 10:22 AM, Tom Horsley wrote:
On Thu, 06 Sep 2018 17:17:21 +0100
Patrick O'Callaghan wrote:
A gentle hint would be welcome.
Unless you are using an honest to gosh bridge, the network
on the VMs is not accessible to the host (at least that's
what I've read). Using Mactavish networking (or whatever
the heck it is called) don't work for host access.
No, the 192.168.122.0/24 should be available from the host machine.
You DO have to hit the VM's 192.168.122.* address from the host.
If you want the VM to be available from the outside world, then
yeah, you need a full-up bridge and not a NAT.
When in doubt, simplify. I set up a basic web server by doing:
$ python -m SimpleHTTPServer
(which listens on 0.0.0.0:8000), opened the port in the firewall and
tried to browse from the host. Same result. So it's not a bug in
qbittorrent-nox.
That you can access the vm with ssh says the vm is already accessible
via the existing networking.
There's always tcpdump. On the host it would show whether traffic is
going both ways. On the guest it would show whether traffic is making
through the network and firewall.
:m
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
