Why is my D-Link IP webcam unreachable from within the LAN, but accessible from outside?
I recently bought a D-Link DCS-930L network webcam which is connected to my WLAN network. It retrieves a IP address via DHCP from DD-WRT based router (a TP-Link TL-WR1043ND), and it is listed under "Active wireless nodes".
The camera is registered to a webservice called "My DLink", which enables the user to access the webcam from the internet (via their webpage or via smartphone apps). This service works, and I can access the camera from outside.
However, when I try to connect from inside my (W)LAN, it says "No route to host". How is that possible?
--
EDIT: I found the answer by myself accidentally by skimming through the IP webcam settings. It turned out that the option Setup > Network Setup > UPnP Port Forwarding was set to Enable. I don't use UPnP in my LAN, and it is disabled on my router.
I don't understand how the enabled UPnP on the webcam could cause troubles, when there were no other devices supporting UPnP. Has anybody an explanation for this?
networking wireless-networking router dd-wrt upnp
asked Feb 2 '14 at 13:38
abaumgabaumg
17817
|
show 1 more comment
I recently bought a D-Link DCS-930L network webcam which is connected to my WLAN network. It retrieves a IP address via DHCP from DD-WRT based router (a TP-Link TL-WR1043ND), and it is listed under "Active wireless nodes".
The camera is registered to a webservice called "My DLink", which enables the user to access the webcam from the internet (via their webpage or via smartphone apps). This service works, and I can access the camera from outside.
However, when I try to connect from inside my (W)LAN, it says "No route to host". How is that possible?
--
EDIT: I found the answer by myself accidentally by skimming through the IP webcam settings. It turned out that the option Setup > Network Setup > UPnP Port Forwarding was set to Enable. I don't use UPnP in my LAN, and it is disabled on my router.
I don't understand how the enabled UPnP on the webcam could cause troubles, when there were no other devices supporting UPnP. Has anybody an explanation for this?
networking wireless-networking router dd-wrt upnp
asked Feb 2 '14 at 13:38
abaumgabaumg
17817
No route to host is a reply from your router, not the Webcam itself. Can you ping the IP address? Can you scan it with nmap? Does it appear as one of the DHCP clients in your DD-WRT router page (under Status -> LAN, active clients)?
– MariusMatutiae
Feb 2 '14 at 13:51
No, I can't ping it, but it does appear as well as DHCP client as WLAN client.imac:~ andreas$ ping 192.168.1.30 PING 192.168.1.30 (192.168.1.30): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 Request timeout for icmp_seq 4 ^C --- 192.168.1.30 ping statistics --- 6 packets transmitted, 0 packets received, 100.0% packet loss
– abaumg
Feb 2 '14 at 13:54
I can however ssh into my router and ping it successfully from there:root@lonkero:~# ping 192.168.1.30 PING 192.168.1.30 (192.168.1.30): 56 data bytes 64 bytes from 192.168.1.30: seq=0 ttl=64 time=1.592 ms 64 bytes from 192.168.1.30: seq=1 ttl=64 time=1.658 ms 64 bytes from 192.168.1.30: seq=2 ttl=64 time=2.857 ms 64 bytes from 192.168.1.30: seq=3 ttl=64 time=1.645 ms --- 192.168.1.30 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 1.592/1.938/2.857 ms
– abaumg
Feb 2 '14 at 13:55
Can you post your routing table?
– MariusMatutiae
Feb 2 '14 at 14:06
192.168.100.1 * 255.255.255.255 UH 0 0 0 ppp0 10.100.10.2 * 255.255.255.255 UH 0 0 0 tun0 192.168.1.0 * 255.255.255.0 U 0 0 0 br0 10.100.10.0 10.100.10.2 255.255.255.0 UG 0 0 0 tun0 169.254.0.0 * 255.255.0.0 U 0 0 0 br0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default 192.168.100.1 0.0.0.0 UG 0 0 0 ppp0
– abaumg
Feb 2 '14 at 14:13
|
show 1 more comment
I recently bought a D-Link DCS-930L network webcam which is connected to my WLAN network. It retrieves a IP address via DHCP from DD-WRT based router (a TP-Link TL-WR1043ND), and it is listed under "Active wireless nodes".
The camera is registered to a webservice called "My DLink", which enables the user to access the webcam from the internet (via their webpage or via smartphone apps). This service works, and I can access the camera from outside.
However, when I try to connect from inside my (W)LAN, it says "No route to host". How is that possible?
--
EDIT: I found the answer by myself accidentally by skimming through the IP webcam settings. It turned out that the option Setup > Network Setup > UPnP Port Forwarding was set to Enable. I don't use UPnP in my LAN, and it is disabled on my router.
I don't understand how the enabled UPnP on the webcam could cause troubles, when there were no other devices supporting UPnP. Has anybody an explanation for this?
networking wireless-networking router dd-wrt upnp
asked Feb 2 '14 at 13:38
abaumgabaumg
17817
I recently bought a D-Link DCS-930L network webcam which is connected to my WLAN network. It retrieves a IP address via DHCP from DD-WRT based router (a TP-Link TL-WR1043ND), and it is listed under "Active wireless nodes".
The camera is registered to a webservice called "My DLink", which enables the user to access the webcam from the internet (via their webpage or via smartphone apps). This service works, and I can access the camera from outside.
However, when I try to connect from inside my (W)LAN, it says "No route to host". How is that possible?
--
EDIT: I found the answer by myself accidentally by skimming through the IP webcam settings. It turned out that the option Setup > Network Setup > UPnP Port Forwarding was set to Enable. I don't use UPnP in my LAN, and it is disabled on my router.
I don't understand how the enabled UPnP on the webcam could cause troubles, when there were no other devices supporting UPnP. Has anybody an explanation for this?
networking wireless-networking router dd-wrt upnp
networking wireless-networking router dd-wrt upnp
asked Feb 2 '14 at 13:38
abaumgabaumg
17817
asked Feb 2 '14 at 13:38
abaumgabaumg
17817
edited Feb 3 '14 at 22:58
abaumg
asked Feb 2 '14 at 13:38
abaumgabaumg
17817
asked Feb 2 '14 at 13:38
abaumgabaumg
17817
asked Feb 2 '14 at 13:38
abaumgabaumg
17817
17817
No route to host is a reply from your router, not the Webcam itself. Can you ping the IP address? Can you scan it with nmap? Does it appear as one of the DHCP clients in your DD-WRT router page (under Status -> LAN, active clients)?
– MariusMatutiae
Feb 2 '14 at 13:51
No, I can't ping it, but it does appear as well as DHCP client as WLAN client.imac:~ andreas$ ping 192.168.1.30 PING 192.168.1.30 (192.168.1.30): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 Request timeout for icmp_seq 4 ^C --- 192.168.1.30 ping statistics --- 6 packets transmitted, 0 packets received, 100.0% packet loss
– abaumg
Feb 2 '14 at 13:54
I can however ssh into my router and ping it successfully from there:root@lonkero:~# ping 192.168.1.30 PING 192.168.1.30 (192.168.1.30): 56 data bytes 64 bytes from 192.168.1.30: seq=0 ttl=64 time=1.592 ms 64 bytes from 192.168.1.30: seq=1 ttl=64 time=1.658 ms 64 bytes from 192.168.1.30: seq=2 ttl=64 time=2.857 ms 64 bytes from 192.168.1.30: seq=3 ttl=64 time=1.645 ms --- 192.168.1.30 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 1.592/1.938/2.857 ms
– abaumg
Feb 2 '14 at 13:55
Can you post your routing table?
– MariusMatutiae
Feb 2 '14 at 14:06
192.168.100.1 * 255.255.255.255 UH 0 0 0 ppp0 10.100.10.2 * 255.255.255.255 UH 0 0 0 tun0 192.168.1.0 * 255.255.255.0 U 0 0 0 br0 10.100.10.0 10.100.10.2 255.255.255.0 UG 0 0 0 tun0 169.254.0.0 * 255.255.0.0 U 0 0 0 br0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default 192.168.100.1 0.0.0.0 UG 0 0 0 ppp0
– abaumg
Feb 2 '14 at 14:13
|
show 1 more comment
No route to host is a reply from your router, not the Webcam itself. Can you ping the IP address? Can you scan it with nmap? Does it appear as one of the DHCP clients in your DD-WRT router page (under Status -> LAN, active clients)?
– MariusMatutiae
Feb 2 '14 at 13:51
No, I can't ping it, but it does appear as well as DHCP client as WLAN client.imac:~ andreas$ ping 192.168.1.30 PING 192.168.1.30 (192.168.1.30): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 Request timeout for icmp_seq 4 ^C --- 192.168.1.30 ping statistics --- 6 packets transmitted, 0 packets received, 100.0% packet loss
– abaumg
Feb 2 '14 at 13:54
I can however ssh into my router and ping it successfully from there:root@lonkero:~# ping 192.168.1.30 PING 192.168.1.30 (192.168.1.30): 56 data bytes 64 bytes from 192.168.1.30: seq=0 ttl=64 time=1.592 ms 64 bytes from 192.168.1.30: seq=1 ttl=64 time=1.658 ms 64 bytes from 192.168.1.30: seq=2 ttl=64 time=2.857 ms 64 bytes from 192.168.1.30: seq=3 ttl=64 time=1.645 ms --- 192.168.1.30 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 1.592/1.938/2.857 ms
– abaumg
Feb 2 '14 at 13:55
Can you post your routing table?
– MariusMatutiae
Feb 2 '14 at 14:06
192.168.100.1 * 255.255.255.255 UH 0 0 0 ppp0 10.100.10.2 * 255.255.255.255 UH 0 0 0 tun0 192.168.1.0 * 255.255.255.0 U 0 0 0 br0 10.100.10.0 10.100.10.2 255.255.255.0 UG 0 0 0 tun0 169.254.0.0 * 255.255.0.0 U 0 0 0 br0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default 192.168.100.1 0.0.0.0 UG 0 0 0 ppp0
– abaumg
Feb 2 '14 at 14:13
No route to host is a reply from your router, not the Webcam itself. Can you ping the IP address? Can you scan it with nmap? Does it appear as one of the DHCP clients in your DD-WRT router page (under Status -> LAN, active clients)?
– MariusMatutiae
Feb 2 '14 at 13:51
No route to host is a reply from your router, not the Webcam itself. Can you ping the IP address? Can you scan it with nmap? Does it appear as one of the DHCP clients in your DD-WRT router page (under Status -> LAN, active clients)?
– MariusMatutiae
Feb 2 '14 at 13:51
No, I can't ping it, but it does appear as well as DHCP client as WLAN client.
imac:~ andreas$ ping 192.168.1.30 PING 192.168.1.30 (192.168.1.30): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 Request timeout for icmp_seq 4 ^C --- 192.168.1.30 ping statistics --- 6 packets transmitted, 0 packets received, 100.0% packet loss– abaumg
Feb 2 '14 at 13:54
No, I can't ping it, but it does appear as well as DHCP client as WLAN client.
imac:~ andreas$ ping 192.168.1.30 PING 192.168.1.30 (192.168.1.30): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 Request timeout for icmp_seq 4 ^C --- 192.168.1.30 ping statistics --- 6 packets transmitted, 0 packets received, 100.0% packet loss– abaumg
Feb 2 '14 at 13:54
I can however ssh into my router and ping it successfully from there:
root@lonkero:~# ping 192.168.1.30 PING 192.168.1.30 (192.168.1.30): 56 data bytes 64 bytes from 192.168.1.30: seq=0 ttl=64 time=1.592 ms 64 bytes from 192.168.1.30: seq=1 ttl=64 time=1.658 ms 64 bytes from 192.168.1.30: seq=2 ttl=64 time=2.857 ms 64 bytes from 192.168.1.30: seq=3 ttl=64 time=1.645 ms --- 192.168.1.30 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 1.592/1.938/2.857 ms– abaumg
Feb 2 '14 at 13:55
I can however ssh into my router and ping it successfully from there:
root@lonkero:~# ping 192.168.1.30 PING 192.168.1.30 (192.168.1.30): 56 data bytes 64 bytes from 192.168.1.30: seq=0 ttl=64 time=1.592 ms 64 bytes from 192.168.1.30: seq=1 ttl=64 time=1.658 ms 64 bytes from 192.168.1.30: seq=2 ttl=64 time=2.857 ms 64 bytes from 192.168.1.30: seq=3 ttl=64 time=1.645 ms --- 192.168.1.30 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 1.592/1.938/2.857 ms– abaumg
Feb 2 '14 at 13:55
Can you post your routing table?
– MariusMatutiae
Feb 2 '14 at 14:06
Can you post your routing table?
– MariusMatutiae
Feb 2 '14 at 14:06
192.168.100.1 * 255.255.255.255 UH 0 0 0 ppp0 10.100.10.2 * 255.255.255.255 UH 0 0 0 tun0 192.168.1.0 * 255.255.255.0 U 0 0 0 br0 10.100.10.0 10.100.10.2 255.255.255.0 UG 0 0 0 tun0 169.254.0.0 * 255.255.0.0 U 0 0 0 br0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default 192.168.100.1 0.0.0.0 UG 0 0 0 ppp0– abaumg
Feb 2 '14 at 14:13
192.168.100.1 * 255.255.255.255 UH 0 0 0 ppp0 10.100.10.2 * 255.255.255.255 UH 0 0 0 tun0 192.168.1.0 * 255.255.255.0 U 0 0 0 br0 10.100.10.0 10.100.10.2 255.255.255.0 UG 0 0 0 tun0 169.254.0.0 * 255.255.0.0 U 0 0 0 br0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default 192.168.100.1 0.0.0.0 UG 0 0 0 ppp0– abaumg
Feb 2 '14 at 14:13
|
show 1 more comment
2 Answers
2
active
oldest
votes
Most of all, you have a very confused routing table. You may wish to erase all of your routes, and let eth0 acquire a new address via DHCP: Then I bet you will see your camera. In other words: I believe the problem lies with your routing table, not with your camera.
Try the follwoing: as sudo,
service network-manager stop
ifconfig br0 down
brctl delbr br0
ifconfig eth0 down
ifconfig eth0 up
dhclient eth0
ping -c3 192.168.1.30
I think it will work now. In any case, all of the changes above disappear upon reboot.
answered Feb 2 '14 at 14:25
MariusMatutiaeMariusMatutiae
38.5k953100
add a comment |
It's possible that you turned on ap isolation in the basic wireless settings of dd-wrt.
answered Feb 2 '14 at 14:35
user295510user295510
1
AP Isolation is disabled.
– abaumg
Feb 2 '14 at 21:43
What range of ip addresses do you have assigned to your vpn and dhcp pools?
– user295510
Feb 3 '14 at 14:24
Also, what is the ip of the machine that is failing to ping the webcam?
– user295510
Feb 3 '14 at 14:44
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%2f710354%2fwhy-is-my-d-link-ip-webcam-unreachable-from-within-the-lan-but-accessible-from%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Most of all, you have a very confused routing table. You may wish to erase all of your routes, and let eth0 acquire a new address via DHCP: Then I bet you will see your camera. In other words: I believe the problem lies with your routing table, not with your camera.
Try the follwoing: as sudo,
service network-manager stop
ifconfig br0 down
brctl delbr br0
ifconfig eth0 down
ifconfig eth0 up
dhclient eth0
ping -c3 192.168.1.30
I think it will work now. In any case, all of the changes above disappear upon reboot.
answered Feb 2 '14 at 14:25
MariusMatutiaeMariusMatutiae
38.5k953100
add a comment |
Most of all, you have a very confused routing table. You may wish to erase all of your routes, and let eth0 acquire a new address via DHCP: Then I bet you will see your camera. In other words: I believe the problem lies with your routing table, not with your camera.
Try the follwoing: as sudo,
service network-manager stop
ifconfig br0 down
brctl delbr br0
ifconfig eth0 down
ifconfig eth0 up
dhclient eth0
ping -c3 192.168.1.30
I think it will work now. In any case, all of the changes above disappear upon reboot.
answered Feb 2 '14 at 14:25
MariusMatutiaeMariusMatutiae
38.5k953100
add a comment |
Most of all, you have a very confused routing table. You may wish to erase all of your routes, and let eth0 acquire a new address via DHCP: Then I bet you will see your camera. In other words: I believe the problem lies with your routing table, not with your camera.
Try the follwoing: as sudo,
service network-manager stop
ifconfig br0 down
brctl delbr br0
ifconfig eth0 down
ifconfig eth0 up
dhclient eth0
ping -c3 192.168.1.30
I think it will work now. In any case, all of the changes above disappear upon reboot.
answered Feb 2 '14 at 14:25
MariusMatutiaeMariusMatutiae
38.5k953100
Most of all, you have a very confused routing table. You may wish to erase all of your routes, and let eth0 acquire a new address via DHCP: Then I bet you will see your camera. In other words: I believe the problem lies with your routing table, not with your camera.
Try the follwoing: as sudo,
service network-manager stop
ifconfig br0 down
brctl delbr br0
ifconfig eth0 down
ifconfig eth0 up
dhclient eth0
ping -c3 192.168.1.30
I think it will work now. In any case, all of the changes above disappear upon reboot.
answered Feb 2 '14 at 14:25
MariusMatutiaeMariusMatutiae
38.5k953100
answered Feb 2 '14 at 14:25
MariusMatutiaeMariusMatutiae
38.5k953100
answered Feb 2 '14 at 14:25
MariusMatutiaeMariusMatutiae
38.5k953100
answered Feb 2 '14 at 14:25
MariusMatutiaeMariusMatutiae
38.5k953100
38.5k953100
add a comment |
add a comment |
It's possible that you turned on ap isolation in the basic wireless settings of dd-wrt.
answered Feb 2 '14 at 14:35
user295510user295510
1
AP Isolation is disabled.
– abaumg
Feb 2 '14 at 21:43
What range of ip addresses do you have assigned to your vpn and dhcp pools?
– user295510
Feb 3 '14 at 14:24
Also, what is the ip of the machine that is failing to ping the webcam?
– user295510
Feb 3 '14 at 14:44
add a comment |
It's possible that you turned on ap isolation in the basic wireless settings of dd-wrt.
answered Feb 2 '14 at 14:35
user295510user295510
1
AP Isolation is disabled.
– abaumg
Feb 2 '14 at 21:43
What range of ip addresses do you have assigned to your vpn and dhcp pools?
– user295510
Feb 3 '14 at 14:24
Also, what is the ip of the machine that is failing to ping the webcam?
– user295510
Feb 3 '14 at 14:44
add a comment |
It's possible that you turned on ap isolation in the basic wireless settings of dd-wrt.
answered Feb 2 '14 at 14:35
user295510user295510
1
It's possible that you turned on ap isolation in the basic wireless settings of dd-wrt.
answered Feb 2 '14 at 14:35
user295510user295510
1
answered Feb 2 '14 at 14:35
user295510user295510
1
answered Feb 2 '14 at 14:35
user295510user295510
1
answered Feb 2 '14 at 14:35
user295510user295510
1
1
AP Isolation is disabled.
– abaumg
Feb 2 '14 at 21:43
What range of ip addresses do you have assigned to your vpn and dhcp pools?
– user295510
Feb 3 '14 at 14:24
Also, what is the ip of the machine that is failing to ping the webcam?
– user295510
Feb 3 '14 at 14:44
add a comment |
AP Isolation is disabled.
– abaumg
Feb 2 '14 at 21:43
What range of ip addresses do you have assigned to your vpn and dhcp pools?
– user295510
Feb 3 '14 at 14:24
Also, what is the ip of the machine that is failing to ping the webcam?
– user295510
Feb 3 '14 at 14:44
AP Isolation is disabled.
– abaumg
Feb 2 '14 at 21:43
AP Isolation is disabled.
– abaumg
Feb 2 '14 at 21:43
What range of ip addresses do you have assigned to your vpn and dhcp pools?
– user295510
Feb 3 '14 at 14:24
What range of ip addresses do you have assigned to your vpn and dhcp pools?
– user295510
Feb 3 '14 at 14:24
Also, what is the ip of the machine that is failing to ping the webcam?
– user295510
Feb 3 '14 at 14:44
Also, what is the ip of the machine that is failing to ping the webcam?
– user295510
Feb 3 '14 at 14:44
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%2f710354%2fwhy-is-my-d-link-ip-webcam-unreachable-from-within-the-lan-but-accessible-from%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
No route to host is a reply from your router, not the Webcam itself. Can you ping the IP address? Can you scan it with nmap? Does it appear as one of the DHCP clients in your DD-WRT router page (under Status -> LAN, active clients)?
– MariusMatutiae
Feb 2 '14 at 13:51
No, I can't ping it, but it does appear as well as DHCP client as WLAN client.
imac:~ andreas$ ping 192.168.1.30 PING 192.168.1.30 (192.168.1.30): 56 data bytes Request timeout for icmp_seq 0 Request timeout for icmp_seq 1 Request timeout for icmp_seq 2 Request timeout for icmp_seq 3 Request timeout for icmp_seq 4 ^C --- 192.168.1.30 ping statistics --- 6 packets transmitted, 0 packets received, 100.0% packet loss– abaumg
Feb 2 '14 at 13:54
I can however ssh into my router and ping it successfully from there:
root@lonkero:~# ping 192.168.1.30 PING 192.168.1.30 (192.168.1.30): 56 data bytes 64 bytes from 192.168.1.30: seq=0 ttl=64 time=1.592 ms 64 bytes from 192.168.1.30: seq=1 ttl=64 time=1.658 ms 64 bytes from 192.168.1.30: seq=2 ttl=64 time=2.857 ms 64 bytes from 192.168.1.30: seq=3 ttl=64 time=1.645 ms --- 192.168.1.30 ping statistics --- 4 packets transmitted, 4 packets received, 0% packet loss round-trip min/avg/max = 1.592/1.938/2.857 ms– abaumg
Feb 2 '14 at 13:55
Can you post your routing table?
– MariusMatutiae
Feb 2 '14 at 14:06
192.168.100.1 * 255.255.255.255 UH 0 0 0 ppp0 10.100.10.2 * 255.255.255.255 UH 0 0 0 tun0 192.168.1.0 * 255.255.255.0 U 0 0 0 br0 10.100.10.0 10.100.10.2 255.255.255.0 UG 0 0 0 tun0 169.254.0.0 * 255.255.0.0 U 0 0 0 br0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo default 192.168.100.1 0.0.0.0 UG 0 0 0 ppp0– abaumg
Feb 2 '14 at 14:13