Telnet; Ip Router And Ip Interface - Jung IPR 300 SREG Product Documentation

7

Telnet

Telnet is a common network protocol based on a TCP connection between a Telnet server (the device in this
case) and a client (the commissioning PC in this case).
For communication to be possible, it is necessary for the device to be administered in the network and to
be reached by the commissioning PC via IP. Settings can then be made on the device (particularly status
information) via Telnet as well as status information viewed without there being a connection to the ETS.
Telnet can either be activated as a function of the Windows operating system or used via a third party
program, e.g. PuTTY.
Telnet access is factory-protected with the password "knxsecure".
Once the device is in secure mode, the telnet interface is disabled.

7.1 IP router and IP interface

Telnet input
help
ifconfig
ifconfig
[help|dhcp|ip |mask]
tpconfig
tpconfig [help|set]
progmode [0|1]
apdu [55..248]
IPR / IPS 300 SREG
Description
Displays all available commands
Displays network parameters
IP mode.......: DHCP
IP............: 192.168.33.142
Subnet mask...: 255.255.0.0
Gateway.......: 192.168.33.1
NTP server....: 192.53.103.108
Sys multicast.: 224.0.23.12
RT multicast..: 224.0.23.12
Hardware addr.: 00:50:c2:79:3f:ff
Sys multicast: Multicast address for System telegrams
RT multicast: Multicast address für routingt telegrams
Set network parameters via the telnet interface.
Expamples:
Setting IP Addresse with DHCP:
ifconfig dhcp
Statically set the IP address to 192.168.1.2 (in this case, the gateway and
mask should also be adapted, see below)
ifconfig ip 192.168.1.2
Set the gateway to 192.168.1.1:
ifconfig gw 192.168.1.1
Set the mask to 255.255.255.0:
ifconfig mask 255.255.255.0
Shows KNX parameters
KNX bus state.: up
KNX address...: 15.15.000
Serial number.: 00-a6-00-00-00-01
Set KNX parameters via the telnet interface.
Set the TP address to 1.1.0:
tpconfig set 1.1.0
Query or change programming mode (0 = off, 1 = on)
Read or configure the maximum length of the KNX TP telegrams. This may be
necessary if there is an incorrect implementation of a TP stack. In that case
the ETS may try to use telegrams with 248 bytes payload, but the TP device
can not process (e.g. Zennio Z35i). Default is 248 and should only be changed
if necessary.
# apdu
maximal len of a KNX telegram 248.
Usage: apdu [55 .. 248]
Telnet
Page 18 of 25