Core 4.7 Wireshark is called with wrong interface

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Make a simple network so at least one node has an ethernet port
2. Start running the simulation
3. Right click on a node and select Wireshark and eth0
4. Wireshark will complain no such device exists.

Wireshark is being told to open a device for example n1.eth0.155 which does not 
exist. I can see by looking at the available interfaces it should be told to 
open veth1.0.155. TCpdump seems to be fine so must be being called with the 
right device.

What version of the product are you using? On what operating system?

This is with Core 4.7 on Ubuntu 14.04

This is a minor annoyance as once Wireshark is open I can select the right 
device but better if it worked.

Original issue reported on code.google.com by stuartma...@gmail.com on 3 Sep 2014 at 9:16

[GoogleCodeExporter]

Original comment by ahrenh...@gmail.com on 15 Sep 2014 at 3:14

• Changed state: Accepted

[GoogleCodeExporter]

fixed in r580

Original comment by ahrenh...@gmail.com on 15 Sep 2014 at 7:17

• Changed state: Fixed