Hi Fenyo,
unfortunalty the setup, either done by cli or WebGui, does make kind of a fuss to the firewall. You need to reconfigure the UnBoundDNS-Section of the opnSense after you ran linuxmuster-setup (see Murks nach linuxmuster-setup im Setup der opnSense - #18 von Adrian). Otherwise you will probably experiance DNS-Loop-Issues.
Kind regards
Thomas
Hi,
Thanks for the idea, but unfortunately I have set the unbound dns tool to query forward in opnsense, but it does not help, still no name resolution, only ping works after gateway recovery. One more oddity is that the server after websetup becomes read-only in the filesystem, so even if I wanted to I couldn’t poke into the config files.
Hi Feyno,
im very sorry that you experiance such hardship while installing linuxmuster.net.
This is not normal.
Thomas has noticed the Problems some weeks ago and we were not able yet to resolve these.
I made some screenshots for you so you can see, how the unbound should be configured.
Regard the „use system Nameservers“ which has no tick!
Restart the services afterwards or the OPNsense itself and then test again.
I wanted to test the vanilla install this week: but there was no time. I’ll try to do that next week …
Yours
Holger
Yes, that’s exactly what I did, the description Thomas linked to did the same, but it didn’t help. I didn’t restart the opnsense but only the service (I don’t think it matters), next time I’ll be able to try again next week.
I didn’t have time to test it this week, but I did get a router for the opnsense, to see if that was the cause of the agony. So I’ll try again next week, but I see that version 7.3 can be installed from scratch. Then I might try it, as I read the description the main difference is that the domain controller and the fileserver have been separated. On the lmn server physical machine, would this mean that in addition to the separate fileserver package installation, the server gets a second ip address or does it need a second network card too?
Thanks Fenyo
Hi Fenyo,
the Fileserverseparation in 7.3 is optional not obligatory, as far as i know.
If you separate it it runs on a separate machine which can be a second virtual Machine on the same VM-Host. There is no need for a second Networkkard since both are in the same Netwokr, which we call „Grün“ (Green).
yours
Holger
OK, thanks, then I guess the fileserver settings can be ignored, it can only be optionally detached and run on another physical or virtual machine if I understand correctly.
Hi Fenyo,
thats correct.
It is also designed to be migrated in a running environment.
When you notice, after a while, that you would like to move the Fileserver to another Machine: to migrate a two server installation (OPNSense,LMN) to a threeserver Installation (OPNsense, LMN, Fileserver)
Yours
Holger
Hi,
Thanks, tap two done, unfortunately it still messes up after websetup. The router has helped the situation so much that now the gateway stays good after websetup, but web interface is no longer accessible from client machine after successful setup message (I can ping it, but nothing else). A new phenomenon is that the dhcp server does not work after websetup, this worked in 7.2, looking into the dhcpd.conf file it does not include the range in setup.ini only nameserver domain ntp gateway and other static stuff. By default name resolution also doesn’t work after websetup only if I set my own name server in resolv.conf. So I don’t know where things go wrong, I can try 7.2 again with router.
Hi.
Your linuxmuster-server has a different name than simply server– I’m not sure, but I think the name server is highly recommended. However, I’m not sure if it could be causing the issues shown in your screenshots.
Holger (@baumhof) – was meinst Du?
Viele Grüße,
Michael
Hello,
In the lmn-appliance script you can set a hostname other than default (which is then put in setup.ini), of course I can also try it with a single/default server name…
Thanks Fenyő
Hello,
@Michael: hostname does not have to be server. None of my LMN-Server have this hostname 
Cheers
Arnaud
Unfortunately, I can’t get it to work, after the websetup the system gets completely messed up, after it runs successfully (I can click on the finish button), until I restart the server as root it still lets me in, but as global-admin it gives ldap error, and after restarting it, it gives authentication error with any user (opnsense is allowed with the changed password during websetup, and I can log in on the physical server itself).
Hi Fenyo,
is the domainservice running?
service samba-ad-dc status
What does it say?
Is it working after a reboot?
Yours
Holger
Hi,
Unfortunately no, the situation is similar to dhcp, it’s installed, it’s active, but it crashes with errors.
Hi Fenyo,
the things happening in your environment are not normal and dont seem to be a normal BUG.
We need to analyse, what is different to the normal installation Process.
Please describe how you installed it, what your virtualization Plattform is, how the VMs are configured (RAM, CPU, Storage, Storage Controller).
Very importaint is the question, how you installed it.
There are certain Points in the Docu, where you are supposed to make a apt update and apt dist-upgrade befor continnuing with the installation. id you do that?
It might be interessting to find out why the samba is not running: can you provide log files for that?
LG
Holger
Hi Fenyo,
did you see this?
Did you use Proxmox?
Does a
systemctl restart samba-ad-dc.service
provide you with a running samba-ad-dc
?
Yours
Holger
Hi,
I’ve only used 2 physical machines so far, my Proxmox knowledge still needs a lot of work (and the storage park of the physical machine itself could use an upgrade first). One of the physical machines has the latest opnsense (25.1-6), the other Ubuntu server 24.04 and lmn 7.3-17. I followed the instructions all the way through except for the Proxmox parts.
Thanks Fenyő
Hello Fenyo,
Ubuntu 24.04 and LMN 7.3 is not a good starting point, because LMN 7.3 is still in heavy development. I would recommend to install first Ubuntu 22.04 with LMN 7.2.
Cheers
Arnaud
Hello,
Yes, I tried that one first (machine 1 opnsense 25.1-5, machine 2 ubuntu 22.04 + lmn 7.2-81), but the situation was similar, except that dhcp worked there, the multiple symptoms were the same. I also thought that with 7.2 I might need an older opnsense, but which one?
Thanks Fenyő
