- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
09-15-2021 11:28 AM
Hi guys, I have a beginner's question I'd like to ask.
I want to set up my own home lab on VMware workstation 16 and something doesn't add up.
First, my simple network topology is the following:
Background information: I saw somewhere that I should go to Virtual Network Editor and add a Vmnet with DHCP disabled with a 10.1.1.0 IP so it could be assigned to an additional interface for the PA VM and for the Windows 10 Network Driver.
So I created a VMnet3 with DHCP off and IP 10.1.1.0 and assigned it to the third Network Adapter (eth1/2) for PA VM and also for the Network Adapter of the Windows 10 machine.
All the above were completed, and still, I can't ping anything from my Windows 10 machine (not the interface, nor the internet). The Windows 10 machine is not visible on any traffic logs, and I'm pretty sure it's not reaching the network for some reason. I'm sure I'm missing something still, I just don't know what exactly.
YOUR HELP IS HIGHLY APPRECIATED.
01-28-2022 04:54 AM
Hi Samy,
It was a fairly silly mistake. You should just set up the default gateway of the server the same as the interface (10.1.1.250 in my case).
As mentioned before, it was a rookie mistake from my side.
09-15-2021 12:36 PM
If you want to save yourself a lot of time and know without a doubt the Palo config is good to go, use our XML-API based solution builder, IronSkillet.
Instructions on pulling the container to Docker are here.
Then you are able to import a skillet using the following link here (use the github repo).
After that, in two clicks you'll have rules and topologies built to best practice. This will further confirm that you may require more troubleshooting within VMWare.
01-27-2022 10:19 AM
Hello ,
I have the same issue .
Did you find any answer on this ?
01-28-2022 03:57 AM
Hi ,
I have solved this problem , i think you have configured the wrong subnetmask on the respective interface , I assumed you have configured /32 for the ip address but you need to change it to /24 if your network belong to /24
01-28-2022 04:54 AM
Hi Samy,
It was a fairly silly mistake. You should just set up the default gateway of the server the same as the interface (10.1.1.250 in my case).
As mentioned before, it was a rookie mistake from my side.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!