On 03/15/2013 08:16 AM, Roger Massey wrote:
> How about trying each of eth0, all, any until hopefully one succeeds.
>
> Roger
>
> ** (process:30757): WARNING **: pcap_compile of [(ether proto
> 0x88cc and
> ether dst 01:80:c2:00:00:0e) or (ether proto 0x2000 and ether dst
> 01:00:0c:cc:cc:cc)] failed: [ethernet addresses supported only on
> ethernet/FDDI/token ring/802.11/ATM LANE/Fibre Channel]
>
> I think I may have seen that message before... Sigh...
>
> I might be able to express it in terms of offsets into the packets and
> make that go away, but that's more complicated - so for the
> moment, I'm
> going to revert my change :-(.
>
You saw that process come up, and compile that expression on "any" in my
code?
I could easily make it #ifdefed for the moment - but I assumed that my
code wouldn't work with that on Windows either - because the message
actually does make sense - for example, loopback transports don't have
ethernet packet headers - which is what I'm looking at.
Putting in "eth0" has always been a kludge.
I was planning on sending discovery requests for each non-loopback
transport after I got the information back from network discovery.
--
Alan Robertson <[email protected]> - @OSSAlanR
"Openness is the foundation and preservative of friendship... Let me claim
from you at all times your undisguised opinions." - William Wilberforce
_______________________________________________
Assimilation mailing list - Discovery-Driven Monitoring
[email protected]
http://lists.community.tummy.com/cgi-bin/mailman/listinfo/assimilation
http://assimmon.org/
