Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#53939 - [openconnect] Invalid resolv.conf created when multiple domains specified by vpn with juniper mode
Attached to Project:
Arch Linux
Opened by Gregory Gleason (gsgleason) - Friday, 05 May 2017, 15:58 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 05 May 2017, 17:07 GMT
Opened by Gregory Gleason (gsgleason) - Friday, 05 May 2017, 15:58 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 05 May 2017, 17:07 GMT
|
DetailsDescription:
When using openconnect to connect to a juniper vpn which specifies multiple domains, an invalid resolv.conf is created. There is a discussion here: http://lists.infradead.org/pipermail/openconnect-devel/2016-August/003819.html Additional info: * package version(s) http://lists.infradead.org/pipermail/openconnect-devel/2016-August/003819.html * config and/or log files etc. Steps to reproduce: My work has a vpn with multiple domains. The script vpnc-script doesn't account for that. There is a mailing list discussion which includes a patch, but I can't tell if it's actually been included upstream or not. I can't seem to access the upstream site. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Friday, 05 May 2017, 17:07 GMT
Reason for closing: Duplicate
Additional comments about closing: Don't make useless duplicates
Friday, 05 May 2017, 17:07 GMT
Reason for closing: Duplicate
Additional comments about closing: Don't make useless duplicates