Closed speltriao closed 2 years ago
Hi,
I was able to replicate the issue into 22.10, it is due to a lack of DNS servers in the resolv.conf file. It only happens after a reboot, because resolv.conf was created by systemd-resolved before installing resolvconf.
It seems to be due to changes tying netplan to NetworkManager, NetworkManager to either systemd-resolved or dnsmasq, and dhclient to systemd-resolved for DNS info.
Whilst resolvconf has been declared as "deprecated" for a while, it has been an easy DNS glue in the Debian family.
Will investigate further the issue, thanks for the message.
On Wed, 28 Sept 2022 at 19:36, Alexandre Speltri @.***> wrote:
Hello, first of all, thank you for your work. It has served me really well for sometime now on Debian.
I've been trying out Ubuntu 22.10 on two computers, and it's working flawlessly, except for ChrootVPN.
After installing ChrootVPN on Ubuntu 22.10, everything works fine, until I reboot. After a reboot, on both computers, my network simply ceased to work... I get an question mark on top of the newtork icon and no connection at all.
I can gladly share more information!
— Reply to this email directly, view it on GitHub https://github.com/ruyrybeyro/chrootvpn/issues/3, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACPDBP6I7QVQDALZG7ZN6S3WASF4RANCNFSM6AAAAAAQYBS7WM . You are receiving this because you are subscribed to this thread.Message ID: @.***>
-- Regards,
-- Rui Ribeiro https://www.linkedin.com/pub/rui-ribeiro/16/ab8/434
resolvconf if broken beyond hope, let's see how it comes when 22.10 is out. Fixed, please download the new vpn.sh. systemd-resolved has to be (re)installed in Ubuntu 22.10 machines where resolvconf was installed.
Again, thanks for alerting me.
Also forgot to mention, Ubuntu 22.10 seems terribly unstable for something so near the date of release. Calamares died several times when using Parallels, ended up installing it using VmWare Fusion.
Thanks for the quick reply. After your fix, I've reinstalled Ubuntu 22.10 from scratch and now I have internet connection after running the script and rebooting.
However, I noticed that when trying to connect to CheckPoint mobile, it acts as the user agent is not installed.... Tried on Firefox (deb, not snap), Firefox ESR (deb), chromium (deb) and chrome (deb).
Curiously, it runs fine on Debian Testing and Debian unstable.
Ubuntu installs a snap, Debian does not. At VPN.sh -i time, the script deploys a Firefox policy when it cans.
If you do VPN.sh uninstall and reinstall, the policy can be deployed; otherwise (and with other browsers like Chrome) you have to visit https://localhost:14186 and accept the certificate manually.
The README talks about this and a couple other pitfalls.
On Fri, 30 Sep 2022, 02:15 Alexandre Speltri, @.***> wrote:
Thanks for the quick reply. After your fix, I've reinstalled Ubuntu 22.10 from scratch and now I have internet connection after running the script and rebooting.
However, I noticed that when trying to connect to CheckPoint mobile, it acts as the user agent is not installed.... Tried on Firefox (deb, not snap), Firefox ESR (deb), chromium (deb) and chrome (deb).
Curiously, it runs fine on Debian Testing and Debian unstable.
— Reply to this email directly, view it on GitHub https://github.com/ruyrybeyro/chrootvpn/issues/3#issuecomment-1262992482, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACPDBPZCCJEXJU6US32EWZ3WAY5KFANCNFSM6AAAAAAQYBS7WM . You are receiving this because you modified the open/close state.Message ID: @.***>
Thanks for your reply. There is a way to install Firefox on Ubuntu without snaps, which can be found here:
https://www.omgubuntu.co.uk/2022/04/how-to-install-firefox-deb-apt-ubuntu-22-04/amp
It's what I used for installing Firefox as a traditional deb. Snapd is not even installed on my system.
Anyway, I'll try to accept the certificate manually!
Thanks for the link. The Firefox policy is indeed installed at vpn.sh -i / chroot install time.
Nevertheless, added a new "policy" command line option. If you do "vpn.sh -i" before installing Firefox, you now run:
vpn.sh policy
The policy file usually is not installed, if firefox is a snap, or if another policy is already installed.
I just got this problem while trying to connect to a checkpoint vpn on debian (and failing for reasons outside this scope).
To solve it I had to execute ln -fs /run/resolvconf/resolv.conf /etc/resolv.conf
an that fixed the /etc/resolv.conf
file.
I dont know if I did uninstall this incorrectly or what, but that solves it if someone else has this problem in the future
Hello, first of all, thank you for your work. It has served me really well for sometime now on Debian.
I've been trying out Ubuntu 22.10 on two computers, and it's working flawlessly, except for ChrootVPN.
After installing ChrootVPN on Ubuntu 22.10, everything works fine, until I reboot. After a reboot, on both computers, my network simply ceased to work... I get an question mark on top of the newtork icon and no connection at all.
I can gladly share more information!