9 Mar
2020
9 Mar
'20
7:49 p.m.
On Mar 9, 2020, at 2:34 PM, Mark J. Blair <nf6x at
nf6x.net> wrote:
PyDECnet is doing a pcap.findalldevs to look for the device you specified. If that
request doesn't work then you'd see this outcome.
What I meant is to specify the address (--hwaddr <addr> or --random-address) in the
circuit config line. If you do that then PyDECnet doesn't attempt to find the
hardware address from the OS.
paul
On Mar 9, 2020, at 10:07 AM, Paul Koning
<paulkoning at comcast.net> wrote:
I haven't used TAP in ages; when I need bridging I use Johnny's bridge. But the
message ("No hardware address") means that PyDECnet tried to find out the MAC
address for the interface you mentioned and could not do so. You can avoid that by
specifying an address explicitly.
Hmm. I also got that error when I set the correct hardware address on the tap0 interface
before launching pydecnet.