Westermo Ibex-RT-370 Firmware

Brand: Westermo

Model: Ibex-RT-370

Type: Firmware

This manual is also suitable for

Software 6 Release Notes

Release 6.9.3-RC0

Westermo Network Technologies AB

November 11, 2020

Contents

1 General Information 3

2 Release Highlights 4

2.1 RC0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

3 Limitations 4

4 Conﬁguration Parameter Changes 4

5 Modules Modiﬁed 7

6 Changed Conﬁguration Parameter Descriptions 7

6.1 MIB Reference: WESTERMO-SW6-MIB . . . . . . . . . . . . . . . . . . . . . . . . 7

6.2 MIB Reference: WESTERMO-SW6-FIREWALL-MIB . . . . . . . . . . . . . . . . . . 39

2 of 40

1 General Information

Company

Westermo Network Technologies AB

Contact Support

www.westermo.com

Release Number

6.9.3-RC0

Software Build Number

707fda8e86362af5732cecda9cad2a665058de6c

Date of this build

November 11, 2020

3 of 40

2 Release Highlights

2.1 RC0

• Products: Initial release for Ibex-RT-280

• IPsec: Initial release

• DNS/DHCP: Support for Domain and Host override added

• Usability: Comment ﬁelds for IPs, Routes and Firewall Rules

3 Limitations

•

When the device is reconﬁgured to Mesh with SAE as encryption, the device has to be rebooted

after applying the conﬁguration

• Multi-SSID with DFS channels is not working (802.11n products only)

4 Conﬁguration Parameter Changes

The following conﬁguration items have been added/changed/removed:

• cfgNetIpComment (added)

• cfgNetIpsecName (added)

• cfgNetIpsecEnabled (added)

• cfgNetIpsecMtu (added)

• cfgWlanDevAtfSchedulingAlgorithm (added)

• cfgWlanIfaceAtfSsidEnabled (added)

• cfgWlanIfaceAtfSsidAirtime (added)

• cfgRouteTableComment (added)

4 of 40

• cfgDhcpDnsmasqDnsDomainOverrideParameter (added)

• cfgDhcpDmnOvrId (added)

• cfgDhcpDmnOvrEnabled (added)

• cfgDhcpDmnOvrDomain (added)

• cfgDhcpDmnOvrServer (added)

• cfgDhcpDnsmasqDnsHostOverrideParameter (added)

• cfgDhcpHstOvrId (added)

• cfgDhcpHstOvrEnabled (added)

• cfgDhcpHstOvrHost (added)

• cfgDhcpHstOvrAddress (added)

• cfgNlmMonType (changed)

• cfgNlmMonUpAction (changed)

• cfgNlmMonDownAction (changed)

• cfgCellSimProﬁleRoaming (added)

• cfgVpnIpsecLeft (added)

• cfgVpnIpsecRight (added)

• cfgVpnIpsecLeftSubnet (added)

• cfgVpnIpsecRightSubnet (added)

• cfgVpnIpsecLeftId (added)

• cfgVpnIpsecRightId (added)

• cfgVpnIpsecLeftAuth (added)

• cfgVpnIpsecRightAuth (added)

• cfgVpnIpsecType (added)

• cfgVpnIpsecAuto (added)

5 of 40

• cfgVpnIpsecKeyExchange (added)

• cfgVpnIpsecMobIke (added)

• cfgVpnIpsecIke (added)

• cfgVpnIpsecEsp (added)

• cfgVpnIpsecIkeLifetime (added)

• cfgVpnIpsecLifetime (added)

• cfgVpnIpsecKeyingTries (added)

• cfgVpnIpsecDpdAction (added)

• cfgVpnIpsecDpdDelay (added)

• cfgVpnIpsecDpdTimeout (added)

• cfgVpnIpsecKeyPassword (added)

• cfgVpnIpsecPassword (added)

• cfgVpnIpsecCustomOptions (added)

• cfgVpnIpsecGlblVirtualTunnelInterface (added)

• cfgVpnIpsecGlblCustomOptions (added)

• cfgVpnIpsecDbgAsn (added)

• cfgVpnIpsecDbgCfg (added)

• cfgVpnIpsecDbgChd (added)

• cfgVpnIpsecDbgDmn (added)

• cfgVpnIpsecDbgEnc (added)

• cfgVpnIpsecDbgEsp (added)

• cfgVpnIpsecDbgIke (added)

• cfgVpnIpsecDbgImc (added)

• cfgVpnIpsecDbgImv (added)

6 of 40

• cfgVpnIpsecDbgJob (added)

• cfgVpnIpsecDbgKnl (added)

• cfgVpnIpsecDbgLib (added)

• cfgVpnIpsecDbgMgr (added)

• cfgVpnIpsecDbgNet (added)

• cfgVpnIpsecDbgPts (added)

• cfgVpnIpsecDbgTls (added)

• cfgVpnIpsecDbgTnc (added)

• cfgFwNatPrtFwdComment (added)

• cfgFwNatOutComment (added)

• cfgFwL2IpFltrComment (added)

• cfgFwFltRComment (added)

5 Modules Modiﬁed

6 Changed Conﬁguration Parameter Descriptions

6.1 MIB Reference: WESTERMO-SW6-MIB

6.1.1 cfgVpnIpsecType

IPsec Type

The type of the connection; currently the accepted values are:

• tunnel(0): signifying a host-to-host, host-to-subnet, or subnet-to-subnet tunnel

• transport(1): signifying host-to-host transport mode

• transportProxy(2): signifying the special Mobile IPv6 transport proxy mode

• passthrough(3): signifying that no IPsec processing should be done at all

• drop(4): signifying that packets should be discarded.

7 of 40

Enumeration tunnel (0), transport (1), transportProxy (2), passthrough (3), drop (4)

Access readwrite

Status current

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.100

6.1.2 cfgVpnIpsecCustomOptions

Custom IPsec Options

These options are appended to the IPsec conﬁguration. This allows to set options not available via

other conﬁguration items. Set to none when no additional options shall be added.

When setting multiple options, separate them with a semicolon ;.

The full list of all available options is at: https://wiki.strongswan.org/projects/strongswan/wiki/ConnSection

Prohibited options are:

• left

• leftid

• leftsubnet

• leftauth

• right

• rightid

• rightauth

• rightsubnet

• keyexchange

• mobike

• ikelifetime

• lifetime

• keyingtries

• type

• ike

• esp

• dpddelay

• dpdtimeout

Essentially everything which is possible to set by other SNMP commands. Applies to AP and STA.

Access readwrite

Status current

Type DisplayString

Range 4 - 4095

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.1000

8 of 40

6.1.3 cfgVpnIpsecAuto

IPsec Auto Startup Operation

What operation, if any, should be done automatically at IPsec startup.

• ignore(0): Ignores the connection. This is equal to deleting a connection from the conﬁg ﬁle.

• add(1): Loads a connection without starting it.

• route(2)

: Loads a connection and installs kernel traps. If trafﬁc is detected between leftsubnet

(

cfgVpnIpsecLeftSubnet

) and rightsubnet (

cfgVpnIpsecRightSubnet

), a connection is

established.

• start(3): loads a connection and brings it up immediately.

Relevant only locally, other end need not agree on it.

Enumeration ignore (0), add (1), route (2), start (3)

Access readwrite

Status current

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.101

6.1.4 cfgVpnIpsecKeyExchange

Key Exchange Method

Which protocol should be used to initialize the connection.

Enumeration ikev1 (1), ikev2 (2)

Access readwrite

Status current

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.102

6.1.5 cfgVpnIpsecMobIke

Disable or Enable IKEv2 MOBIKE Protocol

Enables the IKEv2 MOBIKE protocol deﬁned by RFC 4555. If set to no, the charon daemon will not

actively propose MOBIKE as initiator and ignore the MOBIKE_SUPPORTED notify as responder.

Enumeration no (0), yes (1)

Access readwrite

Status current

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.103

9 of 40

6.1.6 cfgVpnIpsecIke

IKE/ISAKMP SA Encryption/Authentication Algorithms

Comma-separated list of IKE/ISAKMP SA encryption/authentication algorithms to be used, e.g. aes128-

sha256-modp3072. The notation is encryption-integrity[-prf]-dhgroup. In IKEv2, multiple algorithms

and proposals may be included, such as aes128-aes256-sha1-modp3072-modp2048,3des-sha1-

md5-modp1024.

It is possible to conﬁgure a PRF algorithm different to that deﬁned for integrity protection. If no PRF is

conﬁgured, the algorithms deﬁned for integrity are proposed as PRF. The prf keywords are the same

as the integrity algorithms, but have a prf preﬁx (such as prfsha1, prfsha256 or prfaesxcbc).

Defaults to aes128-sha256-modp3072 (aes128-sha1-modp2048,3des-sha1-modp1536 before 5.4.0)

for IKEv1. The daemon adds its extensive default proposal to this default or the conﬁgured value. To

restrict it to the conﬁgured proposal an exclamation mark (!) can be added at the end.

Refer to IKEv1CipherSuites and IKEv2CipherSuites for a list of valid keywords.

Note: As a responder both daemons accept the ﬁrst supported proposal received from the peer. In

order to restrict a responder to only accept speciﬁc cipher suites, the strict ﬂag (!, exclamation mark)

can be used, e.g: aes256-sha512-modp4096!

Access readwrite

Status current

Type DisplayString

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.104

6.1.7 cfgVpnIpsecEsp

ESP Encryption/Authentication Algorithms

Comma-separated list of ESP encryption/authentication algorithms to be used for the connection,

e.g. aes128-sha256. The notation is encryption-integrity[-dhgroup][-esnmode]. For IKEv2, multiple

algorithms (separated by -) of the same type can be included in a single proposal. IKEv1 only includes

the ﬁrst algorithm in a proposal. Only either the ah or the esp keyword may be used, AH+ESP bundles

are not supported.

Defaults to aes128-sha256. The daemon adds its extensive default proposal to this default or the

conﬁgured value. To restrict it to the conﬁgured proposal an exclamation mark (!) can be added at the

end.

Note: As a responder, the daemon defaults to selecting the ﬁrst conﬁgured proposal that’s also

supported by the peer. By disabling charon.prefer_conﬁgured_proposals in strongswan.conf this may

10 of 40

be changed to selecting the ﬁrst acceptable proposal sent by the peer instead. In order to restrict a

responder to only accept speciﬁc cipher suites, the strict ﬂag (!, exclamation mark) can be used, e.g:

aes256-sha512-modp4096!

If dh-group is speciﬁed, CHILD_SA rekeying and initial negotiation include a separate Diffe-Hellman

exchange (this also applies to IKEv1 Quick Mode). However, for IKEv2, the keys of the CHILD_SA

created implicitly with the IKE_SA will always be derived from the IKE_SA’s key material. So any DH

group speciﬁed here will only apply when the CHILD_SA is later rekeyed or is created with a separate

CREATE_CHILD_SA exchange. Therefore, a proposal mismatch might not immediately be noticed

when the SA is established, but may later cause rekeying to fail.

Valid values for esnmode are esn and noesn. Specifying both negotiates extended sequence number

support with the peer, the default is noesn.

Refer to IKEv1CipherSuites and IKEv2CipherSuites for a list of valid keywords.

Access readwrite

Status current

Type DisplayString

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.105

6.1.8 cfgVpnIpsecIkeLifetime

IKE Lifetime

How long the keying channel of a connection (ISAKMP or IKE SA) should last before being renegoti-

ated.

Access readwrite

Status current

Type Integer32

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.106

6.1.9 cfgVpnIpsecLifetime

Connection Instance Lifetime

How long a particular instance of a connection (a set of encryption/authentication keys for user

packets) should last, from successful negotiation to expiry; acceptable values are an integer optionally

followed by s (a time in seconds) or a decimal number followed by m, h, or d (a time in minutes, hours,

or days respectively) (default 1h, maximum 24h). Normally, the connection is renegotiated (via the

keying channel) before it expires (see margintime). The two ends need not exactly agree on lifetime,

11 of 40

although if they do not, there will be some clutter of superseded connections on the end which thinks

the lifetime is longer.

Applies to AP and STA.

Access readwrite

Status current

Type Integer32

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.107

6.1.10 cfgVpnIpsecKeyingTries

Keying Tries

When set to -1 means %forever, otherwise what is set.

Examples:

• -1: try forever

• 3

Access readwrite

Status current

Type Integer32

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.108

6.1.11 cfgVpnIpsecDpdAction

Dead Peer Detection Protocol Usage

Controls the use of the Dead Peer Detection protocol (DPD, RFC 3706) where R_U_THERE no-

tiﬁcation messages (IKEv1) or empty INFORMATIONAL messages (IKEv2) are periodically sent

in order to check the liveliness of the IPsec peer. The values clear, hold, and restart all activate

DPD and determine the action to perform on a timeout. With

clear(1)

the connection is closed with

no further actions taken.

hold(2)

installs a trap policy, which will catch matching trafﬁc and tries to

re-negotiate the connection on demand.

restart(3)

will immediately trigger an attempt to re-negotiate

the connection.

The default is none(0) which disables the active sending of DPD messages.

Applies to AP and STA.

12 of 40

Enumeration none (0), clear (1), hold (2), restart (3)

Access readwrite

Status current

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.109

6.1.12 cfgVpnIpsecDpdDelay

Dead Peer Detection Delay

Deﬁnes the period time interval (in seconds) with which R_U_THERE messages/INFORMATIONAL

exchanges are sent to the peer. These are only sent if no other trafﬁc is received. In IKEv2, a value

of 0 sends no additional INFORMATIONAL messages and uses only standard messages (such as

those to rekey) to detect dead peers.

Access readwrite

Status current

Type Integer32

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.110

6.1.13 cfgVpnIpsecDpdTimeout

DPD Timeout

Deﬁnes the timeout interval in seconds, after which all connections to a peer are deleted in case of

inactivity. This only applies to IKEv1, in IKEv2 the default retransmission timeout applies, as every

exchange is used to detect dead peers.

Access readwrite

Status current

Type Integer32

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.111

6.1.14 cfgVpnIpsecKeyPassword

Password to Unlock Private Key

This is only required if the key is encrypted.

13 of 40

Access readwrite

Status current

Type DisplayString

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.112

6.1.15 cfgVpnIpsecPassword

IPsec Password

When cfgVpnIpsecRightAuth is set to psk.

A preshared secret is most conveniently represented as a sequence of characters. The sequence

cannot contain newline or double-quote characters. Alternatively, preshared secrets can be repre-

sented as hexadecimal or Base64 encoded binary values. A character sequence beginning with 0x is

interpreted as sequence hexadecimal digits. Similarly, a character sequence beginning with 0s is

interpreted as Base64 encoded binary data.

Access readwrite

Status current

Type DisplayString

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.113

6.1.16 cfgVpnIpsecLeft

Left or Local

left = ip address | fqdn | %any | %any4 | %any6 | range | subnet

The IP address of the participant’s public-network interface or one of several magic values. The value

%any for the local endpoint signiﬁes an address to be ﬁlled in (by automatic keying) during negotiation.

If the local peer initiates the connection setup the routing table will be queried to determine the correct

local IP address. In case the local peer is responding to a connection setup then any IP address that

is assigned to a local interface will be accepted. The value %any4 restricts address selection to IPv4

addresses, the value %any6 reistricts address selection to IPv6 addresses.

The preﬁx % in front of a fully-qualiﬁed domain name or an IP address will implicitly set leftal-

lowany=yes.

leftallowany is a modiﬁer for left, making it behave as %any although a concrete IP address has been

assigned. Recommended for dynamic IP addresses that can be resolved by DynDNS at IPsec startup

or update time.

If %any is used for the remote endpoint it literally means any IP address.

14 of 40

If an FQDN is assigned it is resolved every time a conﬁguration lookup is done. If DNS resolution

times out, the lookup is delayed for that time.

Connections can be limited to a speciﬁc range of hosts. To do so a range (10.1.0.0-10.2.255.255)

or a subnet (10.1.0.0/16) can be speciﬁed, and multiple addresses, ranges and subnets can be

separated by commas. While one can freely combine these items, to initiate the connection at least

one non-range/subnet is required.

Please note that with the usage of wildcards multiple connection descriptions might match a given

incoming connection attempt. The most speciﬁc description is used in that case.

Access readwrite

Status current

Type DisplayString

Range 1 - 255

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.2

6.1.17 cfgVpnIpsecRight

Right or Remote

right = ip address | fqdn | %any | %any4 | %any6 | range | subnet

The IP address of the participant’s public-network interface or one of several magic values. The value

%any for the local endpoint signiﬁes an address to be ﬁlled in (by automatic keying) during negotiation.

If the local peer initiates the connection setup the routing table will be queried to determine the correct

local IP address. In case the local peer is responding to a connection setup then any IP address that

is assigned to a local interface will be accepted. The value %any4 restricts address selection to IPv4

addresses, the value %any6 reistricts address selection to IPv6 addresses.

The preﬁx % in front of a fully-qualiﬁed domain name or an IP address will implicitly set rightal-

lowany=yes.

rightallowany is a modiﬁer for right, making it behave as %any although a concrete IP address has

been assigned. Recommended for dynamic IP addresses that can be resolved by DynDNS at IPsec

startup or update time.

If %any is used for the remote endpoint it literally means any IP address.

If an FQDN is assigned it is resolved every time a conﬁguration lookup is done. If DNS resolution

times out, the lookup is delayed for that time.

Connections can be limited to a speciﬁc range of hosts. To do so a range (10.1.0.0-10.2.255.255)

or a subnet (10.1.0.0/16) can be speciﬁed, and multiple addresses, ranges and subnets can be

15 of 40

separated by commas. While one can freely combine these items, to initiate the connection at least

one non-range/subnet is required.

Please note that with the usage of wildcards multiple connection descriptions might match a given

incoming connection attempt. The most speciﬁc description is used in that case.

Access readwrite

Status current

Type DisplayString

Range 1 - 255

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.3

6.1.18 cfgVpnIpsecLeftSubnet

IPsec Left Subnet

leftsubnet = ip subnet[[proto/port]][,. . . ]

Private subnet behind the left/local participant, expressed as network/netmask. The conﬁgured

subnets of the peers may differ, the protocol narrows it to the greatest common subnet.

This is also done for IKEv1, but as this may lead to problems with other implementations, make sure

to conﬁgure identical subnets in such conﬁgurations. IKEv2 supports multiple subnets separated

by commas, IKEv1 only interprets the ﬁrst subnet of such a deﬁnition. This is due to a limitation of

the IKEv1 protocol, which only allows a single pair of subnets per CHILD_SA. So to tunnel several

subnets, a conn entry has to be deﬁned and brought up for each pair of subnets.

The optional part after each subnet enclosed in square brackets speciﬁes a protocol/port to restrict

the selector for that subnet.

Examples:

• 10.0.0.1[tcp/http],10.0.0.2[6/80]

• fec1::1[udp],10.0.0.0/16[/53]

Instead of omitting either value %any can be used to the same effect, e.g.

fec1::1[udp/%any],10.0.0.0/16[%any/53]

If the protocol is icmp or ipv6-icmp the port is interpreted as ICMP message type if it is less than 256,

or as type and code if it greater or equal to 256, with the type in the most signiﬁcant 8 bits and the

code in the least signiﬁcant 8 bits.

The port value can alternatively take the value %opaque for RFC 4301 OPAQUE selectors, or a

numerical range in the form 1024-65535. None of the kernel backends currently supports opaque or

port ranges and uses %any for policy installation instead.

16 of 40

Instead of specifying a subnet, %dynamic can be used to replace it with the IKE address, having the

same effect as omitting left|rightsubnet completely. Using %dynamic can be used to deﬁne multiple

dynamic selectors, each having a potentially different protocol/port deﬁnition.

Access readwrite

Status current

Type DisplayString

Range 1 - 255

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.4

6.1.19 cfgVpnIpsecRightSubnet

IPsec Right Subnet

rightsubnet = ip subnet[[proto/port]][,. . . ]

Private subnet behind the right/remote participant, expressed as network/netmask. The conﬁgured

subnets of the peers may differ, the protocol narrows it to the greatest common subnet.

This is also done for IKEv1, but as this may lead to problems with other implementations, make sure

to conﬁgure identical subnets in such conﬁgurations. IKEv2 supports multiple subnets separated

by commas, IKEv1 only interprets the ﬁrst subnet of such a deﬁnition. This is due to a limitation of

the IKEv1 protocol, which only allows a single pair of subnets per CHILD_SA. So to tunnel several

subnets a conn entry has to be deﬁned and brought up for each pair of subnets.

The optional part after each subnet enclosed in square brackets speciﬁes a protocol/port to restrict

the selector for that subnet.

Examples:

• 10.0.0.1[tcp/http],10.0.0.2[6/80]

• fec1::1[udp],10.0.0.0/16[/53]

Instead of omitting either value %any can be used to the same effect, e.g.

fec1::1[udp/%any],10.0.0.0/16[%any/53]

If the protocol is icmp or ipv6-icmp the port is interpreted as ICMP message type if it is less than 256,

or as type and code if it greater or equal to 256, with the type in the most signiﬁcant 8 bits and the

code in the least signiﬁcant 8 bits.

The port value can alternatively take the value %opaque for RFC 4301 OPAQUE selectors, or a

numerical range in the form 1024-65535. None of the kernel backends currently supports opaque or

port ranges and uses %any for policy installation instead.

Instead of specifying a subnet, %dynamic can be used to replace it with the IKE address, having the

same effect as omitting left|rightsubnet completely. Using %dynamic can be used to deﬁne multiple

17 of 40

dynamic selectors, each having a potentially different protocol/port deﬁnition.

Access readwrite

Status current

Type DisplayString

Range 1 - 255

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.5

6.1.20 cfgVpnIpsecLeftId

IPsec Left ID

leftid = id

How the left/local participant should be identiﬁed for authentication; defaults to left or the subject of

the certiﬁcate conﬁgured with leftcert. If leftcert is conﬁgured, the identity has to be conﬁrmed by

the certiﬁcate, that is, it has to match the full subject DN or one of the subjectAltName extensions

contained in the certiﬁcate.

Can be an IP address, a fully-qualiﬁed domain name, an email address or a Distinguished Name for

which the ID type is determined automatically and the string is converted to the appropriate encoding.

The rules for this conversion are described on IdentityParsing (see https://wiki.strongswan.org/projects/strongswan/wiki/IdentityParsing).

In certain special situations the identity parsing above might be inadequate or produce the wrong

result. Examples are the need to encode a FQDN as KEY_ID or the string parser being unable to

produce the correct binary ASN.1 encoding of a certiﬁcate’s DN. For these situations it is possible to

enforce a speciﬁc identity type and to provide the binary encoding of the identity. To do this a preﬁx

may be used, followed by a colon (:). If the number sign (#) follows the colon, the remaining data is

interpreted as hex encoding, otherwise the string is used as is as the identiﬁcation data. Note: The

latter implies that no conversion is performed for non-string identities. For example, ipv4:10.0.0.1 does

not create a valid ID_IPV4_ADDR IKE identity, as it does not get converted to binary 0x0a000001.

Instead, one could use ipv4:#0a000001 to get a valid identity, but just using the implicit type with

automatic conversion is usually simpler. The same applies to the ASN.1 encoded types.

The following preﬁxes are known: ipv4, ipv6, rfc822, email, userfqdn, fqdn, dns, asn1dn, asn1gn and

keyid.

Custom type preﬁxes may be speciﬁed by surrounding the numerical type value with curly brackets.

rightid for IKEv2 connections optionally takes a % as preﬁx in front of the identity. If given it prevents

the daemon from sending IDr in its IKE_AUTH request and will allow it to verify the conﬁgured identity

against the subject and subjectAltNames contained in the responder’s certiﬁcate (otherwise, it is

only compared with the IDr returned by the responder). The IDr sent by the initiator might otherwise

prevent the responder from ﬁnding a conﬁg if it has conﬁgured a different value for leftid.

18 of 40

Access readwrite

Status current

Type DisplayString

Range 1 - 255

OID 1.3.6.1.4.1.16177.1.400.1.1.1003.2.1.1.6

6.1.21 cfgVpnIpsecRightId

IPsec Right ID

rightid = id

How the right/remote participant should be identiﬁed for authentication; defaults to right or the subject

of the certiﬁcate conﬁgured with rightcert. If rightcert is conﬁgured, the identity has to be conﬁrmed

by the certiﬁcate, that is, it has to match the full subject DN or one of the subjectAltName extensions