Enable FIPS Mode on SLES 15 and Verify the Boot State
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Not everyone is able to own a Samsung 2018 smart TV , owning an older Samsung TV such as 2017, 2016 will help users save progress while still maintaining good image quality.
However, those TVs usually do not automatically set up the network and still have to manually set IP and DNS. In the article below, WebTech360 guides the steps to setup IP and network DNS for your Samsung smart TV !
The setting of network IP and network DNS will help your TV to connect to the network more successfully and steadily, and troubleshoot the network later.
Step 1: Check the information on the network IP address your home is installing:
- To know which IP address your home is installing, use a laptop, tablet, or smartphopne to see.

- For laptop, go to Control Panel -> All Control Panel Items -> Network and Sharing Center and you select the network you are using.
Step 2: Proceed to set IP for TV.
- To set IP for Samsung smart TV, press MENU button (some other remote will have house picture).
- Then you go to the network and select Network status to check the Internet connection.
- You choose to enter the network state.
- After that, the TV will enter network check standby mode.
- The network interface on the TV will display as shown, choose IP Settings to edit.
- You choose Manual Import.
- You choose to go to IP Address and enter the correct IP address of the network operator.
Step 3: To proceed with DNS settings, scroll down to DNS Settings .
- And similar to IP, you set up the DNS network automatically or choose to enter manual mode.
- You choose to go to DNS Server.
Enter compatible DNS, it will normally be 8.8.8.8
- After successfully entering, click OK to end the program.
Wish you success !!!
Follow SUSE’s SP7 procedure to enable FIPS mode, reboot safely, verify the active policy, and check whether your compliance requirement calls for validated modules.
Compare YaST and cryptsetup for a new encrypted SLES data volume, choose LUKS1 or LUKS2, and verify unlock and mount behavior safely.
Create, refine, and verify a least-privilege AppArmor profile on SLES 15 SP7, with a clear note on SLES 16’s SELinux default.
Set up RMT on SLES 15, mirror entitled repositories, and verify HTTPS registration and package access from a test client.
Connect SLES 15 to AD with YaST’s SSSD-based logon management, then verify directory lookup, domain login, and Kerberos tickets.
Set up the right Live Patching path for SLES 16.0 or 15 SP7, apply eligible kernel fixes, and confirm what is active without confusing it with a reboot-required kernel update.
Load a custom SLES 15 kernel module without disabling Secure Boot. Match the running kernel, sign the .ko file, enroll a MOK key, and verify loading.
SLES 15 SP5 can migrate online to SP6, but each node must reboot. Use a tested rolling upgrade or blue-green cutover to keep workloads reachable.
Use SUSE’s supported STIG profile to scan SLES 15, test remediation, review remaining findings, and retain assessment evidence.
Trace a failed Cockpit connection through DNS, port 9090, the systemd socket, firewalld, TLS, and login settings using current SUSE guidance.