Unfortunately, it appears there is no way to get an interface's ethernet address out of libpcap, as it currently stands. (I don't think libpcap actually bothers with trying to get the ethernet address.) You do get the current IP addresses and netmasks however.
<br><br>I hacked up a patch to spit the interfaces IP Addresses, and netmasks (as returned from libpcap) as the default description if there's not a 'real' description returned from libpcap. I believe anything further starts turning rather Linux specific, and unportable quickly.
<br><br>It spits out things like so:<br><br>sim> show xq eth<br>ETH devices:<br> 0 eth0 (Cur IP: <a href="http://192.168.0.2/255.255.255.0">192.168.0.2/255.255.255.0</a>)<br> 1 eth1 (Cur IP: <None>)<br> 2 vmnet1 (Cur IP:
<a href="http://172.16.133.1/255.255.255.0">172.16.133.1/255.255.255.0</a>)<br> 3 vmnet8 (Cur IP: <a href="http://192.168.192.1/255.255.255.0">192.168.192.1/255.255.255.0</a>)<br><br>sim> show xq eth<br>ETH devices:<br>
0 eri0 (Cur IP: XXX.XXX.XX.X/255.255.252.0)<br><br>sim> show xq eth<br>ETH devices:<br> 0 lan0 (Cur IP: <a href="http://10.196.100.20/255.255.254.0">10.196.100.20/255.255.254.0</a>, <a href="http://10.196.100.13/255.255.254.0">
10.196.100.13/255.255.254.0</a>)<br> 1 lan4 (Cur IP: <a href="http://1.1.1.1/255.0.0.0">1.1.1.1/255.0.0.0</a>)<br><br><br>I tested it on Linux (Ubuntu) , Solaris 9 (Sparc) and HPUX 11 (obviously). I can't test it on Windows since I've no compilers. (Unless SIMH compiles with Cygwin?)
<br><br>Hope someone finds this of some vague use... <br><br>David<br><br><br><div class="gmail_quote">On Jan 24, 2008 9:28 AM, David Holland <<a href="mailto:david.w.holland@gmail.com">david.w.holland@gmail.com</a>> wrote:
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><div class="gmail_quote">On Jan 24, 2008 8:34 AM, Hittner, David T. <<a href="mailto:david.hittner@ngc.com" target="_blank">
david.hittner@ngc.com</a>> wrote:<br><div>>snip< <br></div><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>We would be happy for anyone familiar with *ix device programming to provide<br>the code to fill in the device description string to help make it more obvious<br>which adapter you are selecting.</blockquote></div><div>
<br>I suspect about the only things you're going to get in that regard would be for libpcap to give you the ethernet address associated with a given device, maybe IP address (if there's one assigned) as well. Anything beyond that I would think starts getting (IMO) rather unportable.
<br><br>Are you looking for more? <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>Dave<br>SIMH Ethernet developer<br>
<div>
<div></div><br></div></blockquote></div>
</blockquote></div><br>