Re: [WebDNA] Privat IP website behind a public IP website
This WebDNA talk-list message is from 2014
It keeps the original formatting.
numero = 111763
interpreted = N
texte = --Apple-Mail-0F76E942-0C7E-48B3-A203-AFB03B27DC52 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Right So you should be able to set up your firewall so that http (port 80) request= s are handled like this Requests to www.mypublicserver.com (let's say its public IP is 63.x.x.74) ge= t pointed to your public server=20 Then you'll need a second public IP, say 63.x.x.75, that gets pointed (port f= orwarded) to your internal server, say 192.168.1.75. You'll need NAT turned o= n in your firewall. You probably don't want DNS setup for the private host (= 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 list at wjs@webdna.= us if you don't want to say publicly)? Cheers, Will --- 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 3:41 PM, Palle Bo Nielsen
w= rote: >=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 setup= your firewall to port forward requests for port 80 from that public IP to t= he private IP of the internal server. Are you using WebDNA server of FastCGI= ? You might consider using FastCGI for the internal server as the setup will= 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 links o= n the privat ip also has :8000 (the port attached) ? The port routing would b= e 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, say,= 8000, and access from the outside like this http://:8000 and all t= raffic 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 ace= ss it that way. >>>>=20 >>>> Obviously I don't know your specifics, but this might be a general path= 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 ru= nning fine. >>>>>=20 >>>>> On the local network NAT=E2=80=99ed behind the public fixed IP I have a= nother physical server with webdna with a privat fixed IP, which is not acce= ssible from the outside. >>>>>=20 >>>>> Is there any WebDNA way I can access the server on the private network= 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 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-0F76E942-0C7E-48B3-A203-AFB03B27DC52 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Right
So you s= hould be able to set up your firewall so that http (port 80) requests are ha= ndled like this
Th= en you'll need a second public IP, say 63.x.x.75, that gets pointed (port fo= rwarded) to your internal server, say 192.168.1.75. You'll need NAT turned o= n in your firewall. You probably don't want DNS setup for the private host (= I'm guessing) so you'd just access it with
http= ://63.x.x.75
What firewall are you running (fee= l free to email me off list at
wjs@webdna.u= s if you don't want to say publicly)?
Cheers,
Will
William J. Starck, DDS
Big Idea Software, LLC=
15305 Dallas Parkway Suite 300
Addison, TX 75001
817-800-9634
<= div>= Yes, but I need to server HTTP request from b= oth the public server (63.x.x.x) and the private server (192.168.x.x)
<= div class=3D"">
PS. I use FastCGI on bot= h
/Palle
Palle-
=
You don't have to do that.
Like Dan said, just assign a p= ublic IP to your private server, then setup your firewall to port forward re= quests for port 80 from that public IP to the private IP of the internal ser= ver. Are you using WebDNA server of FastCGI? You might consider using FastCG= I for the internal server as the setup will be easier.
=
Cheers,
Will
<= br class=3D"">
---
William J. Starck, DDS
Big I= dea Software, LLC
15305 Dallas Parkway Suite 300
Addison, TX 75001
a) The :8000 (port)option, wouldn=E2=80=99t that req= uire that all links on the privat ip also has :8000 (the port attached) ? Th= e port routing would be easy.
b) How would I do this? I am a bit blank here.
/Palle
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.
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 to the mailing list
. To unsubscribe, E-mail to: archives: h= ttp://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdn= a.us
--Apple-Mail-0F76E942-0C7E-48B3-A203-AFB03B27DC52 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Right So you should be able to set up your firewall so that http (port 80) request= s are handled like this Requests to www.mypublicserver.com (let's say its public IP is 63.x.x.74) ge= t pointed to your public server=20 Then you'll need a second public IP, say 63.x.x.75, that gets pointed (port f= orwarded) to your internal server, say 192.168.1.75. You'll need NAT turned o= n in your firewall. You probably don't want DNS setup for the private host (= 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 list at wjs@webdna.= us if you don't want to say publicly)? Cheers, Will --- 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 3:41 PM, Palle Bo Nielsen w= rote: >=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 setup= your firewall to port forward requests for port 80 from that public IP to t= he private IP of the internal server. Are you using WebDNA server of FastCGI= ? You might consider using FastCGI for the internal server as the setup will= 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 links o= n the privat ip also has :8000 (the port attached) ? The port routing would b= e 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, say,= 8000, and access from the outside like this http://:8000 and all t= raffic 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 ace= ss it that way. >>>>=20 >>>> Obviously I don't know your specifics, but this might be a general path= 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 ru= nning fine. >>>>>=20 >>>>> On the local network NAT=E2=80=99ed behind the public fixed IP I have a= nother physical server with webdna with a privat fixed IP, which is not acce= ssible from the outside. >>>>>=20 >>>>> Is there any WebDNA way I can access the server on the private network= 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 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-0F76E942-0C7E-48B3-A203-AFB03B27DC52 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Right
So you s= hould be able to set up your firewall so that http (port 80) requests are ha= ndled like this
Th= en you'll need a second public IP, say 63.x.x.75, that gets pointed (port fo= rwarded) to your internal server, say 192.168.1.75. You'll need NAT turned o= n in your firewall. You probably don't want DNS setup for the private host (= I'm guessing) so you'd just access it with
http= ://63.x.x.75
What firewall are you running (fee= l free to email me off list at
wjs@webdna.u= s if you don't want to say publicly)?
Cheers,
Will
William J. Starck, DDS
Big Idea Software, LLC=
15305 Dallas Parkway Suite 300
Addison, TX 75001
817-800-9634
<= div>= Yes, but I need to server HTTP request from b= oth the public server (63.x.x.x) and the private server (192.168.x.x)
<= div class=3D"">
PS. I use FastCGI on bot= h
/Palle
Palle-
=
You don't have to do that.
Like Dan said, just assign a p= ublic IP to your private server, then setup your firewall to port forward re= quests for port 80 from that public IP to the private IP of the internal ser= ver. Are you using WebDNA server of FastCGI? You might consider using FastCG= I for the internal server as the setup will be easier.
=
Cheers,
Will
<= br class=3D"">
---
William J. Starck, DDS
Big I= dea Software, LLC
15305 Dallas Parkway Suite 300
Addison, TX 75001
a) The :8000 (port)option, wouldn=E2=80=99t that req= uire that all links on the privat ip also has :8000 (the port attached) ? Th= e port routing would be easy.
b) How would I do this? I am a bit blank here.
/Palle
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.
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 to the mailing list
. To unsubscribe, E-mail to: archives: h= ttp://mail.webdna.us/list/talk@webdna.us Bug Reporting: support@webdn= a.us
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
WebCatalog for Postcards ? (1997)
Post Limits (1998)
Physical Security for WebCatalog Directories (1997)
WebCat 4.0x database losing data? (2003)
Using Applescript to process WebCatalog functions (1998)
Can webcat 3.0/4.0 handle 1,000,000 hits a day? (2000)
Share cost of training videos! (1998)
PIXO support (1997)
hyperlinking unique input strings on the fly when displayingin HTML (2000)
& not allowed in db by definition? (1999)
More on the email templates (I like it) (1997)
Text data with spaces in them... (1997)
select multiple (1997)
too many nested tags ... (1997)
Extended [ConvertChars] (1997)
Using WC for Bulk Emailings (1997)
Duplicate Cart ID (2001)
Date search - yes or no (1997)
Applescript error (1998)
Keep away (1997)