MantisBT - opensim
View Issue Details
0007908opensim[GRID] Hypergridpublic2016-05-13 16:092017-12-26 05:43
smxy 
 
highmajoralways
newopen 
master (dev code) 
 
97a471c (doesn't really matter though - any would be affected)
Grid (1 Region per Sim)
BulletSim
Mono / Linux64
Other
N/A
0007908: OpenSim broken with respect to Melanie's recommended Mono, re: reverse DNS lookups that don't match the forward lookup.
Many grids are hosted in such a way (shared hosting or home-hosted with a Dynamicly-assigned address, for example) that their reverse DNS lookup will never match their forward lookup. This has not been a problem until recent Mono versions. According to Melanie, Mono used to cache the forward lookup and return a reverse lookup that was based on the forward lookup, but it no longer does that in recent versions. An example of this is Mono 4.3.2, which is what Melanie recommends as *THE* version of Mono to use. However, as it no longer "fakes" an appropriate reverse lookup, this breaks Hypergrid teleports for any avatar trying to TP to a grid running Mono 4.3.2, when their home grid does not have a reverse DNS entry that matches its forward entry.

Melanie has stated that OpenSim must be fixed to deal with this.
In the case of my grid, I'm able to enter a local A record, for most such grids, into my pfSense firewall, and it generates an appropriate reverse lookup entry for me (like Mono used to), that resolves the problem. However, I'm unable to do that for all such grids, as I found out today, when I discovered two grids on the same hosted server. The reverse lookup, whether provided by their DNS provider or my firewall, can only point to one of them, and the other one is screwed.
No tags attached.
Issue History
2016-05-13 16:09smxyNew Issue
2016-06-06 09:50DivaNote Added: 0030409
2016-06-06 20:20DivaNote Edited: 0030409bug_revision_view_page.php?bugnote_id=30409#r5469
2016-06-08 14:05Mandarinka TastyNote Added: 0030427
2016-06-08 14:49Mandarinka TastyNote Added: 0030428
2016-06-08 15:32Mata HariNote Added: 0030429
2016-06-08 15:34Mata HariNote Edited: 0030429bug_revision_view_page.php?bugnote_id=30429#r5480
2016-06-08 15:38Mata HariNote Edited: 0030429bug_revision_view_page.php?bugnote_id=30429#r5481
2016-06-08 16:00smxyNote Added: 0030430
2016-06-08 16:05Mata HariNote Edited: 0030429bug_revision_view_page.php?bugnote_id=30429#r5482
2016-06-08 17:56Mandarinka TastyNote Deleted: 0030428
2016-06-08 17:56Mandarinka TastyNote Deleted: 0030427
2017-05-22 13:41DivaNote Added: 0031920

Notes
(0030409)
Diva   
2016-06-06 09:50   
(edited on: 2016-06-06 20:20)
smxy, can you provide more info so I can repro this. Ideally I would like to see:

- a controlled setup where you get the failure, and a detailed description of that setup (i.e. which process is running which version of mono), so that I can repro. By 'controlled' I mean something that is 100% under your control and doesn't depend on other people's grids

- a scanned sketch of the network setup, including the two robusts, the two sims and the viewer

- logs of the failure

Thanks.

(0030429)
Mata Hari   
2016-06-08 15:32   
(edited on: 2016-06-08 16:05)
<post removed....apparently irrelevant>

(0030430)
smxy   
2016-06-08 16:00   
You folks are posting about a different issue altogether, hijacking my mantis. Please open a separate mantis for your issues.
(0031920)
Diva   
2017-05-22 13:41   
Ping.
I'd like to get to the bottom of this.
I need a lot more detailed instructions for how to recreate this problem.