Recent changes to Project Network Bridging Utility

DHCP broken over MAC bridge miniport adapter in Win7

2015-04-10T19:08:11.377000Z

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.

DHCP broken over MAC bridge miniport adapter in Win7

2015-03-25T18:53:22.219000Z

I'm bridging Ethernet segment with virtual WiFi AP and everything works great except for DHCP.
I have DHCP server on the Ethernet side but all devices on WiFi side get the same IP.

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.
Looks like Win7 MAC bridge miniport specifically modifies DHCP packets this way braking DHCP entirely.
Has someone noticed this as well? Perhaps there is a way to fix that or a replacement bridging is driver available?

At this point run standalone DHCP server on the Win7 box so DHCP traffic does not pass the bridge at all avoiding the issue.

#1 Windows 8.1 Support

2015-02-27T13:45:35.500000Z

It seems that Windows 8 uses the Microsoft MAC Bridge service that is not present on earlier Windows versions. This service is installed via \Windows\INF\netbrdg.inf and seems to be responsible for managing the bridge. Unfortunately, there is no documentation about this service.

#1 Windows 8.1 Support

2015-01-09T16:17:14.281000Z

Hello,
unfortunately there are really major changes in bridge miniport driver in Windows 8.1. Currently I've not tenough spare time for this purpose. There is also no documentation available from Microsoft, it would require time to reverse engeneer this mechanisms. Any help is appreciated by the way.

Windows 8.1 Support

2015-01-09T08:54:32.122000Z

Will Network Bridging Utilty supports Windows 8 / 8.1 any time soon?
In Windows 7 the Network Bridging Utility is working like a charm and support for Windows 8.1 will be greatly appriciated. Is this easy to realize or has Microsoft changed the Api in such a way that it's hard or impossible to implement this?

2015-01-02T19:43:15.762000Z

View Changes

Bug fix

2015-01-02T19:41:07.424000Z

Bug fix
View Changes

Home modified by Benjamin Kalytta

2015-01-02T19:39:16.131000Z

--- v4
+++ v5
@@ -25,4 +25,12 @@

 Removes all adapters from bridge and uninstalls the bridge adapter. The bridge service will not be uninstalled. Detaching includes unbinding from bridge service and binding to all installed bindable network protocols, clients and services.

+New in Version 1.0.1.0
+--
+Possibillity introduced to support multiple network adapters with the same hardware id. /attach can have a second argument. This argument either specifies the network adapter physical address (MAC address) or the interface alias name. It is not necessary to specify full name/address, specifying only first part is allowed like in:
+
+    bridgeutil.exe /attach "PCI\VEN_8086&DEV_15A1" D0:50:99
+
+This will attaches all Intel network adapters with the specified hardware id and starting with MAC address D0:50:99.
+
 **Note:** Subversion has read/write access for everyone. So please share your changes and commit it.

2015-01-02T19:26:47.804000Z

View Changes

Bug fixes, added support for multiple devices with the same hardware id.

2015-01-02T19:24:04.647000Z

Bug fixes, added support for multiple devices with the same hardware id.
View Changes