On 2013-12-06 11:21, Mark Pizzolato - Info Comm wrote:
Hi Gregg,
On Thursday, December 05, 2013 at 8:03 PM, Gregg Levine wrote:
Okay so I've managed to install the VDE components and the PCAP
development components on my Raspberry Pi. Invoking make caused the
build system to "choose" the VDE components. Why? When both are
present I figured it would chose both rather then the one I'm not familiar
with.
In any case I know I can work with what the methods chose and eventually
accomplish what I am planning on doing with the appropriate simulators.
The build It is not an either or process. It will build using whatever
Ethernet transports methods are available on the local environment when the
build is done and each of those may be available when running with the
simulator you built.
As I recall, when I did this on the Raspberry Pi, I didn't have to look for
libpcap-dev for that platform, I believe it was packaged with the OS. If
/usr/include/pcap.h exists AND libpcap's shared object is available on the
system (i.e. if tcpdump works) that is sufficient to build (and later use at
runtime) with libpcap support.
You don't explain how you think it chose just VDE rather than both. If you
provide the output that make produced while building the simulator it will be
more clear what capabilities are being built in.
Meanwhile, to use one Ethernet transport method over another at run time will
depend on several different goals. You need to be running as root on any Linux
platform in order to inject packets into the network using libpcap.
You need to be running as root to even sniff packets with pcap.
Johnny
_______________________________________________
Simh mailing list
[email protected]
http://mailman.trailing-edge.com/mailman/listinfo/simh
