Scaleway errors on Ubuntu 20.04:
- Firewall not installed
- Email Protection not installed
- Private IP in panel instead of public IP
This is intended, since Ubuntu 20.04 comes without a preconfigured firewall, as Debian 10 does.Firewall not installed
Please check the install.log and see, what causes the error (Search for "Error detected"). You can also see the skipped install steps there to later fix the error manually.Email Protection not installed
WHEN will you release this verion?An appropriate firewall management will most likely be part of KeyHelp 20.3.
There is no ETA yet - expect something during September, but that doesn't necessarily have to be the case.WHEN will you release this verion?
Check beforehand in the settings whether the public IP is also selected there.
Then Tobi is probably right.
Code: Select all
hostname -I
Code: Select all
$ ifconfig ens2
ens2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 10.65.50.27 netmask 255.255.255.254 broadcast 10.65.50.27
Code: Select all
$ ifconfig ens2:0 inet 51.158.128.50 netmask 255.255.255.255
Code: Select all
$ ifconfig ens2:0
ens2:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 51.158.128.50 netmask 255.255.255.255 broadcast 51.158.127.45
Code: Select all
auto ens2:0
iface ens2:0 inet static
address 51.158.128.50/32
Code: Select all
root@testkh:~# grep CONFIG_NFT_ /boot/config-5.4.0-1018-kvm
root@testkh:~# find /lib/modules -name "*nf_tables*"
root@testkh:~# modprobe nf_tables
modprobe: FATAL: Module nf_tables not found in directory /lib/modules/5.4.0-1018-kvm
This helped me so much, thanksnisompic wrote: ↑Sun 13. Sep 2020, 01:09 The internal IP shown instead of the public IP is a direct result of Scaleway's network architecture.
With their public cloud instances, public IPs are actually NATed one-to-one on the private IP of the instance.
In the case of KeyHelp, since the public IP is nowhere to be found in the OS network interfaces, KeyHelp cannot know what the public IP is (though theoretically, it could by querying this information from the outside).
You cannot replace the private IP on the instance without completely breaking networking on it.
What you can do, however, is assigning the public IP on an "alias interface" on the OS.
For example, imagine my Scaleway instance has private IP 10.65.45.25 and public IP 51.158.128.50, the initial network configuration might look like this:
What you would do then is assign the public IP on an alias interface, like so:Code: Select all
$ ifconfig ens2 ens2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 10.65.50.27 netmask 255.255.255.254 broadcast 10.65.50.27
Which would give you:Code: Select all
$ ifconfig ens2:0 inet 51.158.128.50 netmask 255.255.255.255
If you need persistence, you can create a new .cfg file in /etc/network/interfaces.d, for example /etc/network/interfaces.d/60-keyhelp.cfg, with the following contents:Code: Select all
$ ifconfig ens2:0 ens2:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 51.158.128.50 netmask 255.255.255.255 broadcast 51.158.127.45
Save the file, and reboot the instance.Code: Select all
auto ens2:0 iface ens2:0 inet static address 51.158.128.50/32
KeyHelp will now offer both the private and the public IP in the configuration interface. You can simply uncheck the private IP and keep the public IP.
Cheers!
EDIT: I also found out why the firewall installation was not working properly on Scaleway's Ubuntu 20.04:The nf_tables module isn't built with their kernel which is why the installer cannot apply rules.Code: Select all
root@testkh:~# grep CONFIG_NFT_ /boot/config-5.4.0-1018-kvm root@testkh:~# find /lib/modules -name "*nf_tables*" root@testkh:~# modprobe nf_tables modprobe: FATAL: Module nf_tables not found in directory /lib/modules/5.4.0-1018-kvm
Might be worth requesting this to their team.
You could also rebuild the kernel after configuring the correct options to build the nf_tables module.