--- title: "Debugging - icom OS Routers" slug: "debugging-en" updated: 2024-09-25T15:38:10Z published: 2024-09-25T15:38:10Z canonical: "docs.insys-icom.com/debugging-en" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.insys-icom.com/llms.txt > Use this file to discover all available pages before exploring further. # Debugging - icom OS Routers The router provides some useful troubleshooting tools in the *Administration* → *Debugging* menu. A click on OPEN DEBUG TOOLS permits to select the appropriate debug tool. ## Ping The *Tool* PING is a diagnosis tool for testing the reachability of a certain host in an IPv4 network. The host is entered in form of an IP address or a domain name as *Parameter*. A click on SEND executes the command immediately and outputs the response. Example for a ping to the host insys-icom.com: ```plaintext PING insys-icom.com (172.67.1.194) 56(84) bytes of data. 64 bytes from 172.67.1.194 (172.67.1.194): icmp_seq=1 ttl=58 time=8.36 ms --- insys-icom.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 8.363/8.363/8.363/0.000 ms ``` The *Tool* PING6 is a diagnosis tool for testing the reachability of a certain host in IPv6 network. The host is entered in form of an IP address or a domain name as *Parameter*. A click on SEND executes the command immediately and outputs the response. Example for a ping6 to the host insys-icom.com: ```plaintext PING insys-icom.com(2606:4700:10::ac43:1c2 (2606:4700:10::ac43:1c2)) 56 data bytes 64 bytes from 2606:4700:10::ac43:1c2 (2606:4700:10::ac43:1c2): icmp_seq=1 ttl=59 time=29.10 ms --- insys-icom.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 29.982/29.982/29.982/0.000 ms ``` ## Traceroute The *Tool* TRACEROUTE is a routine that displays the routers and Internet nodes over which IPv4 data packets get to the queried host. The host is entered in form of an IP address or a domain name as *Parameter*. A click on SEND executes the command immediately and outputs the response. Example for Traceroute to the host insys-icom.com: ```plaintext traceroute to insys-icom.com (104.20.13.95), 3 hops max, 38 byte packets 1 192.168.200.2 (192.168.200.2) 0.436 ms 0.266 ms 0.274 ms 2 hsir1.rz1.r-kom.net (95.130.160.1) 3.124 ms 3.491 ms 1.726 ms 3 cr1-be4.rz1.r-kom.net (212.77.160.81) 1.488 ms 3.324 ms 1.605 ms ``` The *Tool* TRACEROUTE6 is a routine that displays the routers and Internet nodes over which IPv6 data packets get to the queried host. The host is entered in form of an IP address or a domain name as *Parameter*. A click on SEND executes the command immediately and outputs the response. Example for Traceroute to the host insys-icom.com: ```plaintext traceroute to insys-icom.com (2606:4700:10::6814:e5f), 3 hops max, 64 byte packets 1 p200300e1270f56010000000000000001.dip0.t-ipconnect.de (2003:e1:270f:5601::1) 1.092 ms 0.448 ms 0.345 ms 2 2003:0:8803:5800::1 (2003:0:8803:5800::1) 17.421 ms 17.569 ms 17.051 ms 3 2003:0:1203:8015::2 (2003:0:1203:8015::2) 30.157 ms 29.923 ms 34.580 ms ``` ## DNS lookup The *Tool* DNS LOOKUP is a routine for querying an entry from a domain name system server. It is usually used to determine the IP address for a certain domain name. The domain name is handed over as *Parameter* here. A click on SEND executes the command immediately and outputs the response. Example for a DNS lookup for the domain name insys-icom.com: ```plaintext 14:08:55.468410 ec:b1:d7:13:1e:82 > 09:00:09:09:13:a6, ethertype Unknown (0x88b7), length 66: 0x0000: 00ca 62a9 0000 ecb1 d713 1e80 8648 fd4b ..b..........H.K 0x0010: a667 5c83 4176 1df8 7b20 8aca 77f4 5519 .g\.Av..{...w.U. 0x0020: 0800 0900 0302 0000 0000 0000 0000 0000 ................ 0x0030: 8deb ace3 .... 14:08:55.607495 ARP, Request who-has 192.168.200.143 tell 192.168.201.226, length 46 14:08:55.677773 ARP, Request who-has 192.168.200.114 tell 192.168.200.111, length 46 14:08:55.874924 ARP, Request who-has 192.168.201.111 tell 192.168.201.29, length 46 ``` ## tcpdump The *Tool* TCPDUMP permits to record network traffic. The *Parameters* to be handed over are described in detail under [www.tcpdump.org](https://www.tcpdump.org). A click on SEND starts the recording. The recording is stopped after a click on *Stop* and the recorded network traffic is displayed. The last recording can be downloaded from the router with a click on *TCPDUMP recording* after the recording. Example for the recording of the network traffic on the router interface **IP net 3** (net3) using `-i net3` as parameter: ```plaintext Example for the recording of the network traffic on the router interface IP net 3 (net3) using -i net3 as parameter: 14:08:55.468410 ec:b1:d7:13:1e:82 > 09:00:09:09:13:a6, ethertype Unknown (0x88b7), length 66: 0x0000: 00ca 62a9 0000 ecb1 d713 1e80 8648 fd4b ..b..........H.K 0x0010: a667 5c83 4176 1df8 7b20 8aca 77f4 5519 .g\.Av..{...w.U. 0x0020: 0800 0900 0302 0000 0000 0000 0000 0000 ................ 0x0030: 8deb ace3 .... 14:08:55.607495 ARP, Request who-has 192.168.200.143 tell 192.168.201.226, length 46 14:08:55.677773 ARP, Request who-has 192.168.200.114 tell 192.168.200.111, length 46 14:08:55.874924 ARP, Request who-has 192.168.201.111 tell 192.168.201.29, length 46 ``` The recording can be restricted further to increase clarity: Only record packets with a certain protocol, here TCP: `-i net3 tcp` Only record packets with a certain protocol and port, here TCP on port 502 (only Modbus): `-i net3 tcp port 502` Record all packets except a certain protocol and port, here UDP on port 1194 (everything except OpenVPN): `-i net3 not udp port 1194` Record all packets from and to a certain IP address: `-i net3 host 192.168.100.35` ## AT command The *Tool* AT command may **only** be used upon consultation with the Technical Support of INSYS icom and permits to transmit AT commands to the selected *Interface*. The command is handed over as *Parameter* here. A click on SEND executes the command immediately and outputs the response. An improper use of this function may affect the function of the router beyond a reset! ## Port mirroring The *Tool* Port mirroring is only available in the [classic web interface](/kb/docs/en/new-and-classic-user-interface-en) and permits to mirror the data traffic on the *Source port* to the *Destination port* (sniffer port). The data traffic can then be read on the destination port for analysis purposes. The term *port* does not only refer to Ethernet ports here. it is also possible to select router interfaces as a *port*.