and it will break any failover system too.<br><br><br><br><div class="gmail_quote">On Fri, Dec 12, 2008 at 8:49 AM, Hurliman, John <span dir="ltr"><<a href="mailto:john.hurliman@intel.com">john.hurliman@intel.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Resolving all hostnames to IP addresses would break virtual hosting, a very common practice. I don't understand your earlier argument: we can't assume DNS presence*, so we should use DNS to resolve all hostnames? Can you clarify that?<br>
<br>
*If you're building a virtual world in an environment where there is no DNS service, why would you put a hostname in your config file?<br>
<br>
John<br>
<div class="Ih2E3d"><br>
> -----Original Message-----<br>
> From: <a href="mailto:opensim-dev-bounces@lists.berlios.de">opensim-dev-bounces@lists.berlios.de</a> [mailto:<a href="mailto:opensim-dev-">opensim-dev-</a><br>
> <a href="mailto:bounces@lists.berlios.de">bounces@lists.berlios.de</a>] On Behalf Of Melanie<br>
> Sent: Thursday, December 11, 2008 9:31 PM<br>
> To: <a href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</a><br>
</div><div><div></div><div class="Wj3C7c">> Subject: Re: [Opensim-dev] external host name<br>
><br>
> Then we should resolve all hostname fields int he LL stack, and feed<br>
> the client IP addresses. That should still allow us flexible handling.<br>
> Most importantly, we should not string-compare hostss. Not if (host a<br>
> == host b) but if (resolve(host a) == resolve(host b))<br>
><br>
> Melanie<br>
><br>
><br>
> Diva Canto wrote:<br>
>> I agree. The problem is that the client doesn't understand that, and<br>
>> this causes problems with caps urls.<br>
>><br>
>> Melanie wrote:<br>
>>> A host name can also be an IP address. IP addresses and hostnames are<br>
>>> interchangable and we can't assume DNS presence. So, the field should<br>
>>> accept a name or IP, and resolve names, like almost everything else on<br>
>>> the internet does.<br>
>>><br>
>>> Melanie<br>
>>><br>
>>><br>
>>> Cristina Videira Lopes wrote:<br>
>>><br>
>>>> The thing is that this can potentially create a RegionInfo data<br>
>>>> structure with<br>
>>>> nRegionInfo.ExternalHostName = regionData.IPADDR;<br>
>>>><br>
>>>> This is inconsistent with certain queries on the Grid server, like<br>
>>>> "give me all my neighbors" which may send host names.<br>
>>>><br>
>>>> So, back to the point: someone needs to decide what is it that<br>
>>>> RegionInfo.ExternalHostName is supposed to hold.<br>
>>>><br>
>>>> Teravus Ovares wrote:<br>
>>>><br>
>>>>> RegionUpData is my fault, and spawned from compatibility issues<br>
>>>>> with .NET remoting and Mono remoting with complex types. It is<br>
>>>>> only used to notify a neighbor region that 'this region is up'<br>
>>>>><br>
>>>>> Best Regards<br>
>>>>><br>
>>>>> Teravus<br>
>>>>><br>
>>>>> On 12/11/08, Cristina Videira Lopes <<a href="mailto:lopes@ics.uci.edu">lopes@ics.uci.edu</a>> wrote:<br>
>>>>><br>
>>>>><br>
>>>>>> Things are very messy right now. You can search for "sim_ip", for<br>
>>>>>> example, which is used in chatting with the grid server, and where<br>
>>>>>> it is being converted to an IP address in about half of the cases.<br>
>>>>>><br>
>>>>>> To compensate, and before I noticed this inconsistency, Homer<br>
>>>>>> introduced another field called "sim_host", so not to mess with<br>
>>>>>> what was already there, that is supposed to carry the external host<br>
>>>>>> name, but this only works up to the point in which RegionInfo data<br>
>>>>>> structures are created. At that point, we need to decide what to<br>
>>>>>> place in m_externalHostName, sim_ip or sim_host. Which means<br>
>>>>>> changes in OGS1.<br>
>>>>>><br>
>>>>>> I also noticed that there is yet another data structure called<br>
>>>>>> RegionUpData that uses IP addresses.<br>
>>>>>><br>
>>>>>> So, messy. Someone should decide what this field is supposed to<br>
>>>>>> be, and make it a rule.<br>
>>>>>><br>
>>>>>> Charles Krinke wrote:<br>
>>>>>><br>
>>>>>> Dear Diva:<br>
>>>>>><br>
>>>>>> You have a very good point and I would support harmonizing to<br>
>>>>>> one notion even at the expense of breaking some things for a while.<br>
>>>>>><br>
>>>>>> In fact, if someone can identify what some of those things are, or<br>
>>>>>> come up with a couple of search strings or grep expressions, I<br>
>>>>>> would like to look at the anomalies myself.<br>
>>>>>><br>
>>>>>> +1 on external_host_name<br>
>>>>>><br>
>>>>>> Charles<br>
>>>>>><br>
>>>>>> ________________________________<br>
>>>>>><br>
>>>>>><br>
>>>>>> From: Cristina Videira Lopes <<a href="mailto:lopes@ics.uci.edu">lopes@ics.uci.edu</a>><br>
>>>>>> To: <a href="mailto:opensim-dev@lists.berlios.de">opensim-dev@lists.berlios.de</a><br>
>>>>>> Sent: Thursday, December 11, 2008 2:42:05 PM<br>
>>>>>> Subject: [Opensim-dev] external host name<br>
>>>>>><br>
>>>>>> It turns out that a lot of problems with CAPs have to do with<br>
>>>>>> inconsistencies surrounding the URL of the seed cap. Specifically,<br>
>>>>>> in some cases we're producing URLs with hostnames, other times<br>
>>>>>> we're producing URLs with IP addresses, for example:<br>
>>>>>><br>
>>>>>> <a href="http://ucigrid03.nacs.uci.edu:9000/CAPS/4cfc94fa-09be-409b-b136-" target="_blank">http://ucigrid03.nacs.uci.edu:9000/CAPS/4cfc94fa-09be-409b-b136-</a> cd<br>
</div></div>>>>>>> a2cdde0000/ vs. MailScanner has detected a possible fraud attempt<br>
<div><div></div><div class="Wj3C7c">>>>>>> from "<a href="http://128.200.71.43:9000" target="_blank">128.200.71.43:9000</a>" claiming to be MailScanner warning:<br>
>>>>>> numerical links are often malicious:<br>
>>>>>> <a href="http://128.200.71.43:9000/CAPS/4cfc94fa-09be-409b-b136-" target="_blank">http://128.200.71.43:9000/CAPS/4cfc94fa-09be-409b-b136-</a> cda2cdde000<br>
>>>>>> 0/<br>
>>>>>><br>
>>>>>> The client is not smart enough to test if this is the same host,<br>
>>>>>> it assumes it isn't, so it decides someone's trying to game it.<br>
>>>>>><br>
>>>>>> The inconsistencies are all over the code in OpenSim, and they<br>
>>>>>> pertain to the use of ExternalHostName in several data s!<br>
>>>>>> tructures. In some cases, an explicit conversion to IP addresses is<br>
>>>>>> made.<br>
>>>>>><br>
>>>>>> We should converge to one single thing. And I believe that thing<br>
>>>>>> should be whatever it is given in external_host_name config. Is<br>
>>>>>> this right? However, I am a bit afraid this is going to break 17<br>
>>>>>> different things...<br>
>>>>>><br>
>>>>>> Crista<br>
>>>>>><br>
>>>>>> _______________________________________________<br>
>>>>>> Opensim-dev mailing list<br>
>>>>>> <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
>>>>>> <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
>>>>>> ________________________________<br>
>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>> _______________________________________________<br>
>>>>> Opensim-dev<br>
>>>>><br>
>>>>><br>
>>>>>> mailing<br>
>>>>>> list<br>
>>>>>><br>
>>>>>><br>
>>>>> <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
>>>>> <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
>>>>><br>
>>>>><br>
>>>>>> _______________________________________________<br>
>>>>>> Opensim-dev mailing list<br>
>>>>>> <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
>>>>>> <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>>><br>
>>>>> _______________________________________________<br>
>>>>> Opensim-dev mailing list<br>
>>>>> <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
>>>>> <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
>>>>><br>
>>>>><br>
>>>><br>
>>>><br>
>>>> ------------------------------------------------------------------ -<br>
>>>> - ----<br>
>>>><br>
>>>> _______________________________________________<br>
>>>> Opensim-dev mailing list<br>
>>>> <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
>>>> <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
>>>><br>
>>> _______________________________________________<br>
>>> Opensim-dev mailing list<br>
>>> <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
>>> <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
>>><br>
>>><br>
>><br>
>><br>
>><br>
>><br>
>> -------------------------------------------------------------------- -<br>
>> - --<br>
>><br>
>> _______________________________________________<br>
>> Opensim-dev mailing list<br>
>> <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
>> <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
> _______________________________________________<br>
> Opensim-dev mailing list<br>
> <a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
> <a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br>
<a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br>
</div></div></blockquote></div><br>