[Winpcap-users] Problems with running WinPCap on a virtual PC
j.munk at maccor.com
Sun Nov 6 14:00:48 PST 2011
Just a follow up.
I have got hold of a WinXP, set it up per your advice in Oracle
VirtualBox and installed my "promiscuous" application. It works
Once again, thank you very much for your help.
On 11/4/2011 10:07 AM, Jens Munk wrote:
> Thanks Mark,
> Well, the Microsoft Virtual PC is not going to work for me, then. I
> have downloaded the Oracle VirtualBox and this seems the way to go. I
> haven't tried it yet, since I need to acquire a WinXP install (The one
> I have came in the package with the Virtual PC).
> This is just a temporary solution. My problem is that part of my main
> project is still in VB6, and now I am getting a new PC with Win7 64
> bit, which cannot run the VB6 development environment. So until I get
> the rest of the VB6 code migrated to a modern language, I will have to
> keep it alive in a virtual "ancient" computer.
> Thanks again,
> On 11/4/2011 1:50 AM, Mark Pizzolato - WinPCap-Users wrote:
>> Hi Jens,
>> > From what you describe below your VM running under Virtual PC is
>> running XP. That VM has 2 Network interfaces configured on it. One
>> using NAT and the other "Bridged" to the LAN the remote
>> micro-controller device.
>> What you are seeing is a 'feature' of the Virtual PC environment's
>> Bridging/Switch Emulation. It does NOT allow arbitrary MAC addresses
>> to be passed back to the Virtual Device. The only MAC address that
>> will pass inward is the MAC address of the virtual NIC. You can
>> determine what this MAC address is by looking at the output of an
>> "IPCONFIG/ALL". Under the interface in question the MAC address will
>> be listed as the 'Physical Address'.
>> If you have your application use the physical MAC address packets
>> should pass.
>> Alternatively, you could setup a different VM environment using
>> Oracle VirtualBox. Install an XP environment on that VM and
>> configure the NIC (on the VirtualBox side). Set the NIC to Bridged
>> Adapter bridged with the appropriate LAN interface. Click on the
>> Advanced link in the settings tab and change the Promiscuous Mode
>> setting to "Allow All".
>> Good Luck.
>> - Mark Pizzolato
>> On Thursday, November 03, 2011 at 3:13 PM, Jens Munk wrote:
>>> Carlos, Mark,
>>> Sorry about that. The host PC is a Windows 7 64 bit professional,
>>> and the
>>> virtualization is Microsoft's Windows Virtual PC with WinXP. More
>>> it is the "Windows XP Mode with Virtual PC" package you can download
>>> directly from Microsoft:
>>> MAC addresses of virtual and physical network adapters: I was
>>> unaware that
>>> they would be different, and I would have to investigate this.
>>> However, should the virtualization machine take care of this?
>>> Thanks again. I really hope you can help me with this one,
>>> what virtualization engine are you using to run the VM ?
>>> On 11/2/2011 11:29 PM, Mark Pizzolato - WinPCap-Users wrote:
>>>> Hi Jens,
>>>> You fail to mention the what OS the host is running, AND what
>>> Virtualization software you are using. You also don't mention what
>>> address you are using as the source MAC address in your outgoing
>>> Specifically, is the source MAC address being used the same as the MAC
>>> address which the virtual network adapter is using?
>>>> Provide details and I'll try to explain what is happening and what
>>>> you may
>>> need to do.
>>>> - Mark
>>>> On Wednesday, November 02, 2011 at 3:19 PM. Jens Munk wrote:
>>>>> I am trying to run my application, that is using WinPCap to send and
>>>>> receive raw ethernet messages, on a virtual WinXP. The messages get
>>>>> send OK, but the incoming messages never get to the virtual WinXP and
>>>>> thus my application. This is confirmed by WireShark. Likewise running
>>>>> WireShark on the host shows that the incoming messages are present
>>>>> So how do I get this to work, i.e. get incoming raw messages all the
>>>>> way back to the virtual machine?
>>>>> Some info on my setup: The PC has two adapters: One for the company
>>>>> and internet and one for this purpose (I am communicating with the
>>>>> micro- controllers). The first adapter is set as "Shared networking
>>>>> (NAT)" and works fine on the internet. The other one and the one I
>>>>> want to use for this is set as its name.
>>>> Winpcap-users mailing list
>>>> Winpcap-users at winpcap.org
>> Winpcap-users mailing list
>> Winpcap-users at winpcap.org
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
-------------- next part --------------
An HTML attachment was scrubbed...
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 307 bytes
Desc: not available
More information about the Winpcap-users