<html><head></head><body><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div>I got private to private worked out... thanks!!<br><br>Before I get myself in too much more trouble with this...</div><div><br></div><div>- is it possible for a Public node to also be a private node? Say I have Public node 43039 (I do) and it works connecting to and accepting connections among other Public nodes. One and only one radio interface. Can I also make it a private node, for example 1001, and able to accept or initiate connects with another known private node?<br><br>Somehow I came to believe this is possible... but it could have been the tacos and creme soda messing with me... <br><br>Perhaps differently - creating a radio-less 'hub' that could 'bridge' public and private?<br><br>Only one node can be associated with the 'chan_ ..." interface on the same server - yes? no?<br><br>I'm trying to reduce the footprint (rack and tower space, power suck, etc.) of a multi-site RF-linked system down to repeater + node at each site. Not every site needs to be publicly addressable/connectable - as you can imagine the feedback mess if someone ignorant the construct started re-connecting different sites together making a gnarly set of loops.</div><div style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"></div></div></body></html>