openconnect: no specific route and wrong MTU
Open
@nmav is already working on this.
Since Nov 13, 2023.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Maintainer: @nmav
Environment: aarch64, Xiaomi Redmi Router AX6S(mediatek/mt7622), OpenWrt 23.05.0 r23497-6637af95aa
Description:
I using my router as client for remote Openconnect server. It worked perfect with OpenWrt 22.03.5 but stopped after upgrade firmware to 23.05.0. My investigation bring me two issues:
- no specific route to the ocserv's IP-address after connection is up
- wrong MTU on the openconnect interface (always 1500 whatever set in the config)
I managed to working connection by manual add the route and change MTU to 1436 but I don't know why it's not working automatically.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.