Windows 7 miniport network bridge clones MAC address, what is it, how to fix?
I have here an experimental Windows7 system which interconnects two ethernet segments with network bridging.
It works like charm, but... it substitutes the MAC addresses of the forwarded packets with its own. This is not a bridge function, looks much more like an arp proxying router.
More exactly:
segment1 <--> Win7 <--> segment2
If I send a packet from segment1 to segment2, it is perfectly forwarded, but the receiver on segment2 sees the MAC address of the Win7, and not the MAC of the original sender!
Why is it? Is there any workaround? Maybe an alternative software?
windows-7 networking router bridge
asked Jun 8 '16 at 3:17
peterhpeterh
1,41482138
|
show 1 more comment
I have here an experimental Windows7 system which interconnects two ethernet segments with network bridging.
It works like charm, but... it substitutes the MAC addresses of the forwarded packets with its own. This is not a bridge function, looks much more like an arp proxying router.
More exactly:
segment1 <--> Win7 <--> segment2
If I send a packet from segment1 to segment2, it is perfectly forwarded, but the receiver on segment2 sees the MAC address of the Win7, and not the MAC of the original sender!
Why is it? Is there any workaround? Maybe an alternative software?
windows-7 networking router bridge
asked Jun 8 '16 at 3:17
peterhpeterh
1,41482138
Are both segments wired Ethernet? This behavior would be pretty much required if bridging Wi-Fi without WDS.
– grawity
Jun 8 '16 at 4:49
No, what you say is NOT a switch, but a proxy arp. It is not "required behavior", it is not a switch. Wds hasn't anything to do with that, it is not about wireless headers, it is about that mac addresses are overwritten by the miniport "switch". Btw, bridging two ethernet segments does the same behavior.
– peterh
Jun 8 '16 at 5:03
Well, if it were Wi-Fi, then the bridge would have to overwrite MAC addresses because that is in fact required by the wireless headers. (Well, unless you're an AP.). If it's Ethernet-only, then no, that's not required.
– grawity
Jun 8 '16 at 5:04
@grawity Well, here is a simple description, what is a bridge: en.m.wikipedia.org/wiki/File:Network_Bridging.png . And: 1) a similar configuration works perfectly with Linux 2) bridging 2 ethernet segments with the windows miniport bridge behaves the same. MAC overwrite isn't needed in any cases, where did you get this?
– peterh
Jun 8 '16 at 5:14
@grawity And finally: a "bridge" which overwrites MAC is not a bridge. It is a router.
– peterh
Jun 8 '16 at 5:23
|
show 1 more comment
I have here an experimental Windows7 system which interconnects two ethernet segments with network bridging.
It works like charm, but... it substitutes the MAC addresses of the forwarded packets with its own. This is not a bridge function, looks much more like an arp proxying router.
More exactly:
segment1 <--> Win7 <--> segment2
If I send a packet from segment1 to segment2, it is perfectly forwarded, but the receiver on segment2 sees the MAC address of the Win7, and not the MAC of the original sender!
Why is it? Is there any workaround? Maybe an alternative software?
windows-7 networking router bridge
asked Jun 8 '16 at 3:17
peterhpeterh
1,41482138
I have here an experimental Windows7 system which interconnects two ethernet segments with network bridging.
It works like charm, but... it substitutes the MAC addresses of the forwarded packets with its own. This is not a bridge function, looks much more like an arp proxying router.
More exactly:
segment1 <--> Win7 <--> segment2
If I send a packet from segment1 to segment2, it is perfectly forwarded, but the receiver on segment2 sees the MAC address of the Win7, and not the MAC of the original sender!
Why is it? Is there any workaround? Maybe an alternative software?
windows-7 networking router bridge
windows-7 networking router bridge
asked Jun 8 '16 at 3:17
peterhpeterh
1,41482138
asked Jun 8 '16 at 3:17
peterhpeterh
1,41482138
edited Jun 8 '16 at 3:43
peterh
asked Jun 8 '16 at 3:17
peterhpeterh
1,41482138
asked Jun 8 '16 at 3:17
peterhpeterh
1,41482138
asked Jun 8 '16 at 3:17
peterhpeterh
1,41482138
1,41482138
Are both segments wired Ethernet? This behavior would be pretty much required if bridging Wi-Fi without WDS.
– grawity
Jun 8 '16 at 4:49
No, what you say is NOT a switch, but a proxy arp. It is not "required behavior", it is not a switch. Wds hasn't anything to do with that, it is not about wireless headers, it is about that mac addresses are overwritten by the miniport "switch". Btw, bridging two ethernet segments does the same behavior.
– peterh
Jun 8 '16 at 5:03
Well, if it were Wi-Fi, then the bridge would have to overwrite MAC addresses because that is in fact required by the wireless headers. (Well, unless you're an AP.). If it's Ethernet-only, then no, that's not required.
– grawity
Jun 8 '16 at 5:04
@grawity Well, here is a simple description, what is a bridge: en.m.wikipedia.org/wiki/File:Network_Bridging.png . And: 1) a similar configuration works perfectly with Linux 2) bridging 2 ethernet segments with the windows miniport bridge behaves the same. MAC overwrite isn't needed in any cases, where did you get this?
– peterh
Jun 8 '16 at 5:14
@grawity And finally: a "bridge" which overwrites MAC is not a bridge. It is a router.
– peterh
Jun 8 '16 at 5:23
|
show 1 more comment
Are both segments wired Ethernet? This behavior would be pretty much required if bridging Wi-Fi without WDS.
– grawity
Jun 8 '16 at 4:49
No, what you say is NOT a switch, but a proxy arp. It is not "required behavior", it is not a switch. Wds hasn't anything to do with that, it is not about wireless headers, it is about that mac addresses are overwritten by the miniport "switch". Btw, bridging two ethernet segments does the same behavior.
– peterh
Jun 8 '16 at 5:03
Well, if it were Wi-Fi, then the bridge would have to overwrite MAC addresses because that is in fact required by the wireless headers. (Well, unless you're an AP.). If it's Ethernet-only, then no, that's not required.
– grawity
Jun 8 '16 at 5:04
@grawity Well, here is a simple description, what is a bridge: en.m.wikipedia.org/wiki/File:Network_Bridging.png . And: 1) a similar configuration works perfectly with Linux 2) bridging 2 ethernet segments with the windows miniport bridge behaves the same. MAC overwrite isn't needed in any cases, where did you get this?
– peterh
Jun 8 '16 at 5:14
@grawity And finally: a "bridge" which overwrites MAC is not a bridge. It is a router.
– peterh
Jun 8 '16 at 5:23
Are both segments wired Ethernet? This behavior would be pretty much required if bridging Wi-Fi without WDS.
– grawity
Jun 8 '16 at 4:49
Are both segments wired Ethernet? This behavior would be pretty much required if bridging Wi-Fi without WDS.
– grawity
Jun 8 '16 at 4:49
No, what you say is NOT a switch, but a proxy arp. It is not "required behavior", it is not a switch. Wds hasn't anything to do with that, it is not about wireless headers, it is about that mac addresses are overwritten by the miniport "switch". Btw, bridging two ethernet segments does the same behavior.
– peterh
Jun 8 '16 at 5:03
No, what you say is NOT a switch, but a proxy arp. It is not "required behavior", it is not a switch. Wds hasn't anything to do with that, it is not about wireless headers, it is about that mac addresses are overwritten by the miniport "switch". Btw, bridging two ethernet segments does the same behavior.
– peterh
Jun 8 '16 at 5:03
Well, if it were Wi-Fi, then the bridge would have to overwrite MAC addresses because that is in fact required by the wireless headers. (Well, unless you're an AP.). If it's Ethernet-only, then no, that's not required.
– grawity
Jun 8 '16 at 5:04
Well, if it were Wi-Fi, then the bridge would have to overwrite MAC addresses because that is in fact required by the wireless headers. (Well, unless you're an AP.). If it's Ethernet-only, then no, that's not required.
– grawity
Jun 8 '16 at 5:04
@grawity Well, here is a simple description, what is a bridge: en.m.wikipedia.org/wiki/File:Network_Bridging.png . And: 1) a similar configuration works perfectly with Linux 2) bridging 2 ethernet segments with the windows miniport bridge behaves the same. MAC overwrite isn't needed in any cases, where did you get this?
– peterh
Jun 8 '16 at 5:14
@grawity Well, here is a simple description, what is a bridge: en.m.wikipedia.org/wiki/File:Network_Bridging.png . And: 1) a similar configuration works perfectly with Linux 2) bridging 2 ethernet segments with the windows miniport bridge behaves the same. MAC overwrite isn't needed in any cases, where did you get this?
– peterh
Jun 8 '16 at 5:14
@grawity And finally: a "bridge" which overwrites MAC is not a bridge. It is a router.
– peterh
Jun 8 '16 at 5:23
@grawity And finally: a "bridge" which overwrites MAC is not a bridge. It is a router.
– peterh
Jun 8 '16 at 5:23
|
show 1 more comment
1 Answer
1
active
oldest
votes
If segment2 is Wi-Fi, packets from clients in segment1 with their original MAC addresses will be dropped by the wireless AP in segment2 since these MAC addresses have no Wi-Fi association with the AP. Substitution of the MAC addresses at Win7 is one practical solution, no matter if you still want to call it bridging.
answered Jan 15 at 13:03
HakkkHakkk
11
2
Not I call it bridging, the microsoft calls it bridging. What it is not. It is not a "practical solution", it is some different thing what it is called.
– peterh
Jan 15 at 13:23
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1086678%2fwindows-7-miniport-network-bridge-clones-mac-address-what-is-it-how-to-fix%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If segment2 is Wi-Fi, packets from clients in segment1 with their original MAC addresses will be dropped by the wireless AP in segment2 since these MAC addresses have no Wi-Fi association with the AP. Substitution of the MAC addresses at Win7 is one practical solution, no matter if you still want to call it bridging.
answered Jan 15 at 13:03
HakkkHakkk
11
2
Not I call it bridging, the microsoft calls it bridging. What it is not. It is not a "practical solution", it is some different thing what it is called.
– peterh
Jan 15 at 13:23
add a comment |
If segment2 is Wi-Fi, packets from clients in segment1 with their original MAC addresses will be dropped by the wireless AP in segment2 since these MAC addresses have no Wi-Fi association with the AP. Substitution of the MAC addresses at Win7 is one practical solution, no matter if you still want to call it bridging.
answered Jan 15 at 13:03
HakkkHakkk
11
2
Not I call it bridging, the microsoft calls it bridging. What it is not. It is not a "practical solution", it is some different thing what it is called.
– peterh
Jan 15 at 13:23
add a comment |
If segment2 is Wi-Fi, packets from clients in segment1 with their original MAC addresses will be dropped by the wireless AP in segment2 since these MAC addresses have no Wi-Fi association with the AP. Substitution of the MAC addresses at Win7 is one practical solution, no matter if you still want to call it bridging.
answered Jan 15 at 13:03
HakkkHakkk
11
If segment2 is Wi-Fi, packets from clients in segment1 with their original MAC addresses will be dropped by the wireless AP in segment2 since these MAC addresses have no Wi-Fi association with the AP. Substitution of the MAC addresses at Win7 is one practical solution, no matter if you still want to call it bridging.
answered Jan 15 at 13:03
HakkkHakkk
11
answered Jan 15 at 13:03
HakkkHakkk
11
answered Jan 15 at 13:03
HakkkHakkk
11
answered Jan 15 at 13:03
HakkkHakkk
11
11
2
Not I call it bridging, the microsoft calls it bridging. What it is not. It is not a "practical solution", it is some different thing what it is called.
– peterh
Jan 15 at 13:23
add a comment |
2
Not I call it bridging, the microsoft calls it bridging. What it is not. It is not a "practical solution", it is some different thing what it is called.
– peterh
Jan 15 at 13:23
2
2
Not I call it bridging, the microsoft calls it bridging. What it is not. It is not a "practical solution", it is some different thing what it is called.
– peterh
Jan 15 at 13:23
Not I call it bridging, the microsoft calls it bridging. What it is not. It is not a "practical solution", it is some different thing what it is called.
– peterh
Jan 15 at 13:23
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1086678%2fwindows-7-miniport-network-bridge-clones-mac-address-what-is-it-how-to-fix%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Are both segments wired Ethernet? This behavior would be pretty much required if bridging Wi-Fi without WDS.
– grawity
Jun 8 '16 at 4:49
No, what you say is NOT a switch, but a proxy arp. It is not "required behavior", it is not a switch. Wds hasn't anything to do with that, it is not about wireless headers, it is about that mac addresses are overwritten by the miniport "switch". Btw, bridging two ethernet segments does the same behavior.
– peterh
Jun 8 '16 at 5:03
Well, if it were Wi-Fi, then the bridge would have to overwrite MAC addresses because that is in fact required by the wireless headers. (Well, unless you're an AP.). If it's Ethernet-only, then no, that's not required.
– grawity
Jun 8 '16 at 5:04
@grawity Well, here is a simple description, what is a bridge: en.m.wikipedia.org/wiki/File:Network_Bridging.png . And: 1) a similar configuration works perfectly with Linux 2) bridging 2 ethernet segments with the windows miniport bridge behaves the same. MAC overwrite isn't needed in any cases, where did you get this?
– peterh
Jun 8 '16 at 5:14
@grawity And finally: a "bridge" which overwrites MAC is not a bridge. It is a router.
– peterh
Jun 8 '16 at 5:23