Thanks for responding. It's true that I do have VMWare running on most of
my Honeyd machines, so when I get back home I'm going to test the theory. I
do know that I have disabled and uninstalled the VMWare drivers on my
current travel machines and it had no impact...but maybe there's driver
reminants that don't remove automatically. And when I run both Winpcap and
Honeyd -W, they report the correct network drivers.
I'm on the road, but heading home today. I'm going to test these three
theories:
1. It's a new Wincap error, so I'll try it with old version.
2. It's a VMWare problem, I'll try it on a machine that never had VMWare.
3. Try running it on Win9x vs. W2K or above.
----- Original Message -----
From: "Ray" <raymond_at_silenttrace.com>
To: "Roger A. Grimes" <roger_at_banneretcs.com>
Sent: Sunday, February 29, 2004 8:06 AM
Subject: Re: Error running Honeyd-WIN32
> Not sure if Mike agrees with me on this or not but I think its a Winpcap
> issue. I have noticed that at times Winpcap doesn't notice or find all
the
> available NICS on a win32 system. Thus if you are running vmware or more
> than one nic can be found it will select only one of them and thus honeyd
> might not see the right nic to monitor.
>
> Sorry but it is quite early for me here and I may have my own wording
> backwards and that winpcap sees them all but only passes one ... Not sure
> but do know that you are correct and that it is the latest version of
> winpcap that started the mess.
>
> Hope it helps or at least gets you three thinking in a new direction.
>
> Raymond Brown
> www.silenttrace.com
> raymond_at_silenttrace.com
>
Received on Sun Feb 29 2004 - 16:35:08 PST
