On 7/11/23 19:15, Lists wrote:
I have a Fedora (35) workstation with some VMs running on a virtual
LAN and I want to open service(s) to the local Physical LAN. Goal is
to make an HTTP service running on 192.168.122.11:80 visible to
192.168.1.* as 192.168.1.62:80
The problem isn't your firewall configuration, instead it's that a VM
with a NIC configured in NAT mode has no network connection that would
allow traffic to flow from the 198.168.1.* network to the 192.168..122.*
network. When I need to allow a VM to expose services to an external
network like your LAN, I set it up with a bridged network
configuration. This configuration results in your VM being given its
own address on the 192.168.1.* network and any ports it exposes to be
visible to the other devices on that network. No port forwarding is
necessary. Firewall software running in the VM is used to control
access to these ports, the host's firewall is not a factor. This Fedora
Docs article provides more details and describes how to set this up:
https://docs.fedoraproject.org/en-US/fedora-server/administration/virtual-routing-bridge/
--
David King
dave at daveking dot com
_______________________________________________
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, report it: https://pagure.io/fedora-infrastructure/new_issue
