Hi there,
I manage several rigs running VE Pro, all of which are networked together for ease of transferring files. Each system has its own main and slave. I wrote a couple of rules into our firewalls on each of the Masters to keep them from seeing any but their own Slave, so that when one us moves a file from one rig to another, we don't still connect to the slave of the old rig - that would be bad news.
I used ipfw to block all traffic to the ports specified in the VE Pro manual (6472-6477), and it has generally worked very well. However, I just had a few sessions that, despite that firewall rule, were still connecting to that old slave. The firewall rule I used was "ipfw add deny all from (IP of other master) to any 6472-6477". This works insomuch as the other slaves are no longer visible in the plugin window, but it's still connecting somehow. I'm not a networking expert so it could be I'm not doing it right, but shouldn't prevent VE from connecting at all?
Also, I'm using IPFW because it seemed like the most straightforward of the firewalls built into OSX, but I know that it's deprecated. So far it's been working swimmingly but it seems the upgrade to Mavericks might've changed something.
I'd be interested if anyone else has had to deal with networking multiple slaves, and how you dealt with the problem of preventing errant connections.
Thanks,
Mike
Forum Statistics
196,697 users have contributed to 43,030 threads and 258,429 posts.
In the past 24 hours, we have 6 new thread(s), 10 new post(s) and 89 new user(s).
