# `mix ads.info`
[🔗](https://github.com/tallakt/yaads/blob/v0.1.0/lib/mix/tasks/ads.info.ex#L1)

Finds the PLCs on the network, as `mix ads.route` does, and shows what one's system service
answers: its version and state, its host name and its network adapters. It answers only to a
machine it has a route for, which `mix ads.route` adds.

    $ mix ads.info 10.0.0.5
    CX-1234AB (10.0.0.5), 5.36.69.176.1.1

      TwinCAT System 3.1.4026, in run
      Host name  CX-1234AB

      Adapter                                       MAC                DHCP  Addresses
      TwinCAT-Intel PCI Ethernet Adapter (Gigabit)  00:01:05:76:34:AE  no    10.0.0.5/24
                                                                             gateway 10.0.0.1

`--resolve` looks a host name up on the PLC, with its DNS and hosts file, as often as given:

    $ mix ads.info 10.0.0.5 --resolve scada-1 --resolve nowhere.invalid
      scada-1          10.0.0.7
      nowhere.invalid  not found

## Options

  * `--state`, `--host-name`, `--adapters` - show only these; all three if none is given, nor
    `--resolve`
  * `--resolve NAME` - the address the PLC finds for a host name
  * `--net-id` - this machine's NetId, as the PLC's route has it, if not its address with `.1.1`
  * `--search` - where to search, a broadcast address or a PLC's, as often as needed (default
    every network this machine is on)
  * `--yes`, `-y` - take the only PLC that answers without asking
  * `--codepage` - of the PLC's strings, such as `windows-1251`, if not Windows-1252 (see
    `ADS.Codepage`)
  * `--timeout` - how long to wait for answers over UDP, in ms (default 2000 for the search,
    5000 otherwise)
  * `--tcp-port`, `--udp-port` - if not 48898 and 48899

---

*Consult [api-reference.md](api-reference.md) for complete listing*