OK, so I have a camera DVR that can be accessed remotely via HTTP. Default is port 80 (duh), but that doesn't work since I forward port 80 and 443 to my web server. So I changed it to port 81.

Problem is, my company confines all HTTP traffic to either 80 and 443 (I think). 81 gives me a refused connection, but I know the DVR is accessible since I can ping it from my phone.

I'm not about to launch a port sniffer as I'm sure IS will be calling me in a matter of seconds. 8080 may be open, but I doubt it. Question is, is there a way to route to my DVR via port 80 and still maintain separate web server calls? I was looking into a squid proxy, but not sure that will solve things.

 

Socks proxy is possible, http://www.panix.com/~ruari/censorship.html

Use http://www.canyouseeme.org/ to test a few ports, IS won't know where it's coming from. You are not allowed to ask your it dept to open you a personal forwarding port and route to your local dvr's ip? It's safe and will give you the access you seek with ease.

DVR is accessible via 81? that's weird.

 

I can make the DVR accessible to whatever I want. But since 80 and 443 are forwarded to my server, I chose 81. Could be whatever. BTW, 81 and 8080 are blocked going out.

I use my airport extreme and NAT to simply forward based on port and internal IP address. Basic and it works, unless trying to get out of fort knox, with a limited number of accessible ports.

Can't ask IS. I mean I could, they owe me about 85,000 favors. But this isn't a core requirement for work, so... It'll be denied.

 

Do they allow some other well known ports outbound, like telnet/ftp/ssh/smtp/dns/pop3? If so you could try one of those ports.

There are devices such as F5 load balancer that can look at the URL typed and based on that forward to the proper web server behind it. An apache reverse proxy may work for a home solution.

ex web.scrib.com/ would be forwarded to your your web server while camera.scrib.com/ would goto your camera. Both URL could have the same public IP.

 

use a port above 1023. 0 to 1023 are well-known ports, so there could either be another application running on the port, or it could be blocked by your ISP for whatever reason. it's always best to use 1024 or above since it's less likely to be used to blocked. ymmv

 

How hard is it to set up a reverse proxy?

 

Not too difficult, it's only a few lines in the config file. There are several ways to do it. Here is one way that should do what you want...
http://www.oracle-base.com/articles/...figuration.php

 

Will this work if I'm using a no-ip.org dydns service? Just using a freebie setup right now.

 

BTW, it appears much more involved in Mountain Lion Server than what is depicted above.