cannot ping "Internet" from DMZ on VirtualBox after changing the WAN from Bridged to Host-Only adapter
I hope all is OK with you, and you are healthy, and safe !
In VirtualBox I created a pfSense- firewall with LAN, and DMZ, both using Host-Only- adapters (so to be able to remote (SSH) from my Host- PC into LAN, and DMZ easily). My WAN has Bridged- adapter and accepting its IP- address from my home- network's DHCP. The VirtuaBox' DHCPs on LAN, and DMZ are stopped, and are configured on the Firewall so any dynamically configured client- pc to take an ip- address automatically. I have also a small web- server (Apache) with a simple test- page into the DMZ. After adding PAT:8888, and Rules for ICMP, :53, :80, and :443 into the Firewall, I am able to access from my Host by http://WAN:8888 the web page into the DMZ' web- server, and to access, and ping Internet- web- pages from the DMZ.
I needed to isolate more my WAN so I have changed the VirtualBox' WAN interface from Bridged to Host-Only adapter too, but for it I left the DHCP- server of the VirtualBox active (it doesn't provide a Default Gateway, and DNS). I have changed all other Firewall' settings accordingly. I started a MS Win 10 Virtual PC with the same Host-Only interface as the WAN, and I am still able to access from it the web- page into the DMZ by http://WAN:8888 (with the new, auto- assigned WAN- address). I am able to ping from the DMZ the WAN IP, but I am not able to ping from the DMZ the IP of Win 10 PC (its firewall is stopped).
Could you give some hand, what might be the issue here, please?
Thanks, and Best,
Did you create a firewall rule to permit packets to pass from DMZ to LAN ?
@bgroper Thank you for you reply,
I want this not to be allowed at this time.
The lab is for pen- testing, and for now the only available point to access from "outside" should be from Win 10 computer to the DMZ:80.