New answers tagged

0

One way to find out the IP address of a device is with a protocol analyser such as wireshark. If you capture enough traffic from a network interface, you should see some broadcast traffic generated by just about every device on the network. You can then filter for packets with a source MAC matching your router. In wireshark this filter would be eth.src == ...


0

Finally we didn't see a problem in this behaviour and we looked to a full capture of the use case and this only appeared on the end of the test, not during it. So I guess that's only weird but not a real problem. What we finally did was export the Wireshart capture to a PDML file, and we parsed that with a program we built to analize and correlate ...


0

I'm fairly certain that XenServer uses the weak host model, which explains the behavior you're seeing. You probably have two options: Configure the XenServer to use the strong host model, if possible. Assign a different ip address to the interface in question. For an explanation of the strong and weak host models, have a read here: ...



Top 50 recent answers are included