@cm said:
you're right - it was rather a rant than a suggestion ;-)
HAHAHA! Hmmmm... maybe that is what's going on. I know someone who is comfortable doing terminal stuff, and will ask a few questions.
Thanks for that info.
- Greg
196,759 users have contributed to 43,031 threads and 258,436 posts.
In the past 24 hours, we have 4 new thread(s), 13 new post(s) and 90 new user(s).
i just stumbled across some hint related to OSX server http://support.apple.com/kb/ht5413
it appears apple has moved from IPFW to PF - the article also indicates older rules might remain active in case you upgraded your system from an earlier version ...
i want a 10.9 capable mac please - at best a MacPro ;-) too much unusable scrap with an apple logo here ...
i just learned there are actually 3 firewalls in OS X: IPFW (deprecated, but former rules might remain active), AFL (the one you have basic access throught the GUI), PF (accessible anly throug pfctl or a third-party-tool)
you can also configure AFL through the command line:
add a computer to the whitelist: /usr/libexec/afctl -w 192.168.0.10 (the IP of the remote computer)
add a class-C network to the whitelist: /usr/libexec/afctl -w 192.168.0.0/24 (your private or audio network)
if that does not solve the issues we had to dive into pfctl ...
Thanks for this info, but I am not really comfortable working with command line stuff. I agree with Greg that this is not a huge problem, but it is a bit of an ongoing irritation and it would be great if it could be fixed.
Best,
Michael
i couldn't agree more ...
i'll try to get my hands on a mavericks capable mac and dive into the depth of firewalling for a more profound knowledge.
as suspected earlier - it _could_ be that UDP ports are not read properly.
This problem persists in the latest VEP update. Again, it is not huge, but it continues to be irritating.
Michael
I has been more than a year since the last post on this topic. I am still having this problem. Paul, is the VSL team still looking for a solution?
Thanks.
Michael
Hi Michael,
Looks like we gave up, at least as far as VE PRO 5 is concerned.
Instead, we´re focussing on implementing many new features from the VE PRO wishlist. Hope this problem can also be solved with the next major upgrade/update (not scheduled yet).
Best,
Paul