@kristo I had the same issue and someone at my work came up with a solution to modify the resolv.conf. I ended up with this script using inotifywait, whenever the file is changed this will fix the bad name.
#!/bin/sh
if [[ $EUID -ne 0 ]]; then
echo "This script must be run as root"
exit 1
fi
inotifywait --monitor --event create --include 'resolv.conf' /etc |
while read file; do
if grep -q example.com /etc/resolv.conf
then
sed 's/comname/com|name/g' /etc/resolv.conf | tr '|' '\n' > /tmp/resolv.conf.new
cp /tmp/resolv.conf.new /etc/resolv.conf
fi
done
I run it with a systemd job at network startup:
# /etc/systemd/system/forticlient-fixer.service
[Unit]
Wants=network-online.target
After=network-online.target
[Service]
ExecStart=/root/bin/monitor-resolv.sh
[Install]
WantedBy=multi-user.target
Pinned Comments
douglasimcabral commented on 2022-11-10 15:37 (UTC) (edited on 2023-03-10 00:41 (UTC) by douglasimcabral)
Community,
The Fortinet provides two products, "FortiClient EMS" and "FortiClient VPN only". This package only correspond to "FortiClient VPN only" and your lastest version is 7.0.7.0246 at 03-09-2023.
If you are interested in "FortiClient EMS", I suggest following the AUR package 'forticlient' [https://aur.archlinux.org/packages/forticlient]