OK, we came up with a curious scenario. Wilko had his redirector on a host
with only a public IP address while the data server was on a host with a
private IP address. He used the default settings which currently is split
routing. He connected to the redirector using a public IP address and was,
obviously, told that the server that had the file was not reachable. Now,
the problem is that at SLAC public and private addresses are all reachable
both ways within the site because that's how the networking people set it
up. So, he was rightfully confused. The solution for him was this awkward
directive
xrd.network routes local eth0,eth0
So, two questions come up:
1) What should be the default setting? I am now tempted to say "local"
because that's how the old xrootd acted. Nnever mind that sites with
*actual* pulic/private network folks were just as confused; at least it
would be consistent. So, should the default be "local"?
2) Since each machine had a single interface it doesn't make sense to
require that you specify the interfaces (notice that you are explicitly
saying that by repeating the same interface). So, the question is should
it be required that the interfaces be specified and if so, when? The
choices are:
a) Make it optional and if you really have a dual homed machines you
better specify it or it becomes unpredictable whether or not the machine
will be reachable it the routes are not local.
b) Make it optional only for 'routes local' since it's likely you are
using single homed machines. If you have a dual homed machine you can
specify that but if you don't it will still work in a predictable, though
not ideal, way.
I sort of favor (b) but it's a toss up.
So what are your thoughts? Read all about it here:
http://www.xrootd.org/doc/dev4/xrd_config.htm#_Toc380525648
Andy
########################################################################
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
|