<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto">I am good with pcap, no problem, especially if the alternative brings in architecture dependency on PyDECnet.<br><br><div id="AppleMailSignature" dir="ltr"><div><div><span style="background-color: rgba(255, 255, 255, 0);"><br></span></div><div><span style="background-color: rgba(255, 255, 255, 0);">---</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">Supratim Sanyal, W1XMT</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">39.19151 N, 77.23432 W</span></div><div><span style="background-color: rgba(255, 255, 255, 0);">QCOCAL::SANYAL via <a href="http://www.update.uu.se/~bqt/hecnet.html">HECnet</a></span></div></div><div><br></div></div><div dir="ltr"><br>On Mar 10, 2020, at 10:06 AM, Robert Armstrong <<a href="mailto:bob@jfcl.com">bob@jfcl.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr"><blockquote type="cite"><span>issues with the tap adapter. </span><br></blockquote><span></span><br><span> Just curious - is there any disadvantage to using pcap to access tap</span><br><span>devices? Or any advantages to a native interface? I haven't noticed any</span><br><span>problems.</span><br><span></span><br><span>Bob</span><br><span></span><br><span></span><br><span></span><br></div></blockquote></body></html>