<div>It would be nice if it was at least sysop selectable whether user filters set by one SSID would apply to all connections by the same call, irregardless of SSID.</div> <div> </div> <div>I find that users of my program many times are running two instances of it and several times I have seen users with 3 instances of my program. Sometimes from the same IP and sometimes from home and from work, or home and from their remote station. They set all the instances to auto reconnect and all with no SSID. What then happens is each instance reconnects and bumps off an existing connection. This continues for hours and hours on end, causing a huge amount of traffic on the system. To prevent this, I put a routine into the user program has to detect this. It them assignes a random SSID in the range of 1-14 to the user. Then as long as they aren't running more than 15 instances of the program, eventually they all will have different
SSIDs. Then all the excess traffic stops.</div> <div> </div> <div>With ARC, connecting with different random SSIDs is not a problem as all SSIDs from 0-14 use the same filtering. With Spider it is a problem as each SSID has its own set of filters. With ARC if you really want different filtering, then you connect with an SSID of 16 or higher.</div> <div> </div> <div>One of the reasons I am looking into this is when a user connects to my Spider system they may end up connected to any one of 3 different Spider clusters. The filters have to be set on each one. Having 15 possible sets of filters on each of 3 nodes makes it very difficult for me as a sysop to copy filters from one cluster to another without getting really confused. It would be nice if there was just one filter per node per user.</div> <div> </div> <div>Lee</div><p>
<hr size=1>Yahoo! Mail<br>
Bring photos to life! <a href="http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=39174/*http://photomail.mail.yahoo.com">New PhotoMail </a> makes sharing a breeze.