https://sourceforge.net/p/networkbridgingutility/discussion/2015-04-10T19:08:11.377000ZRecent posts to Discussion2015-04-10T19:08:11.377000Z2015-04-10T19:08:11.377000ZBenjamin Kalyttahttps://sourceforge.net/u/bkausbk/https://sourceforge.net5a77d9ad219fad0e93858f4f964a3a9a436d56b0

<div class="markdown_content"><p>In order to be able to use DHCP you have to run a dedicated DHCP server. WiFI AP has it's own DHCP (192.168.173.1...254), but as soon as it get bridged this DHCP server is deactivated, so only link local addresses are available.</p></div>

2015-03-25T18:53:22.219000Z2015-03-25T18:53:22.219000Zlm1https://sourceforge.net/u/lmielick/https://sourceforge.net2c351c65c64949eedd5e80a2d6952ed1ae1095e8

<div class="markdown_content"><p>I'm bridging Ethernet segment with virtual WiFi AP and everything works great except for DHCP.<br /> I have DHCP server on the Ethernet side but all devices on WiFi side get the same IP.</p> <p>I have found that somehow not only the MAC address in the Ethernet header is modified by the bridge but also the requester MAC inside DHCP payload gets modified as well causing a bogus response.<br /> Looks like Win7 MAC bridge miniport specifically modifies DHCP packets this way braking DHCP entirely.<br /> Has someone noticed this as well? Perhaps there is a way to fix that or a replacement bridging is driver available?</p> <p>At this point run standalone DHCP server on the Win7 box so DHCP traffic does not pass the bridge at all avoiding the issue.</p></div>