Zum Hauptinhalt springen

Kategorie: Administration

Quick Info: VMware Workstation Netzwerk funktioniert nicht

Ich habe kürzlich meine VMware Workstation auf eine neue Hostmaschine umgezogen und seitdem funktionierten weder die vmnet Interfaces noch sonst irgendein Netzwerk Service von VMware. Mittels vmware-network -status lässt sich der aktuelle Zustand der virtuellen NICs und der Netservices überprüfen. Bei mir kam Bridge networking on vmnet0 is not running DHCP service on vmnet1 is not running Hostonly virtual adapter on vmnet1 is disabled DHCP service on vmnet8 is not running NAT service on vmnet8 is not running Hostonly virtual adapter on vmnet8 is disabled Some/All of the configured services are not running was ich versuchte mit vmware-network -start zu beheben.

Quick Info: VMware Workstation network not working

Lately I moved my VMware Workstation to another machine and since then neither the vmnet NICs nor any of the VMware network services was working. With vmware-network -status the status of the virtual NICs and netservices can be checked. I got Bridge networking on vmnet0 is not running DHCP service on vmnet1 is not running Hostonly virtual adapter on vmnet1 is disabled DHCP service on vmnet8 is not running NAT service on vmnet8 is not running Hostonly virtual adapter on vmnet8 is disabled Some/All of the configured services are not running as response.

Quick Info: Kein Zugriff auf Veracrypt Volumes nach non-root mount

Kürzlich habe ich Debian auf meinem Desktop Computer aufgesetzt (thx @Hypfer das du mich zu diesem Schritt ermutigt hast). Eines der ersten Probleme welches mir über den Weg lief war, dass meine externe, verschlüsselte HDD nur für den root User lesbar war. Grund dafür ist, dass ich VeraCrypt via gksudo gestartet habe da es sonst nicht in der Lage war die Volumes zu mounten. Die Lösung dafür war eine Ausnahme in die sudoers Datei zu schreiben:

Quick Info: No access to Veracrypt encrypted volume after mounting as non-root

I recently switched over to Debian on my desktop computer (thx @Hypfer for convincing me to do this). One of the first issues I ran into was the fact that after I mounted my encrypted external harddrive it was only readable for the root user. The cause of this is that I start Veracrypt via gksudo because otherwise I was not able to mount my drives since my main user is not in the sudoers list.

Quick Info: Debian stuck at boot due to IPv6

Lately I bought a couple HDDs to finish my home made NAS running OpenMediaVault Debian. I personally think that IPv6 should be supported by any means, so I activated it right after finishing the installation process and everything was working fine. I shut down the system during the night hours because there was no reason to leave it on because I had not yet copied any data onto the NAS.