In the PPP list, you are able to specify you own definition of PPP negotiation for every remote site contacting your network.
The authentication of point-to-point connections in the WAN commonly relies on one of the protocols PAP, CHAP, MSCHAP or MSCHAPv2. The protocols here have a "hierarchy" amongst themselves, i. e. MSCHAPv2 is a "higher-level" protocol than MSCHAP, CHAP and PAP (higher protocols provide higher security). Many dial-in routers at Internet providers allow up-front authentication using a higher-level protocol such as CHAP, but only support the use of PAP further down the line. If the setting for the protocol for authentication is fixed in the LANCOM, the connection may fail because no common authentication protocol can be negotiated.
A flexible setting for the authentication protocols in the LANCOM ensures that the PPP connection is established as required. In addition, one or more protocols can be defined that are accepted for authentication of remote sites in the LANCOM (inbound connections) and on login of the LANCOM into other remote sites (outbound connections).
- When establishing inbound connections, the LANCOM requires the lowest of the permitted protocols, but where possible it also permits the remote site to use one of the higher-level protocols (enabled in the LANCOM).
- When establishing outbound connections, the LANCOM offers all enabled protocols, but only permits a selection from precisely these protocols. It is not possible to negotiate one of the disabled, possibly higher-level, protocols.
The PPP authentication protocols are set in the PPP list.
LANconfig: Communication / Protocols / PPP list
WEBconfig: Setup / WAN / PPP