I have 2 different IP cameras. When I use sign in to my NEW router I can see one cameras IP address there:
192.168.1.100
I also have another IP camera that I long time before found in ipconfig in cmd on the below address
192.168.1.4
I could then before enter only the 192.168.1.4 in chrome browser and it logged in to the IP Cameras settings page where I could change its port to 1024 so I now can enter in Chrome: 192.168.1.4:1024 so log in to the camera. However this IP camera 192.168.1.4 is not shown in the devices on my NEW router.
The problem is:
When I enter 192.168.1.100 in chrome, I only get a "Website can't be reached" I also can't find out what port this IP camera use. I have used WireShark and other port sniffer tools.
Any idéa of what to do in order to get to the cameras setting in chrome or get a connection with this camera. Finding out the port to 192.168.1.100 should be one factor I beleive?
(If I use "Onvif Device Manager" this software automatically find the camera and shows the feed which means that something is working. But it doesn't provide what http port that it is found on)
Related
I have a TD Vision DVR and can watch the video stream connected to DVR by android application XMEye.I want to watch video directly by using ip address of DVR in every where .
I can see the video in home network by using ip address
192.168.1.108 inside internet explorer .
I set the Port forwarding in my Zyxel modem from Port 80 to Port 80 .
But when I put the modem external IP inside the browser , the page for login appears and I enter the user and pass but there is a prompt that can not find the device.
What should I do to solve this problem?
I use tor proxy and i set the tunnel port to 192.168.1.2:9050.
I also set my router dhcp that give 192.168.1.2 to my pc
but my problem is that sometimes I use another router or my phone hotspot and they give my pc anothre ip (like 192.168.43.164/24) . I can't set their dhcp. so tor doesn't work.
Is there any way to always get the same ip ?
Or Is there any way to refer my wifi ip (something like localhost that refer to 127.0.0.1) to set in tor?
Your phone hotspot gives you a different DHCP's IP because it is threated as another network bridging one network (your PC) to another one (current network connected on your phone).
If you are using wireless hotspot and connecting to your phone's network on wi-fi, that is not possible because tethering IP that is provided for your phone router to use DHCP services is hardcoded in com.android.server.connectivity.Tethering, unless you have root access privileges.
And that it the reason to your phone routing service (USB Bridged or Wi-Fi Hostpot) gives you always an 192.168.42.X IP address.
If you are using Android, you can get more details in this thread on Android Enthusiasts in Stack Exchange:
https://android.stackexchange.com/questions/46499/how-configure-the-dhcp-settings-of-wifi-tethering-hotspot-on-android
If I connect a device via ethernet onto a switch, and do not receive an IP address via DHCP, how do I determine what the correct settings for that network should be, i.e. how do I choose a static IP address, subnet mask and gateway?
The specifics in my case are that I have an NVR with an 8 port POE switch that has 3 cameras plugged into it. I plugged my Windows 10 PC into the switch, expecting to be issued an IP address from the NVR via DHCP, but my PC was not given an IP. Perhaps the NVR assigns IPs via BOOTP? I want to get onto the network, probably by assigning a static IP that's not already used, then determine the IPs of the cameras so I can stream video from them directly using VLC.
Can I use tcpdump? There should be plenty of traffic from the cameras to the NVR.
how do I choose a static IP address, subnet mask and gateway?
The short answer - this should be done by your network administrator. If you are the network administrator - you should. But seems that you are connecting to the network you know nothing about.. Anyway here are some points that perhaps can help you.
There is a special thing called ARP Duplicate Address Detection (DAD). In Linux you can check if the particular IP is occupied in your broadcast segment with help of arping utility. From MAN page:
-D
Duplicate address detection mode (DAD). See RFC2131, 4.4.1.
Returns 0, if DAD succeeded i.e. no replies are received.
So if IP address is occupied you will see something like:
-bash-4.4# arping -D 10.0.99.99 -I eth0
ARPING 10.0.99.99 from 0.0.0.0 eth0
Unicast reply from 10.0.99.99 [DE:AD:BE:EF:00:8D] 1.274ms
Sent 1 probes (1 broadcast(s))
Received 1 response(s)
If this IP address is vacant, you'll see no responses. Read about ARP ping in Windows.
Also you can inspect the network through the tcpdump (to see some IP addressing info at least in broadcast packets), nmap and some other scanning utilities, but this topic is too broad (and at the same time it's well disclosed on the Internet). Btw you have to consider network architecture difficulties: vlan and so on.
I've logged in to my router's console to check a small internet problem.
And accidently noticed a strange ip connected to the wireless network which is 169.254.70.177 (the rest were all on the 192.168.1.0/24),
I looked that ip up on whois and got nothing, result was that 'this ip is unroutable'.
What does that mean ? and why possibly would be seeing this strange ip on my local network ?
This ip was appearing as connected to the router via wireless network, a few seconds later it appeared as connected via ethernet.
Can someone please explain what could this possibly happen ?
The 169.254.0.0/16 address range is the "zeroconf" range that many devices fall back to when no local address is configured and DHCP fails.
It's a link-local address, meaning that devices can only communicate within the local layer 2 segment. These addresses are not routed.
The device in question is probably set up for DHCP but failing that (filtered, exhausted pool, ...) has fallen back to zeroconf. Another possibility is a stray packet that the device has sent out on the wrong interface.
Using packet capturing, you should be able to find out the device's MAC address and be able to locate it.
The 192.168.X.X Ip's are the ones being assigned by your router, they are private network reserved addresses. The other address you see is probably your router's connection to the WAN
I have a box running OpenSuse with two local network segments:
192.168.2.0/24 (lan0)
192.168.33.0/24 (vlan0)
and 3rd connection,
DHCP (wan), used for Internet access.
and I'd like to be able to route everything (tcp, udp, icmp, whatever) in lan0 and vlan0 segments.
I have enabled ip forwarding and ip masquarading using YaST. I also added both 192.168.xx.0/24 to trusted networks in SuSEfirewall2 and set up explicit routing in FW_ROUTE setting. rp_filter is off for both.
I have internet access on both segments and i am able to ping in both directions (router - pc on the segment) but cannot ping from lan0's machine to vlan0's one. I get 'destination host unreachable' error whenever I try to ping from lan0 to vlan0.
My understanding is i am missing some major settings which would let router route packets from lan0 to vlan0 instead of masquarading them and sending to the Internet. Windows boxes at lan0/vlan0 do not see each other too :(
Any help would be greatly appreciated.
In case someone runs into same problem - it appeared that pings do not work for Windows 10 boxes only. Android phone pings fine so the root cause is not OpenSuse box at all.