Comment 6 for bug 1814502

Revision history for this message
Dan Lenski (lenski) wrote :

Ah, that's useful to know.

The Juniper NC protocol (what OpenConnect implements) has a mechanism for the server to tell the client what MTU to use, but no mechanism AFAIK for the client to tell the server what MTU it thinks it has at the IP level — unlike AnyConnect which has both.

This makes the Juniper protocol pretty bad for negotiating a usable MTU. (GlobalProtect protocol is even worse, though.)

```
$ openconnect --prot=nc -vvvv juniper.company.com
...
Received MTU 1400 from server
```