IPC@CHIP® RTOS-LNX – API Documentation

Header image

Main page


CHIP.INI [IP_ETH1]


[IP_ETH1]
ADDRESSx=IP address of the Ethernet 1 interface

Defines the IPv4 addresses of the Ethernet 1 interface, of the IPC@CHIP®. A maximum of five IP addresses may be listed with tags ADDRESS and ADDRESS1 up to ADDRESS4. The entry tag search is terminated at the first non-existant tag in this sequence.

Note: The tag ADDRESS0 is not recognized, instead the tag ADDRESS must be used.

Only numerical IP addresses are allowed here.
Default:
No default.
Example:
[IP_ETH1]
ADDRESS=192.168.200.1
ADDRESS1=172.30.10.12
Since
V0.87


[IP_ETH1]
NETMASKx=IP address mask of the Ethernet 1 interface

Defines the IPv4 subnet mask of the Ethernet 1 interface of IPC@CHIP®. A maximum of five IP address masks may be listed with tags NETMASK and NETMASK1 up to NETMASK4. The entry tag search is terminated at the first non-existant tag in this sequence.

Note: The entry NETMASK0 is not recognized, instead the tag NETMASK must be used.

Default:
If no subnet mask entry was found, the subnet mask will be set to 255.255.255.0.
Example:
[IP_ETH1]
NETMASK=255.255.255.224
NETMASK1=255.255.240.0
Since
V0.87


[IP_ETH1]
GATEWAY=Gateway IP address

Defines the default IPv4 gateway.

The TCP/IP stack of the IPC@CHIP® supports only one valid default gateway for all device interfaces (Ethernet, PPP etc).
Default:
No default.
Example:
[IP_ETH1]
GATEWAY=192.168.0.1
Note:
As the device only supports one valid default gateway, gateway configurations set on other interfaces can override the gateway configuration on this interface. Only the last gateway configuration from any ethernet interface will be valid as the default configuration of the device at each moment. Also note that if DHCP is used on any interface, it is not possible to predict which interface will set the default gateway.
Since
V0.87


[IP_ETH1]
DHCP=0/1

Set to 1 if DHCP client should be used to get the IP configuration for the internal Ethernet 1 interface from a DHCP server. If defined as 0, a static network configuration is used.

Any settings for IP address, subnet mask and gateway are ignored if DHCP is used.
Default:
Use DHCP.
Example:
[IP_ETH1]
DHCP=1
Since
V0.87


[IP_ETH1]
DHCP_TRIALS=Number of DHCP configuration trials

Specify the number of DHCP configuration trials.

The IPC@CHIP® will try to obtain an IP configuration via DHCP several times. The IPC@CHIP® will try to discover a DHCP server in the network in order to obtain a dynamic IP configuration.

The number of trials can be configured with this option. Valid values are between 0 and 128. A value of 0 will set the number of trials to endless (AUTOIP will not be performed).

The time interval between each DHCP server discovery attempt is set to 3 seconds. If the IPC@CHIP® is able to discover a DHCP server but the DHCP IP lease attempt fails it will disable DHCP and configure itself using AUTOIP.

Default:
Default are 3 trials
Since
V0.87


[IP_ETH1]
HOSTNAME_OPT=0/1

Insert device name at DHCP requests as option 12. If set to 1, the IPC@CHIP® will insert its hostname as option 12 in its DHCP configuration requests. This is the name defined at Device name. If the additional entry CLIENT_ID is not defined, the device name string is also inserted at the DHCP request as client identifier option 61.
Default:
By default this feature is disabled.
Example:
[IP_ETH1]
HOSTNAME_OPT=1
Since
V0.87


[IP_ETH1]
AUTOIP=0/1

If AUTOIP is set to 1 and DHCP= 1, the Ethernet 1 interface will be configured by the AutoIP algorithm in case that the IP configuration by DHCP fails.
The AutoIP procedure configures the Ethernet interface with a random IP address between 169.254.1.0 and 169.254.254.255. After selecting a random IP, it executes an address collision detection by sending ARP probes. The procedure repeats with new random IP addresses, until no collision can be detected.

Default:
AutoIP is enabled by default.
Example:
[IP_ETH1]
AUTOIP=0
Since
V0.87


[IP_ETH1]
CLIENT_ID=string

Insert client identifier string at DHCP requests as option 61. Maximum name size: 20 characters.

If this entry is specified, the IPC@CHIP® insert at its DHCP request the specified string as DHCP option 61. If this entry is not specified but the entry HOSTNAME_OPT is yet defined, the IPC@CHIP® inserts here its Device name.

If CLIENT_ID is set to the reserved word "MAC_ADDR", the IPC@CHIP® builds a 7 Byte long client identifier option consisting of:
1 Byte Hardware type, with value 1 for Ethernet
6 Bytes physical Ethernet address.
Default:
By default this feature is disabled.
Example:
[IP_ETH1]
CLIENT_ID=MAC_ADDR
Since
V0.87


[IP_ETH1]
ETH_PRIO=prio

Defines the task priority of the Packet driver Ethernet receiver task (@PKT). Allowed value are 2-127.
Default:
Default is 14.
Example:
[IP_ETH1]
ETH_PRIO=11
Since
V1.05


[IP_ETH1]
ETH_ENABLE=0/1

Defines whether the internal Ethernet 1 controller of the IPC@CHIP® is started or not. If ETH_ENABLE=0 the Ethernet 1 device is not started.
Default:
By default the Ethernet 1 device is disabled.
Example:
[IP_ETH1]
ETH_ENABLE=1
Since
V0.87


[IP_ETH1]
DISABLE_HELLO=0/1

Defines whether to disable UDP configuration HELLO messages for the Ethernet 1 interface. If DISABLE_HELLO=1 HELLOs are not sent over this interface.
Default:
By default the UDP configuration server HELLO messages are enabled
Example:
[IP_ETH1]
DISABLE_HELLO=1
Since
V1.18





Top of page | Main page

Copyright © 2018 Beck IPC GmbH
Generated on Fri Jun 8 2018 12:48:20 by Doxygen 1.8.13