The IP Settings app always takes the last defined external interface and assigns it to the GATEWAYDEV variable in /etc/sysconfig/network. This results in disconnecting the server from the Internet if the last external interface is not connected to the Internet. In this case, the admin has to manually edit /etc/sysconfig/network in order to set the correct gateway device. I think it would be better to have an option in the IP Settings app to define the "default gateway device" in case there are more than one external interface.
I ran into a similar permission problem with transmission and solved it with mounting the Downloads folder to wherever I need it. For example, I wanted to access it from my personal account, so I did the following:
Just to follow up with this issue. I had to create mounting points for transmission Download folder because I thought that was the only way to access the folder from flexshare or user home via SMB. I didn't know about the setting that would allow SMB to follow symbolic links!
So, once you turn "follow symlinks" option on in the SMB' config, then you only need to make a symlink to the transmission Download folder!
Hmm, in this case I think I'm keeping the old Asus router.
I'm redoing my home network after retiring the noisy Dell R410 server. I'll operate the new clearOS server (Dell T30) in standalone mode and relinquish the DHCP service to the ISP fiberoptic modem.
I originally had the clearOS in gateway mode in order to monitor and control the internet access. But since clearOS proxy does not function in transparent mode (due to the internet services nowadays are mostly secured, https), I think standalone mode is the way to go.
I'm thinking of getting rid of my old Asus router working currently as an AP and install a PCIe WiFi card directly into my clearOS box. In this case, clearOS will work as a wireless access point, in addition to the other services it's currently providing, e.g. DHCP, file sharing, plex, etc.
What do you think? Is this a good idea?
ClearOS 7.5 is working as a gateway in my home network. Suddenly, the only Windows client in the network has stoped accessing the network!
It's a Windows 10 running on a laptop. The WiFi connects to the network, but gets wrong IP, gateway and DNS addresses. I flushed the Windows caches and restarted the DHCP client, but still the machine cannot get addresses from the clearOS DHCP server. It connects though if I disabled DHCP auto mode and manually enter the addresses.
I tried to connect the laptop to another network and it worked flawlessly there! Only with clearOS it fails to automatically get the addresses from the DHCP server.
I checked the server and found no traces of the laptop in the DHCP leases table nor in the Intrusion Prevention System.
The Windows machine is manually connecting to the network now, but I really want to make it connects automatically. I'd appreciate any help in this regard.
It depends on your configuration. If you want to run a native hypervisor, then vSphere is the most feature-rich but with a bit of setup difficulty. If you want an easy setup and a straight forward operation, then clearVM.
In case you want a hosted hypervisor (running on top of clearOS), then libvirt is your choice. Kimchi UI will make VMs setup a lot easier. In case you run clearOS in gateway mode, then be aware that there are still some issues with networking that need to be fixed, as mentioned here: https://wikisuite.org/item266-ClearOS-in-Gateway-Mode-Refuses-to-Route-KVMs
I'm trying to access clearOS shares from Windows 10 but without success! The SMBv1 is enabled in Windows 10. The clearOS server is 7.5 beta and running Samba in "Simple Server" mode with "Windows 10 Domain Logons" disabled.
The server appears in the Windows file manager and in "nbtstat -A 192.168.0.1" output. When I double click on the server's icon, Windows asks for username and password. All usernames and passwords I enter are rejected! I tried to login with "winadmin" and with normal users, but always the same result.