There is no way of doing that. We never found a reason as we can flow the
data throug the same IP address and avoid the standard overhead (not that
it matters much if you're transfering a big file). Also, how would your
proposal be applicable for anything but inside transfers (i.e intranet)?
On Sun, 17 May 2020, Justas Bal?as wrote:
> Is this what admins can control? Do we have documentation for this? I was going back and forth and don't see any such ways. The idea is: Does not matter which protocol (ROOT, HTTP, DAV) and for xrootd server I want to configure:
> the control interface is 192.168.0.1:2094 and the data interface is 10.0.0.1. Any client connecting to 192.168.0.1:2094 and want to transfer file locally or to another xrootd server would use 10.0.0.1 interface/network. So Client/Server Auth/mappinng happens via 192.168.0.1:2094, but data flows via 10.0.0.1.
>
> --
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/1192#issuecomment-629891262
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/xrootd/xrootd/issues/1192#issuecomment-629936869",
"url": "https://github.com/xrootd/xrootd/issues/1192#issuecomment-629936869",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
