[prev in list] [next in list] [prev in thread] [next in thread] 

List:       helix-server-dev
Subject:    Re: [Helix-server-dev] NAT and Hostname difficulty.
From:       Aaron Barnes <aaron () stasis ! org>
Date:       2009-04-20 21:23:30
Message-ID: 49ECE7D2.4010204 () stasis ! org
[Download RAW message or body]

Fantastic!  That did the job.  I figured there had to be a way to do 
it.  I appear to have been distracted by the wrong part of the 
documentation.

Thank you for saving me hours of work,

--aaron

Jamie Gordon wrote:
> Don't worry, you should not have to change the URLs. :)
>
> As long as your NAT is routing the RTSP port, your RTSP links should
> work. For the ramgen links as in your example,
> > http://legacypages.com:8080/ramgen/africa/vid1.4.rm
>
> the server will by default use the interface address the HTTP request
> came in on, so if that is getting the wrong address in your setup, then
> you can set the hostname for the ramgen mountpoint configuration.
>
> You will already have a section like the following, you just need to add
> the "hostname"
>     <List Name="RAM File Generator">
>         <Var ShortName="pn-ramgen"/>
>         <Var MountPoint="/ramgen/"/>
>         <Var Hostname="external.ip.addr"/>
>     </List>
>
> This does not require a change to the URLs, it will now use the given
> hostname for all RAMs generated from that mount point.
>
> Same change is needed for the sdpgen mountpoint config if you are using
> sdpgen.
>
> -Jamie
>
> On 4/20/2009 12:00 PM, aaron barnes wrote:
>> I'm in the unfortunate circumstance where I'm having to move a helix
>> server from a public IP to a private IP in a NAT situation, which is
>> presenting a problem.
>>
>> I understand from the docs that the way to do this is to set:
>>
>> <var Hostname="external.ip.addr"/>   in the helix.cfg
>>
>> then append:   ?usehostname to the url of anything accessing the server.
>>
>> Unfortunately, I've got unknown numbers (large numbers) of legacy pages
>> linking to old urls that do not have this, so replacing every link which
>> used to look like:
>>
>> http://legacypages.com:8080/ramgen/africa/vid1.4.rm
>>
>> http://legacypages.com:8080/ramgen/africa/vid1.4.rm?usehostname
>>
>> is going to cause considerable pain.
>>
>> any recommendation of a way around this?  to keep the same urls but fix
>> the NAT addressing problem?
>>
>> Any help/pointers are greatly appreciated,
>>
>> --aaron
>>
>>
>> _______________________________________________
>> Helix-server-dev mailing list
>> Helix-server-dev@helixcommunity.org
>> http://lists.helixcommunity.org/mailman/listinfo/helix-server-dev


_______________________________________________
Helix-server-dev mailing list
Helix-server-dev@helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/helix-server-dev
[prev in list] [next in list] [prev in thread] [next in thread]