vmware vmxnet driver (vic) error

Is anybody successfully using the vmxnet network driver (vic)? With various VMWare Server 1.0+ versions and host operating systems I'm experiencing the following problem: vm_fault(0xd5fd9298, 0x0, 0, 3) -> e kernel: page fault trap, code=0 Stopped at _bus_dmamap_load_mbuf+0xf

Re: vmware vmxnet driver (vic) error

Here is the trace. You could download my whole vmware image to reproduce... Reyk Floeter wrote: > On Thu, May 03, 2007 at 08:01:53PM +0200, Bert Koelewijn wrote: >> Is anybody successfully using the vmxnet network driver (vic)? > > yes, i was using it with esx and the freewar

Re: vmware vmxnet driver (vic) error

9:ae" and this uuid.bios won't: uuid.bios = "56 4d 06 40 43 9c 36 70-df 0a cb d7 9f 61 22 b7" ethernet0.generatedAddress = "00:0c:29:61:22:b7" Could somebody try to reproduce? Thanks, Bert Reyk Floeter wrote: On Thu, May 03, 2007 at 08:01:53PM +0200, Bert Koelew

OpenBSD 4.0 vulnerable?

Hi, Are all security patches applied to MAIN, already applied to the OPENBSD_4_0 stable branche? If not, does this have any security consequences? Thanks, Bert

Re: OpenBSD 4.0 vulnerable?

Thanks Brad! ;=) Bert Koelewijn wrote: Hi, Are all security patches applied to MAIN, already applied to the OPENBSD_4_0 stable branche? If not, does this have any security consequences? Thanks, Bert

Possible bridge bug

Hello all, Could someone explain this behaviour? When an IP address is assigned to a bridge member interface, an arp broadcast request to this interface bypasses bridge filter rules. But, an arp unicast request is blocked as it should. Setup: 192.168.1.1(00:aa:bb:01:02:03) --pcn0-[bridge]-pc

Re: Possible bridge bug

Stuart Henderson wrote: Could someone explain this behaviour? When an IP address is assigned to a bridge member interface, an arp broadcast request to this interface bypasses bridge filter rules. But, an arp unicast request is blocked as it should. If you can, it might be helpful to confirm