Re: [WebDNA] Privat IP website behind a public IP website

This WebDNA talk-list message is from

2014

It keeps the original formatting. numero = 111765
interpreted = N
texte = --Apple-Mail-5FC9ECFA-B762-45F4-BA85-DB143B000127Content-Type: text/plain;charset=utf-8Content-Transfer-Encoding: quoted-printableIn that case you'd have to use 8080 and forward that port to the private ser=verSo your URL for the private server would look like http://63.x.x.74:8080Cheers,Will---William J. Starck, DDSBig Idea Software, LLC15305 Dallas Parkway Suite 300Addison, TX 75001817-800-9634http://www.bigideasoft.com> On Dec 12, 2014, at 4:15 PM, Palle Bo Nielsen w=rote:>=20> Hi Will>=20> As the discussion opens my awareness widens.>=20> Basically I only have one public IP and that is my dilemma.>=20> NAT is turned on on my router/firewall and I am able to make a Port Forwar=d rule.>=20> So maybe mu challenge is the ONE PUBLIC IP. And IF it is; is it hen at all= possible to have the one server on a public IP hosting http and another on t=he local network hosting http as well and both being accessed from the outsi=de.>=20> PS. Sagemcom>=20> /Palle>=20>=20>> On 12/12/2014, at 23.06, WJ Starck, DDS wrote:>>=20>> Right>>=20>> So you should be able to set up your firewall so that http (port 80) requ=ests are handled like this>>=20>> Requests to www.mypublicserver.com (let's say its public IP is 63.x.x.74)= get pointed to your public server=20>>=20>> Then you'll need a second public IP, say 63.x.x.75, that gets pointed (po=rt forwarded) to your internal server, say 192.168.1.75. You'll need NAT tur=ned on in your firewall. You probably don't want DNS setup for the private h=ost (I'm guessing) so you'd just access it with http://63.x.x.75>>=20>> What firewall are you running (feel free to email me off list at wjs@webd=na.us if you don't want to say publicly)?>>=20>> Cheers,>>=20>> Will>>=20>>=20>> --->> William J. Starck, DDS>> Big Idea Software, LLC>> 15305 Dallas Parkway Suite 300>> Addison, TX 75001>> 817-800-9634>> http://www.bigideasoft.com>>=20>>> On Dec 12, 2014, at 3:41 PM, Palle Bo Nielsen = wrote:>>>=20>>> Yes, but I need to server HTTP request from both the public server (63.x=.x.x) and the private server (192.168.x.x)>>>=20>>> PS. I use FastCGI on both>>>=20>>> /Palle>>>=20>>>=20>>>> On 12/12/2014, at 22.19, WJ Starck, DDS wrote:>>>>=20>>>> Palle->>>>=20>>>> You don't have to do that.>>>>=20>>>> Like Dan said, just assign a public IP to your private server, then set=up your firewall to port forward requests for port 80 from that public IP to= the private IP of the internal server. Are you using WebDNA server of FastC=GI? You might consider using FastCGI for the internal server as the setup wi=ll be easier.>>>>=20>>>> Cheers,>>>>=20>>>> Will>>>>=20>>>>=20>>>> --->>>> William J. Starck, DDS>>>> Big Idea Software, LLC>>>> 15305 Dallas Parkway Suite 300>>>> Addison, TX 75001>>>> 817-800-9634>>>> http://www.bigideasoft.com>>>>=20>>>>> On Dec 12, 2014, at 1:42 PM, Palle Bo Nielsen wrote:>>>>>=20>>>>> a) The :8000 (port)option, wouldn=E2=80=99t that require that all link=s on the privat ip also has :8000 (the port attached) ? The port routing wou=ld be easy.>>>>>=20>>>>> b) How would I do this? I am a bit blank here.>>>>>=20>>>>> /Palle>>>>>=20>>>>>=20>>>>>=20>>>>>> On 12/12/2014, at 19.45, Dan Strong wrote:>>>>>>=20>>>>>> Maybe set up port forwarding on your router for an arbitrary port, sa=y, 8000, and access from the outside like this http://:8000 and all= traffic to this port gets forwarded to 192.168.1.135 or whatever...>>>>>>=20>>>>>> Or you could set up some sort of dyndns on the privare computer and a=cess it that way.>>>>>>=20>>>>>> Obviously I don't know your specifics, but this might be a general pa=th to explore. Hope it helps.>>>>>>=20>>>>>> -Dan Strong>>>>>> http://DanStrong.com>>>>>>=20>>>>>>> On Fri, Dec 12, 2014 at 10:08 AM, Palle Bo Nielsen wrote:>>>>>>> HI>>>>>>>=20>>>>>>> I have a network with a public fixed IP on which a webdna website i r=unning fine.>>>>>>>=20>>>>>>> On the local network NAT=E2=80=99ed behind the public fixed IP I hav=e another physical server with webdna with a privat fixed IP, which is not a=ccessible from the outside.>>>>>>>=20>>>>>>> Is there any WebDNA way I can access the server on the private netwo=rk from the outside, possible using the Publicly available WebDNA server?>>>>>>>=20>>>>>>> /Palle--------------------------------------------------------->>>>>>> This message is sent to you because you are subscribed to>>>>>>> the mailing list .>>>>>>> To unsubscribe, E-mail to: >>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us>>>>>>> Bug Reporting: support@webdna.us>>>>>> --------------------------------------------------------- This messag=e is sent to you because you are subscribed to the mailing list . To unsubsc=ribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Rep=orting: support@webdna.us>>>>>=20>>>>> --------------------------------------------------------- This message= is sent to you because you are subscribed to the mailing list . To unsubscr=ibe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Repo=rting: support@webdna.us>>>> --------------------------------------------------------- This message i=s sent to you because you are subscribed to the mailing list . To unsubscrib=e, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Report=ing: support@webdna.us>>>=20>>> --------------------------------------------------------- This message i=s sent to you because you are subscribed to the mailing list . To unsubscrib=e, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Report=ing: support@webdna.us>> --------------------------------------------------------- This message is= sent to you because you are subscribed to the mailing list . To unsubscribe=, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporti=ng: support@webdna.us>=20> --------------------------------------------------------- This message is s=ent to you because you are subscribed to the mailing list . To unsubscribe, E=-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting:= support@webdna.us--Apple-Mail-5FC9ECFA-B762-45F4-BA85-DB143B000127Content-Type: text/html;charset=utf-8Content-Transfer-Encoding: quoted-printable

In that case you'd have to use 8080 an=d forward that port to the private server

So your U=RL for the private server would look like =http://63.x.x.74:8080

Cheers,

Will<=/div>

---

William J. Starck, DDS

Big Idea Software, LLC

15305 Dallas Parkway Suite 300

Addison, TX 75001

817-800-9634

http://www.bigideasoft.com

On Dec 12, 2014, at 4:15 PM, Palle Bo Nielsen <powerpalle@powerpalle.dk> wrote:

Hi Will

As the discussion opens my awareness widens.

Basically I only hav=e one public IP and that is my dilemma.

NAT is turned on on my router/firewa=ll and I am able to make a Port Forward rule.

So maybe mu challenge is the O=NE PUBLIC IP. And IF it is; is it hen at all possible to have the one server= on a public IP hosting http and another on the local network hosting http a=s well and both being accessed from the outside.

PS. Sagemcom

/Palle

On 12=/12/2014, at 23.06, WJ Starck, DDS <wjs@bigideasoft.com> wrote:

Right

So y=ou should be able to set up your firewall so that http (port 80) requests ar=e handled like this

Requests to www.mypu=blicserver.com (let's say its public IP is 63.x.x.74) get pointed to you=r public server

Then you'll need a second public IP, say 63.x.x.75, that gets pointed (po=rt forwarded) to your internal server, say 192.168.1.75. You'll need NAT tur=ned on in your firewall. You probably don't want DNS setup for the private h=ost (I'm guessing) so you'd just access it with http://63.x.x.75

=
What firewall are you running (feel free to email me off lis=t at wjs@webdna.us if you do=n't want to say publicly)?

Cheers,

W=ill

---
William J. Starck, DDS
Big Idea Software, LLC
15305 Dallas Parkway Suite 300
Add=ison, TX 75001
817-800-9634
http://www.bigideasoft.com<=/a>

On Dec 12, 2014, at 3:41= PM, Palle Bo Nielsen <powerpalle@powerpalle.dk> wrote:

Yes, but I need to server HTTP request from both the publi=c server (63.x.x.x) and the private server (192.168.x.x)

PS. I use FastCGI on both

/Palle

On 12/12/2014, at 22.19, WJ Starck, DDS <=wjs@bigideasoft.com>=; wrote:

Palle-
You don't have to do that.

Like Dan said, just assign a pub=lic IP to your private server, then setup your firewall to port forward requ=ests for port 80 from that public IP to the private IP of the internal serve=r. Are you using WebDNA server of FastCGI? You might consider using FastCGI f=or the internal server as the setup will be easier.
Cheers,

Will

---
William J. Starck, DDS
Big Id=ea Software, LLC
15305 Dallas Parkway Suite 300
=
Addison, TX 75001
817-800-9634
=
http://w=ww.bigideasoft.com

On De=c 12, 2014, at 1:42 PM, Palle Bo Nielsen <powerpalle@powerpalle.dk> wrote:

=
a) The :8000 (port)option, wouldn=E2=80=99t that requ=ire that all links on the privat ip also has :8000 (the port attached) ? The= port routing would be easy.

b) How would I do this? I am a bit blank here.

/Palle

On 12/12/2014, at 19.45, Dan Strong <dan@danstrong.com> wrote:

Maybe set up por=t forwarding on your router for an arbitrary port, say, 8000, and access fro=m the outside like this http://<your-ip>:8000 and all traffic to this p=ort gets forwarded to 192.168.1.135 or whatever...

Or you could set up some sort of dyndns on the priv=are computer and acess it that way.

Obviously I don't know your specifics, but this might be a= general path to explore. Hope it helps.

-Dan Strong
http://DanStrong.com
<=/div>

On Fri, Dec 12, 2014 at 10:08 AM, P=alle Bo Nielsen <powerpalle@powerpalle.dk&g=t; wrote:
HI

I have a network with a public fixed IP on which a webdna website i running f=ine.

On the local network NAT=E2=80=99ed behind the public fixed IP I have anothe=r physical server with webdna with a privat fixed IP, which is not accessibl=e from the outside.

Is there any WebDNA way I can access the server on the private network from t=he outside, possible using the Publicly available WebDNA server?

/Palle---------------------------------------------------------
This message is sent to you because you are subscribed to
the mailing list <talk@webdn=a.us>.
To unsubscribe, E-mail to: <talk-leave@webdna.us>
archives: http://mail.webdna.us/list/talk@webdna.us
Bug Reporting: support@webdn=a.us

---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: h=ttp://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdn=a.us
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: h=ttp://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdn=a.us
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: h=ttp://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdn=a.us
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: h=ttp://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdn=a.us
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: h=ttp://mail.webdna.us/list/talk@webdna.usBug Reporting: support@webdn=a.us

---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list .To unsubscribe, E-mail to: archives: http://mail.=webdna.us/list/talk@webdna.usBug Reporting: support@webdna.us

=--Apple-Mail-5FC9ECFA-B762-45F4-BA85-DB143B000127-- Associated Messages, from the most recent to the oldest:

Re: [WebDNA] Privat IP website behind a public IP website ("WJ Starck, DDS" 2014)
Re: [WebDNA] Privat IP website behind a public IP website (Palle Bo Nielsen 2014)
Re: [WebDNA] Privat IP website behind a public IP website ("WJ Starck, DDS" 2014)
Re: [WebDNA] Privat IP website behind a public IP website (Palle Bo Nielsen 2014)
Re: [WebDNA] Privat IP website behind a public IP website ("WJ Starck, DDS" 2014)
Re: [WebDNA] Privat IP website behind a public IP website (Palle Bo Nielsen 2014)
Re: [WebDNA] Privat IP website behind a public IP website (Dan Strong 2014)
[WebDNA] Privat IP website behind a public IP website (Palle Bo Nielsen 2014)

--Apple-Mail-5FC9ECFA-B762-45F4-BA85-DB143B000127Content-Type: text/plain;charset=utf-8Content-Transfer-Encoding: quoted-printableIn that case you'd have to use 8080 and forward that port to the private ser=verSo your URL for the private server would look like http://63.x.x.74:8080Cheers,Will---William J. Starck, DDSBig Idea Software, LLC15305 Dallas Parkway Suite 300Addison, TX 75001817-800-9634http://www.bigideasoft.com> On Dec 12, 2014, at 4:15 PM, Palle Bo Nielsen w=rote:>=20> Hi Will>=20> As the discussion opens my awareness widens.>=20> Basically I only have one public IP and that is my dilemma.>=20> NAT is turned on on my router/firewall and I am able to make a Port Forwar=d rule.>=20> So maybe mu challenge is the ONE PUBLIC IP. And IF it is; is it hen at all= possible to have the one server on a public IP hosting http and another on t=he local network hosting http as well and both being accessed from the outsi=de.>=20> PS. Sagemcom>=20> /Palle>=20>=20>> On 12/12/2014, at 23.06, WJ Starck, DDS wrote:>>=20>> Right>>=20>> So you should be able to set up your firewall so that http (port 80) requ=ests are handled like this>>=20>> Requests to www.mypublicserver.com (let's say its public IP is 63.x.x.74)= get pointed to your public server=20>>=20>> Then you'll need a second public IP, say 63.x.x.75, that gets pointed (po=rt forwarded) to your internal server, say 192.168.1.75. You'll need NAT tur=ned on in your firewall. You probably don't want DNS setup for the private h=ost (I'm guessing) so you'd just access it with http://63.x.x.75>>=20>> What firewall are you running (feel free to email me off list at wjs@webd=na.us if you don't want to say publicly)?>>=20>> Cheers,>>=20>> Will>>=20>>=20>> --->> William J. Starck, DDS>> Big Idea Software, LLC>> 15305 Dallas Parkway Suite 300>> Addison, TX 75001>> 817-800-9634>> http://www.bigideasoft.com>>=20>>> On Dec 12, 2014, at 3:41 PM, Palle Bo Nielsen = wrote:>>>=20>>> Yes, but I need to server HTTP request from both the public server (63.x=.x.x) and the private server (192.168.x.x)>>>=20>>> PS. I use FastCGI on both>>>=20>>> /Palle>>>=20>>>=20>>>> On 12/12/2014, at 22.19, WJ Starck, DDS wrote:>>>>=20>>>> Palle->>>>=20>>>> You don't have to do that.>>>>=20>>>> Like Dan said, just assign a public IP to your private server, then set=up your firewall to port forward requests for port 80 from that public IP to= the private IP of the internal server. Are you using WebDNA server of FastC=GI? You might consider using FastCGI for the internal server as the setup wi=ll be easier.>>>>=20>>>> Cheers,>>>>=20>>>> Will>>>>=20>>>>=20>>>> --->>>> William J. Starck, DDS>>>> Big Idea Software, LLC>>>> 15305 Dallas Parkway Suite 300>>>> Addison, TX 75001>>>> 817-800-9634>>>> http://www.bigideasoft.com>>>>=20>>>>> On Dec 12, 2014, at 1:42 PM, Palle Bo Nielsen wrote:>>>>>=20>>>>> a) The :8000 (port)option, wouldn=E2=80=99t that require that all link=s on the privat ip also has :8000 (the port attached) ? The port routing wou=ld be easy.>>>>>=20>>>>> b) How would I do this? I am a bit blank here.>>>>>=20>>>>> /Palle>>>>>=20>>>>>=20>>>>>=20>>>>>> On 12/12/2014, at 19.45, Dan Strong wrote:>>>>>>=20>>>>>> Maybe set up port forwarding on your router for an arbitrary port, sa=y, 8000, and access from the outside like this http://:8000 and all= traffic to this port gets forwarded to 192.168.1.135 or whatever...>>>>>>=20>>>>>> Or you could set up some sort of dyndns on the privare computer and a=cess it that way.>>>>>>=20>>>>>> Obviously I don't know your specifics, but this might be a general pa=th to explore. Hope it helps.>>>>>>=20>>>>>> -Dan Strong>>>>>> http://DanStrong.com>>>>>>=20>>>>>>> On Fri, Dec 12, 2014 at 10:08 AM, Palle Bo Nielsen wrote:>>>>>>> HI>>>>>>>=20>>>>>>> I have a network with a public fixed IP on which a webdna website i r=unning fine.>>>>>>>=20>>>>>>> On the local network NAT=E2=80=99ed behind the public fixed IP I hav=e another physical server with webdna with a privat fixed IP, which is not a=ccessible from the outside.>>>>>>>=20>>>>>>> Is there any WebDNA way I can access the server on the private netwo=rk from the outside, possible using the Publicly available WebDNA server?>>>>>>>=20>>>>>>> /Palle--------------------------------------------------------->>>>>>> This message is sent to you because you are subscribed to>>>>>>> the mailing list .>>>>>>> To unsubscribe, E-mail to: >>>>>>> archives: http://mail.webdna.us/list/talk@webdna.us>>>>>>> Bug Reporting: support@webdna.us>>>>>> --------------------------------------------------------- This messag=e is sent to you because you are subscribed to the mailing list . To unsubsc=ribe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Rep=orting: support@webdna.us>>>>>=20>>>>> --------------------------------------------------------- This message= is sent to you because you are subscribed to the mailing list . To unsubscr=ibe, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Repo=rting: support@webdna.us>>>> --------------------------------------------------------- This message i=s sent to you because you are subscribed to the mailing list . To unsubscrib=e, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Report=ing: support@webdna.us>>>=20>>> --------------------------------------------------------- This message i=s sent to you because you are subscribed to the mailing list . To unsubscrib=e, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Report=ing: support@webdna.us>> --------------------------------------------------------- This message is= sent to you because you are subscribed to the mailing list . To unsubscribe=, E-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporti=ng: support@webdna.us>=20> --------------------------------------------------------- This message is s=ent to you because you are subscribed to the mailing list . To unsubscribe, E=-mail to: archives: http://mail.webdna.us/list/talk@webdna.us Bug Reporting:= support@webdna.us--Apple-Mail-5FC9ECFA-B762-45F4-BA85-DB143B000127Content-Type: text/html;charset=utf-8Content-Transfer-Encoding: quoted-printable