| 2 | |
| 3 | These --server-bridges are not over lapping in any way : pki, subnets, wire or clients. |
| 4 | |
| 5 | Note on W10 + HyperV .. |
| 6 | Today, after extensive testing and obviously reconfiguring different bridges between ''HyperV-Host + VMs'' and ''OS Net Interface + TAP'' .. I found that --server-bridge did not pass ''data'' while the Control channel was fully functional. I had to ''rebuild the entire stack'', taking many individual steps '''plus''' reboot(s) before the OS network bridge would function correctly. (Although the HyperV Switch worked locally, it would not function within the OS bridge with TAP adaptor, even though wireshark showed decrypted pings from the client on the local TAP .. routing is enabled). |
| 7 | |
| 8 | Note on W7 |
| 9 | For what ever reason, human error possibly, I was also forced to reboot this machine before the --server-bridge worked. |
| 10 | |
| 11 | I'll update this post if anything changes over night. |