Oliver Freyermuth

@vague666 That parameter not set. Should it matter for non-passive DCC?

Interestingly, running: ``` /set dcc_own_ip 0.0.0.0 ``` fixes the issue. Is this expected? I would expect `0.0.0.0` to be used automatically when binding, especially when doing active DCC, no?

@ailin-nemui, thanks for coming back to this. Here's what I observe in a table: | local machine | dcc_own_ip | remote host | XDCC works? | |-------------------|-----------------|-----------------|-------------------| | dual-stacked |...

That is actually my current (default) setting (using a 5.4.8 kernel here, no overrides for that variable in `sysctl.conf` / `sysctl.d`): ``` $ sysctl -a | grep net.ipv6.bindv6only net.ipv6.bindv6only =...

> While I can understand your usecase, this would be a major development effort. As it's not something needed by CERN, the chance that we implement such a feature is...

Thanks! I think with these two (or at least one of these) we could achieve the wanted behaviour, without going a full ACL route. The open-ness of CERN is sadly...

> Sounds like it would partially solve #169, right? It's surely an ingredient, but the focus here is different: It allows to connect to workers spawned by JupyterHub via a...

I pushed two more commits here which ensure no port collision happens for the forwarded port. This is achieved by choosing a random port on the Hub and forwarding the...

Rebased to current `master` to get the new CI working.

I pushed three more commits with a small improvement, and two more changes: - It is now possible to disable the `connect_to_job` feature for the `CondorSpawner` again to allow reverting...