Originally Posted by cdoublejj
Well what does a hub do? i just send the packets every where it it dumb hardware. it does not what PC is where what request cam form where it just send the packets to every port. the computers A gets the packet the Computer B requested at the same time Computer B gets however Computer B doesn't do any thing with it.
I might Host and VM would get a minecraft packet request but, since only host has an MC server Host is the only 1 that does any thing with it. Guest just ignores it, host and VM get a request for Feed The Beast but, since VM is the only one with a Feed the Beast Server, VM is the only one that does any thing with packet and Host ignores the packet.
As it is my router won't let me open up the same ports for different Ip addressed to i have to open different port ranger for VM and Host to run games game servers. Since all the traffic is coming from the Same physical NIC, guest gets to piggy back off the dynamic IP linked to host. That may not be the correct or entirely correct reasoning why why dynamic service works for guest if it indeed has virtual NIC.
EDIT: Nope i think it's because the both use the same modem and that's the IP my dynamic IP service sees. ^_^
A hub does not do what you are seeking. A hub is the exact same as a switch, except packets are broadcast instead of unicast, but only one item (the destination) responds. Hubs are beyond bad, period. A good switch can do port mirroring, but that's usually for something like IDS.
I seriously don't understand why you are wanting to do this though. Hyper-V creates a virtual network and virtual NICs live on this network, and basically, the physical NIC tied to this virtual network is the gateway port out of the that virtual network. Once you tie a NIC to a virtual NIC in Hyper-V, you would treat it just like a separate computer since it emulates that NIC with it's own MAC address. If you have two services running on your network, one on one server and one on the other, you need to configure these services to use different ports. This has nothing to do with virtualization and is just how things are meant to be.
Regardless, you should not be running anything on the physical server if it's running the Hyper-V role. It should ONLY be your hypervisor and nothing else.
No router will let you open the same port for multiple destination IPs, as it would get confused (again, this is by design). Not to be rude, but whatever it is you're doing...you're doing it wrong and you need to redesign your system/solution/services.