Quantcast
Channel: Intel Communities: Message List - Wired Ethernet
Viewing all articles
Browse latest Browse all 9952

Re: Intel i218-v promiscuous mode failure

$
0
0

Hello wb,

 

yes, "physically" it's a 'asRock h97m pro4' with 'intel i218-v' onboard. In a simple '/24' subnet ( let's say 10.0.0/24 ). But no, I didn't try to capture network traffic.

 

I had to replace an old installation. Hosted inside the new installation, I transferred the old setup into a virtual machine - to keep old settings and missed data accessible to the user. Static address 10.0.0.10, on an emulated nic with network bridge to physical device. So it should be able to access network shares on the new system, 10.0.0.1 ( static ). Gateway / router 10.0.0.254, other nodes, one 10.0.0.2 ( dhcp, but static lease ).

 

From '.2' I can ping both nodes accessible via the 'i218-v', '.1' with mac-address of device ( according to arp table ), and '.10' with mac-address defined inside VirtualBox. Also, I'm able to ping '.2' from new host and from old guest installation. But '.1' does not see '.10' and '.10' does not see '.1' - so no access to network shares.

However, arp-packets seem to find their way. On both host and guest there is an entry of the other node.

 

And switching 'vlan and priority' off or setting

lm\system\*controlSet*\control\class\{4d36 e972-e325-11ce-bfc1-0800 2be1 0318}\007\MonitorMode = x 0000 0001

( with ...\007\ComponentId = 'pci\ven_8086&dev_15a1' ) didn't help.

 

cu -  Stefan


Viewing all articles
Browse latest Browse all 9952

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>