[Bf-committers] Netrender?

[Robert]

My bad, I don't normally reply to mailing lists, I'm more of a read-only 
type of person.
I hit reply instead of reply-list.
I'll send this to the mailing list.
-Robert

On 10/7/18 4:34 AM, Alexander Kampmann wrote:
> hey,
>
> Yes, a ssh tunnel or VPN would be an alternative to my ssl auth approach.
>
> I have not spent any time on debugging/diagnosing the checksum
> mismatches and timeouts yet. I wanted to hear whether it makes sense to
> do so first.
>
> Alex
>
> PS: Is there a reason you replied to me directly, rather than to the
> list? Maybe this discussion would be interesting for others?
>
> On 06/10/2018 18:07, Robert wrote:
>> I'm not very familiar with netrender:
>> https://en.blender.org/index.php/Doc:2.6/Manual/Render/Performance/Netrender
>> but I do know that if you leave a port open to the world, it may get
>> used for unintended purposes.
>> My suggestion? SSH to your host and use an SSH tunnel :
>> https://www.revsys.com/writings/quicktips/ssh-tunnel.html
>> You can use Putty if you are on Windows, or terminal otherwise.
>> You can create a script/expect script to start the tunnel when the
>> machine starts up.
>>
>> The other suggestion I would also recommend is Tinc VPN . It is way
>> easier to setup than OpenVPN.
>> I have it on my mac, windows, and linux boxes and they can all see
>> eachother/ I can connect to ports on those behind the firewall. I think
>> you have a public static IP address so that could be your main host.
>>
>> There is probably something going on with conversions in netrender that
>> is causing a checksum mismatch.
>> Have you looked at the upload method of netrender to see what causes this?
>> -Robert
>>
>> On 10/6/18 9:52 AM, Alexander Kampmann wrote:
>>> hi,
>>>
>>> I spend the last couple of days setting up a netrender master in the
>>> google cloud. This was more challenging than I thought it would. There
>>> were two main problems:
>>>
>>> (1) A bug in the code, fixed by myself:
>>> https://developer.blender.org/rBAf975292b1ec103826fe244dfdb851fed0428b624
>>>
>>> (2) There doesn't seem to be any way for master, slave and clients to
>>> authenticate each other. If those services are connected to the
>>> internet, this means anyone could use my render server. I patched the
>>> code to use SSL client authentication (I guess you could also use
>>> something external, e.g. VPN, but that would require more setup).
>>>
>>> Now I can render small files. But for larger scenes, I get either a
>>> timeout on submitting the job, or "File upload but checksum mismatch,
>>> this shouldn't happen" on one of the job files. This means my netrender
>>> master is not usable.
>>>
>>> So, basically I have three questions:
>>>
>>> (1) Is netrender being used successfully by someone? If so, I am
>>> probably doing something wrong.
>>>
>>> (2) Would you like to merge my ssl client authentification code? If
>>> there is a better way of securing master and slave, it might be better
>>> to avoid feature creep.
>>>
>>> (3) Assuming that it actually is that the code is broken, does it make
>>> sense to fix it or is there a better alternative to distributed rendering?
>>>
>>> Best,
>>>
>>> Alex
>>>
>>>
>>>
>>> _______________________________________________
>>> Bf-committers mailing list
>>> Bf-committers at blender.org
>>> https://lists.blender.org/mailman/listinfo/bf-committers