impactrest.blogg.se - Lan network device discovery tool

LAN NETWORK DEVICE DISCOVERY TOOL INSTALL
LAN NETWORK DEVICE DISCOVERY TOOL SOFTWARE
LAN NETWORK DEVICE DISCOVERY TOOL PC
LAN NETWORK DEVICE DISCOVERY TOOL WINDOWS

You need to be able to quickly find where an endpoint is located when the intrusion prevention system indicates that the endpoint is trying to communicate with a known external malware site. A system may be in one location today and running on a different physical system tomorrow.

LAN NETWORK DEVICE DISCOVERY TOOL SOFTWARE

Software licensing mechanisms help, but it would still be nice to track these instances so you know the organization is compliant with vendor licensing requirements.ĭynamic workloads are also making network discovery more challenging. These systems are simply software packages running on an x86 platform. I found nc terminates cleanly in combination with a line-break (via the echo).The new world of virtual appliances has changed network device discovery and inventory needs. On the client side, we listen with nc until we get a payload. So we don't have to know which network we are on.

Sending it to 255.255.255.255 means broadcast to the whole subnet, regardless of size. The IP doesn't have to be got via ifconfig obviously, but its quite easy to parse. The script will send a UDP broadcast on Port 12001 and exit nc, after the payload (our echo command) + 2 seconds.

This only works if the "Farmers PC" and your "pole-mounted servers" are in the same subnet, though. The User/Farmer then only has to listen like this: echo | nc -ulp 12001Īnd after X minutes they should get something like this: This is my IP: 192.168.1.121 # replace eth0 with the name of your interface or get the IP via other means With netcat you could do something like a cronjob on your "pole-mounted servers" that does something like this every X minutes: #!/bin/bash Whenever I have problems sshing to the server, I execute a small script that, by a combination of ping and ssh (within a loop of IPs), and checking on the response, can get the current IP.ĭepending on many aspects of your network configuration this may work for you or not. If that is your target please mention it.Ī server that I am accessing remotely changes IP once in a while, since it is assigned by DHCP. If you could give more information on the current configuration, that will narrow the problem.

LAN NETWORK DEVICE DISCOVERY TOOL PC

If correctly configured, they should not "forget the PC IP address". The right mechanisms depend very much on what are you willing to operate, how are you accessing the servers.

LAN NETWORK DEVICE DISCOVERY TOOL WINDOWS

You will of course have time windows of "network-blindness", depending on the frequency set in crontab.Īlternatively, a crontab task could broadcast/send email/etc. You could set a crontab task that checks the current IP, and whenever it deviates from a set value, it changes the IP back to the target. Instead of getting a way to know the new IP, you could have the servers recover the old IP to a fixed value.

Access to the servers that currently have the problem, to implement solution 1.

Generate a method to avoid the problem in future cases.

I want something exactly like those program but with bash commands.Īs I understand, you have two different problems: If you have worked with Device Discovery tool (DDT) for IP Cameras you know that they will find the camera IP independent of the PC which has the DDT on it. I want something like this : echo "What is your IP Address ? " | nc -w1 -u 4545Īnd I put something on the PC which answers to this message whenever they got the exact phrase What is your IP Address ? " nc -l -u -p 4545īut for the nc I have to specify a network range which is not possible for me. Is there any tool like "NC" in Linux which can help me to write a bash script to find their IP ? I have network access to the PC but I cannot connect a Monitor to the PC so the only way is to find the IP using the local network. but after some search I realized I have to know the range at least for example (172.16.12.X or 10.10.200.X) which is not possible for me because the farmers forgot the network range too.

I thought maybe using Broadcast IP address and sending a message over local network might help to solve this problem. The problem is that after a while they forget the PC IP Address and we want to give them a tool to detect and show them the current IP Address. Sometimes they change the range of these PCs IP address from original one to their own desired IP Range.įor example I ship them with 192.168.10.10/24 but they might change it to something like 172.16.12.19/29 or 10.10.200.10/8 or.

LAN NETWORK DEVICE DISCOVERY TOOL INSTALL

( they install it on a pole 6 or 7 meters above ground level and it is very hard to access) I have an embedded PC running Linux server and a simple web server which is used in agriculture industry, my customers buy these PCs and use them in their fields.