ZeroMQ publishing arp-scan looper software that can synchronize the 'state' of the network. This part runs as root, and maybe on a different machine.
Component 2:
ZeroMQ subscribing thread within dudemon that watches the state of the network, and on changes, potentially triggers the !here and !bye options.
How to deal with packet loss on the network (only actually register someone as gone after n minutes missing... dont register leave events if everyone disappears at once.. etc) need to be figured out.
[shout out to pamela at heatsync labs here]
Component 1:
ZeroMQ publishing arp-scan looper software that can synchronize the 'state' of the network. This part runs as root, and maybe on a different machine.
Component 2:
ZeroMQ subscribing thread within dudemon that watches the state of the network, and on changes, potentially triggers the !here and !bye options.
How to deal with packet loss on the network (only actually register someone as gone after n minutes missing... dont register leave events if everyone disappears at once.. etc) need to be figured out.