How to locally (within LAN) and publicly (over internet) access an IP camera using only one IP?
Is this possible? If so, how to set it up?
Currently, I access my IP camera via 192.168.1.2:8888 when at home, and some_public_ip:8888 (portforwarded) when out. It's really a hassle having to switch from one configuration to the other each time I start up my IP camera monitoring app on my smartphone/tablet.
networking port-forwarding ip-camera cctv
asked Sep 30 '13 at 7:49
silvernightstarsilvernightstar
211415
|
show 2 more comments
Is this possible? If so, how to set it up?
Currently, I access my IP camera via 192.168.1.2:8888 when at home, and some_public_ip:8888 (portforwarded) when out. It's really a hassle having to switch from one configuration to the other each time I start up my IP camera monitoring app on my smartphone/tablet.
networking port-forwarding ip-camera cctv
asked Sep 30 '13 at 7:49
silvernightstarsilvernightstar
211415
You'll need to point a domain name to your IP address (assuming your home IP is static). This does raise concerns about security though which you will need to read up on.
– Dave
Sep 30 '13 at 8:15
Thanks, but I'm not sure if that would work. I'm already using DDNS to point a particular domain name to my public IP. And when I'm home, I'm still unable to access my IP camera using that domain name (and thus the need for the additional config of 192.168.1.2:8888 for local access).
– silvernightstar
Sep 30 '13 at 9:10
So, your public IP is pointing at your local computer yes?
– Dave
Sep 30 '13 at 9:21
1
Seems like it's an issue with your home router. I know some of those doesn't allow hairpin connections (connections from inside to the public interface of the router).
– Kent
Sep 30 '13 at 10:06
@DaveRook no, only public IP's port 8888 is being forwarded to 192.168.1.2:8888 (the IP camera)
– silvernightstar
Oct 1 '13 at 4:33
|
show 2 more comments
Is this possible? If so, how to set it up?
Currently, I access my IP camera via 192.168.1.2:8888 when at home, and some_public_ip:8888 (portforwarded) when out. It's really a hassle having to switch from one configuration to the other each time I start up my IP camera monitoring app on my smartphone/tablet.
networking port-forwarding ip-camera cctv
asked Sep 30 '13 at 7:49
silvernightstarsilvernightstar
211415
Is this possible? If so, how to set it up?
Currently, I access my IP camera via 192.168.1.2:8888 when at home, and some_public_ip:8888 (portforwarded) when out. It's really a hassle having to switch from one configuration to the other each time I start up my IP camera monitoring app on my smartphone/tablet.
networking port-forwarding ip-camera cctv
networking port-forwarding ip-camera cctv
asked Sep 30 '13 at 7:49
silvernightstarsilvernightstar
211415
asked Sep 30 '13 at 7:49
silvernightstarsilvernightstar
211415
edited Sep 30 '13 at 8:03
silvernightstar
asked Sep 30 '13 at 7:49
silvernightstarsilvernightstar
211415
asked Sep 30 '13 at 7:49
silvernightstarsilvernightstar
211415
asked Sep 30 '13 at 7:49
silvernightstarsilvernightstar
211415
211415
You'll need to point a domain name to your IP address (assuming your home IP is static). This does raise concerns about security though which you will need to read up on.
– Dave
Sep 30 '13 at 8:15
Thanks, but I'm not sure if that would work. I'm already using DDNS to point a particular domain name to my public IP. And when I'm home, I'm still unable to access my IP camera using that domain name (and thus the need for the additional config of 192.168.1.2:8888 for local access).
– silvernightstar
Sep 30 '13 at 9:10
So, your public IP is pointing at your local computer yes?
– Dave
Sep 30 '13 at 9:21
1
Seems like it's an issue with your home router. I know some of those doesn't allow hairpin connections (connections from inside to the public interface of the router).
– Kent
Sep 30 '13 at 10:06
@DaveRook no, only public IP's port 8888 is being forwarded to 192.168.1.2:8888 (the IP camera)
– silvernightstar
Oct 1 '13 at 4:33
|
show 2 more comments
You'll need to point a domain name to your IP address (assuming your home IP is static). This does raise concerns about security though which you will need to read up on.
– Dave
Sep 30 '13 at 8:15
Thanks, but I'm not sure if that would work. I'm already using DDNS to point a particular domain name to my public IP. And when I'm home, I'm still unable to access my IP camera using that domain name (and thus the need for the additional config of 192.168.1.2:8888 for local access).
– silvernightstar
Sep 30 '13 at 9:10
So, your public IP is pointing at your local computer yes?
– Dave
Sep 30 '13 at 9:21
1
Seems like it's an issue with your home router. I know some of those doesn't allow hairpin connections (connections from inside to the public interface of the router).
– Kent
Sep 30 '13 at 10:06
@DaveRook no, only public IP's port 8888 is being forwarded to 192.168.1.2:8888 (the IP camera)
– silvernightstar
Oct 1 '13 at 4:33
You'll need to point a domain name to your IP address (assuming your home IP is static). This does raise concerns about security though which you will need to read up on.
– Dave
Sep 30 '13 at 8:15
You'll need to point a domain name to your IP address (assuming your home IP is static). This does raise concerns about security though which you will need to read up on.
– Dave
Sep 30 '13 at 8:15
Thanks, but I'm not sure if that would work. I'm already using DDNS to point a particular domain name to my public IP. And when I'm home, I'm still unable to access my IP camera using that domain name (and thus the need for the additional config of 192.168.1.2:8888 for local access).
– silvernightstar
Sep 30 '13 at 9:10
Thanks, but I'm not sure if that would work. I'm already using DDNS to point a particular domain name to my public IP. And when I'm home, I'm still unable to access my IP camera using that domain name (and thus the need for the additional config of 192.168.1.2:8888 for local access).
– silvernightstar
Sep 30 '13 at 9:10
So, your public IP is pointing at your local computer yes?
– Dave
Sep 30 '13 at 9:21
So, your public IP is pointing at your local computer yes?
– Dave
Sep 30 '13 at 9:21
1
1
Seems like it's an issue with your home router. I know some of those doesn't allow hairpin connections (connections from inside to the public interface of the router).
– Kent
Sep 30 '13 at 10:06
Seems like it's an issue with your home router. I know some of those doesn't allow hairpin connections (connections from inside to the public interface of the router).
– Kent
Sep 30 '13 at 10:06
@DaveRook no, only public IP's port 8888 is being forwarded to 192.168.1.2:8888 (the IP camera)
– silvernightstar
Oct 1 '13 at 4:33
@DaveRook no, only public IP's port 8888 is being forwarded to 192.168.1.2:8888 (the IP camera)
– silvernightstar
Oct 1 '13 at 4:33
|
show 2 more comments
3 Answers
3
active
oldest
votes
I had this same issue with not being able to access my IP camera from my inside private network using my public IP address. I have a Linksys router and found under the security settings internet NAT redirect filtering. Once I disabled this I can now just use my public IP address even while on the inside.
answered Apr 1 '14 at 0:56
EdwardEdward
1457
add a comment |
The only other way to do this is to have a separate dedicated outside IP address that is just for the camera. Computers on the LAN will see the current camera as on the same LAN, so you are using the internal IP address for the camera. Computers outside the LAN (i.e. over the internet) are seeing your modem's/router's IP address, which forwards just that port to the internal IP address.
What I did was simply to set it up in my camera software as if it were two separate cameras, one with the internal address & one with the external. Then it's just a matter of clicking on the right camera in the software (and easy to tell, as one shows an image & the other doesn't.)
answered Oct 1 '13 at 5:19
DebraDebra
3,85011021
add a comment |
You can accomplish by having a DNS server on your network. (sounds expensive but some routers have the DNS role on them).
Create an A record to match your DDNS record but to point to the internal IP instead. This way when you are inside your network the router will send your request to the DVR internal IP.
Ex:
DDNS Record. MyDVR.ddns.org points to 1.1.1.1 (my WAN IP)
Internal DNS Record. MyDVR,ddns.org points to 192.168.1.1 (My DVR LAN IP)
When connected everywhere on the internet. your MyDVR.ddns.org URL will resolve 1.1.1.1 so it will connect to your WAN IP and NAT will forward to your DVR.
When connected whiting your LAN. your MyDVR.ddns.org URL will resolve 192.168.1.1 So it will connect directly to your DVR.
Some router also allows to create firewall rules to route the traffic back to the DVR but in some instances this create a risk that can be exploited by pentesting software.
answered Jan 12 at 23:46
William QuevedoWilliam Quevedo
1
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f652191%2fhow-to-locally-within-lan-and-publicly-over-internet-access-an-ip-camera-usi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
I had this same issue with not being able to access my IP camera from my inside private network using my public IP address. I have a Linksys router and found under the security settings internet NAT redirect filtering. Once I disabled this I can now just use my public IP address even while on the inside.
answered Apr 1 '14 at 0:56
EdwardEdward
1457
add a comment |
I had this same issue with not being able to access my IP camera from my inside private network using my public IP address. I have a Linksys router and found under the security settings internet NAT redirect filtering. Once I disabled this I can now just use my public IP address even while on the inside.
answered Apr 1 '14 at 0:56
EdwardEdward
1457
add a comment |
I had this same issue with not being able to access my IP camera from my inside private network using my public IP address. I have a Linksys router and found under the security settings internet NAT redirect filtering. Once I disabled this I can now just use my public IP address even while on the inside.
answered Apr 1 '14 at 0:56
EdwardEdward
1457
I had this same issue with not being able to access my IP camera from my inside private network using my public IP address. I have a Linksys router and found under the security settings internet NAT redirect filtering. Once I disabled this I can now just use my public IP address even while on the inside.
answered Apr 1 '14 at 0:56
EdwardEdward
1457
answered Apr 1 '14 at 0:56
EdwardEdward
1457
answered Apr 1 '14 at 0:56
EdwardEdward
1457
answered Apr 1 '14 at 0:56
EdwardEdward
1457
1457
add a comment |
add a comment |
The only other way to do this is to have a separate dedicated outside IP address that is just for the camera. Computers on the LAN will see the current camera as on the same LAN, so you are using the internal IP address for the camera. Computers outside the LAN (i.e. over the internet) are seeing your modem's/router's IP address, which forwards just that port to the internal IP address.
What I did was simply to set it up in my camera software as if it were two separate cameras, one with the internal address & one with the external. Then it's just a matter of clicking on the right camera in the software (and easy to tell, as one shows an image & the other doesn't.)
answered Oct 1 '13 at 5:19
DebraDebra
3,85011021
add a comment |
The only other way to do this is to have a separate dedicated outside IP address that is just for the camera. Computers on the LAN will see the current camera as on the same LAN, so you are using the internal IP address for the camera. Computers outside the LAN (i.e. over the internet) are seeing your modem's/router's IP address, which forwards just that port to the internal IP address.
What I did was simply to set it up in my camera software as if it were two separate cameras, one with the internal address & one with the external. Then it's just a matter of clicking on the right camera in the software (and easy to tell, as one shows an image & the other doesn't.)
answered Oct 1 '13 at 5:19
DebraDebra
3,85011021
add a comment |
The only other way to do this is to have a separate dedicated outside IP address that is just for the camera. Computers on the LAN will see the current camera as on the same LAN, so you are using the internal IP address for the camera. Computers outside the LAN (i.e. over the internet) are seeing your modem's/router's IP address, which forwards just that port to the internal IP address.
What I did was simply to set it up in my camera software as if it were two separate cameras, one with the internal address & one with the external. Then it's just a matter of clicking on the right camera in the software (and easy to tell, as one shows an image & the other doesn't.)
answered Oct 1 '13 at 5:19
DebraDebra
3,85011021
The only other way to do this is to have a separate dedicated outside IP address that is just for the camera. Computers on the LAN will see the current camera as on the same LAN, so you are using the internal IP address for the camera. Computers outside the LAN (i.e. over the internet) are seeing your modem's/router's IP address, which forwards just that port to the internal IP address.
What I did was simply to set it up in my camera software as if it were two separate cameras, one with the internal address & one with the external. Then it's just a matter of clicking on the right camera in the software (and easy to tell, as one shows an image & the other doesn't.)
answered Oct 1 '13 at 5:19
DebraDebra
3,85011021
answered Oct 1 '13 at 5:19
DebraDebra
3,85011021
answered Oct 1 '13 at 5:19
DebraDebra
3,85011021
answered Oct 1 '13 at 5:19
DebraDebra
3,85011021
3,85011021
add a comment |
add a comment |
You can accomplish by having a DNS server on your network. (sounds expensive but some routers have the DNS role on them).
Create an A record to match your DDNS record but to point to the internal IP instead. This way when you are inside your network the router will send your request to the DVR internal IP.
Ex:
DDNS Record. MyDVR.ddns.org points to 1.1.1.1 (my WAN IP)
Internal DNS Record. MyDVR,ddns.org points to 192.168.1.1 (My DVR LAN IP)
When connected everywhere on the internet. your MyDVR.ddns.org URL will resolve 1.1.1.1 so it will connect to your WAN IP and NAT will forward to your DVR.
When connected whiting your LAN. your MyDVR.ddns.org URL will resolve 192.168.1.1 So it will connect directly to your DVR.
Some router also allows to create firewall rules to route the traffic back to the DVR but in some instances this create a risk that can be exploited by pentesting software.
answered Jan 12 at 23:46
William QuevedoWilliam Quevedo
1
add a comment |
You can accomplish by having a DNS server on your network. (sounds expensive but some routers have the DNS role on them).
Create an A record to match your DDNS record but to point to the internal IP instead. This way when you are inside your network the router will send your request to the DVR internal IP.
Ex:
DDNS Record. MyDVR.ddns.org points to 1.1.1.1 (my WAN IP)
Internal DNS Record. MyDVR,ddns.org points to 192.168.1.1 (My DVR LAN IP)
When connected everywhere on the internet. your MyDVR.ddns.org URL will resolve 1.1.1.1 so it will connect to your WAN IP and NAT will forward to your DVR.
When connected whiting your LAN. your MyDVR.ddns.org URL will resolve 192.168.1.1 So it will connect directly to your DVR.
Some router also allows to create firewall rules to route the traffic back to the DVR but in some instances this create a risk that can be exploited by pentesting software.
answered Jan 12 at 23:46
William QuevedoWilliam Quevedo
1
add a comment |
You can accomplish by having a DNS server on your network. (sounds expensive but some routers have the DNS role on them).
Create an A record to match your DDNS record but to point to the internal IP instead. This way when you are inside your network the router will send your request to the DVR internal IP.
Ex:
DDNS Record. MyDVR.ddns.org points to 1.1.1.1 (my WAN IP)
Internal DNS Record. MyDVR,ddns.org points to 192.168.1.1 (My DVR LAN IP)
When connected everywhere on the internet. your MyDVR.ddns.org URL will resolve 1.1.1.1 so it will connect to your WAN IP and NAT will forward to your DVR.
When connected whiting your LAN. your MyDVR.ddns.org URL will resolve 192.168.1.1 So it will connect directly to your DVR.
Some router also allows to create firewall rules to route the traffic back to the DVR but in some instances this create a risk that can be exploited by pentesting software.
answered Jan 12 at 23:46
William QuevedoWilliam Quevedo
1
You can accomplish by having a DNS server on your network. (sounds expensive but some routers have the DNS role on them).
Create an A record to match your DDNS record but to point to the internal IP instead. This way when you are inside your network the router will send your request to the DVR internal IP.
Ex:
DDNS Record. MyDVR.ddns.org points to 1.1.1.1 (my WAN IP)
Internal DNS Record. MyDVR,ddns.org points to 192.168.1.1 (My DVR LAN IP)
When connected everywhere on the internet. your MyDVR.ddns.org URL will resolve 1.1.1.1 so it will connect to your WAN IP and NAT will forward to your DVR.
When connected whiting your LAN. your MyDVR.ddns.org URL will resolve 192.168.1.1 So it will connect directly to your DVR.
Some router also allows to create firewall rules to route the traffic back to the DVR but in some instances this create a risk that can be exploited by pentesting software.
answered Jan 12 at 23:46
William QuevedoWilliam Quevedo
1
answered Jan 12 at 23:46
William QuevedoWilliam Quevedo
1
answered Jan 12 at 23:46
William QuevedoWilliam Quevedo
1
answered Jan 12 at 23:46
William QuevedoWilliam Quevedo
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f652191%2fhow-to-locally-within-lan-and-publicly-over-internet-access-an-ip-camera-usi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You'll need to point a domain name to your IP address (assuming your home IP is static). This does raise concerns about security though which you will need to read up on.
– Dave
Sep 30 '13 at 8:15
Thanks, but I'm not sure if that would work. I'm already using DDNS to point a particular domain name to my public IP. And when I'm home, I'm still unable to access my IP camera using that domain name (and thus the need for the additional config of 192.168.1.2:8888 for local access).
– silvernightstar
Sep 30 '13 at 9:10
So, your public IP is pointing at your local computer yes?
– Dave
Sep 30 '13 at 9:21
1
Seems like it's an issue with your home router. I know some of those doesn't allow hairpin connections (connections from inside to the public interface of the router).
– Kent
Sep 30 '13 at 10:06
@DaveRook no, only public IP's port 8888 is being forwarded to 192.168.1.2:8888 (the IP camera)
– silvernightstar
Oct 1 '13 at 4:33