Hello,
After updating to Lmn 7.2.22, the server no longer has an external IP address (fixed external IP), so there’s no internet connection—only the internal network—and even that is very sluggish. I’ve had this problem before during installation; at that time, the authentication key pairs weren’t generated between the server and the firewall if the server’s hostname wasn’t set to “server.” Now, in theory, this should be fine because everything looks okay on the Kerberos authentication tab in OpenSense (25.7.11.9).
Hi Fenyo,
the shown ext. IP-address is just the WAN-address of your OPNSense. You can check it here:
cd /etc/profile.d/
cat Z99-linuxmuster.sh
-> IPext -> just a command… there’s a curl or wget command to a provider like dyndns.org or something like that.
I disabled this line as it sometimes took several seconds until the external IP was resolved.
So: What happens when you try this command directly?
Greetings,
Michael
Hello,
Even when I set up a simple client to use the external IP address, it keeps timing out, so it might just be a coincidence related to the update—it could be a network issue or a problem with the internet service provider. For now, I’m trying to figure out which of the three it might be…
Best Regards, Fenyo
If I disconnect the server from the network, everything works fine with the client when I set it to our external IP address, so the internet service is working fine; therefore, the server update must have completely messed up the system. Unfortunately, we still don’t have a backup server, and it’s been quite a while since I last took a snapshot. Here is the output of the commands you requested.
Is there any way to restore the previous 7.2.21 package? The output of the commands you requested is as follows.
Hi Fenyo,
you misunderstood me … you need to enter the command:
wget -q -O - http://ipinfo.io/ip |tail
to resolve your external IP.
But again: this command just shows your IP when your login screen appears. The v7-server itself does not have an own WAN-IP-address!
And: of course it’s always possible to downgrade a package … but I don’t think that’s the reason for the problem. You can find older versions here:
However, I advise against installing them manually.
Greetings,
Michael
The command above doesn’t return anything, which is no surprise, since the server doesn’t have an external IP address. The older 7.2.21 package didn’t help, so it’s possible that one of the Ubuntu packages was to blame; if I recall correctly, the firmware package was updated, which might cause something like this.
yes … that’s correct … it’s just the WAN-IP-address of your OPNSense … I don’t understand the problem with it?
Opnsense hasn’t been updated, but it seems that only the Opnsense WAN port can be pinged, while the gateway cannot.
Hi Fenyo,
in order to debug this step by step you should do the following test:
On the Opnsense, try ping www.heise.de
If this works, your WAN should be fine. If not, you have a problem with the Opnsense and we have to resolve this first.
And please post your IP configuration (Opnsense WAN/red IP + gateway, Opnsense LAN/green IP, Server LAN IP).
Best regards, Jörg
The router’s configuration was corrupted due to a network error. I switched to a temporary router after reassigning the network interfaces in OpenSense. Once the original router was restored, I restored OpenSense from a snapshot because it wouldn’t work with the reassigned configuration. So Opnsense is very sensitive to router changes, but the good news is that thanks to this incident, my request for a PBE server might get the green light.