Network troubleshooting assistant

[korda]

With a bigger network spread, managed by a central client (mac 000001), we are missing an option of a mobile assistant(s) client PC going in the area of troubles and listening on main client communications where it can, so it can locate remote unit under question.
Right now central comm associated with the bridge mac, connected to a client. We do not really use bridge mac, it should all be going to mac 000001. Why make bridge responsible for any data processing, if one has a PC connected to it with much more computing power?
At this point second client with the same mac as the main client does not get anything, unless asks data directly. This creates a confusion. We are trying to avoid situation when there are many masters on the net.

[kbanks]

second client with the same mac as the main client

is not allowed/not supported. If you are using Portal, you can tell each copy to be a different address on the network (the laptop could be 00.00.02 for example).

Gateway clients specify what address they want to be as one of their XML-RPC parameters.

In either case, if you want you communications to work, give everybody unique addresses.

[korda]

Unfortunately you completely missed the point. And why two clients are not allowed to have the same mac and what reason? I have tried - it works, not the way we would like, but it works. I think because synapse mesh now coupled with the real mac on the connected bridge (even if bridge is used as passive transport) - that is the obstacle for this very useful feature.

[mgenti]

I remember discussing this with you on the phone before so I believe I understand what you are describing. We have this idea on our list to consider for future revisions.