I am having problems making VMWare work with my Lavasoft Personal Firewall 3.0. My VMware machine does not receive an IP address and can not access the internet.

I found the information below on a forum, but can’t figure out where to set “Packet Type” to “Transit”. Previously when I had Lavasoft Firewall version 2, I was able to find this selection in the rules, but it 3.0 I can’t.

http://www.lavasoftsupport.com/index.php?showtopic=2746

"I found the same problem, but I think I've figured it out. I tried to add new rule with this settings:

Where the direction is Outbound (then you can select packet type) and the packet type is (here you select) Transit
Where the specified local host is (your VPN network settings).
And Allow it."

Any help would be appreciated.

Thanks.

I was able to get the VMWare machine to get an IP address assigned by adding a “Low-Level” System-Wide Rule…

Where the protocol is UDP
and the direction is Outbound
Allow

But my VMWare machine still can not access the internet.

Still need help!!!

Hello tschurr
sorry, but it isn't the right forum here.
I just contacted LS and asked to help you, so pls be patient.
Sincere Regards
Raziel

LPFW blocks transit packets, which could prevent virtual machines from accessing the network. To allow virtual machines to access the network, create the LPFW default rules for vmware.exe and then do the following.

First, check whether your virtual machine connects to your computer via bridged mode or NAT mode. To do this:

1. Open the Virtual Machine Control Panel.
2. Click the Hardware tab.
3. Select Ethernet.
4. Under Connect to the following network one of the following options will be selected: NAT: Used to share the host's IP address or Bridged: Connected directly to the physical network.

Note:If you use NAT mode, you do not need to create additional LPFW rules. Your virtual machines should now be able to access the network.

If you use Bridged mode, create the following global rule to allow traffic from the virtual machine:

For LPFW 2.0:

1. Click Options on the toolbar, select System.
2. Under Global rules and rawsocket access select Rules.
3. Click Add to create the following new global rule:

Where the local host is (specify your virtual machine IP address or the subnet to which it belongs, for example, 192.168.5.0)
Allow it

For LPFW 3.0:

1. Click Settings > Network Rules > System-Wide Rules > Low-Level Rules.
2. Click Add and create the following rule:

Where the protocol is IP
and IP protocol type is TCP, UDP
and local address is (specify your virtual machine IP address or the subnet to which it belongs, for example, 192.168.5.0)
Allow
Click OK to save the changes.

If your virtual machine gets its dynamic IP address via DHCP, it is necessary to create additional low-level rules for LPFW 3.0:

1. Click Settings > Network Rules > System-Wide Rules > Low-Level Rules.
2. Click Add and create the following rule:

Where the protocol is UDP
and remote port is 67, 68, 546, 547
and local port is 67, 68, 546, 547
Allow
Click OK to save the changes.