05-21-2020, 06:53 PM
Hi Kent,
yes, thanks, I absolutely will do..
and you are right, my info about switching off IPv6 was a bit confusing. It was just some sort of last wild guess. I switched it off manually by editing the file /etc/sysctl.conf (adding net.ipv6.conf.all.disable_ipv6 = 1). I have to admit, last time working with such kind of stuff was 20 years ago, I'm no expert - so better ignore that piece of information as it probably was nonsense
.
I have set up a fresh system, without anything configured (just did a first boot and positively checked if the ui is accessible). So right now it is connected via ethernet, audio is not configured.
Just to clearify, as soon as I configure my wifi (and unplug ethernet cable), I still can access the system over wifi via ssh (so a wrong IP is not the problem - I always get them with the help of a network scanner). But the web-ui doesn't show up, and via ssh the 'moodeutl -l' command shows only the first lines (as shown in my initial post), and running the 'sysinfo.sh' as mentioned by Tim doesn't give any output but leaves the ssh-connection nonresponding.
Ciao Chris
yes, thanks, I absolutely will do..
and you are right, my info about switching off IPv6 was a bit confusing. It was just some sort of last wild guess. I switched it off manually by editing the file /etc/sysctl.conf (adding net.ipv6.conf.all.disable_ipv6 = 1). I have to admit, last time working with such kind of stuff was 20 years ago, I'm no expert - so better ignore that piece of information as it probably was nonsense
. I have set up a fresh system, without anything configured (just did a first boot and positively checked if the ui is accessible). So right now it is connected via ethernet, audio is not configured.
Just to clearify, as soon as I configure my wifi (and unplug ethernet cable), I still can access the system over wifi via ssh (so a wrong IP is not the problem - I always get them with the help of a network scanner). But the web-ui doesn't show up, and via ssh the 'moodeutl -l' command shows only the first lines (as shown in my initial post), and running the 'sysinfo.sh' as mentioned by Tim doesn't give any output but leaves the ssh-connection nonresponding.
Ciao Chris
