I updated my music broadcasting stack which incudes my broadcast server that accesses and encodes the music which I then send to my relay servers. They now have the latest security patches on my 2025 Data Center broadcast sever and my Fedora Linux 44 music relay server I serve up IceCast and ShoutCast stream from.
I ended up with an issue as I had brought up a test vm I hadn’t worked on in a long time that was the same ip.addess of my W2025 broadcast server. After applying the patches and rebooting the broadcast servers behavior to the ip.address conflict was not to bring the network interfaces up at all which threw me. I disabled, brought up dhcp, searched for ghost interfaces etc. Finally I shutdown the broadcast server and attempted to ssh into the ip.address that shouldn’t have been up and I was able to and identify it as my test vm. I shutdown my test vm and brought up my broadcast VM\server and all interfaces were visible. Just strange the network interfaces would disappear when looking on the cli with an ipconfig but show the 169.nnn.nnn.nnn ip in the UI you get when unable to get a dhcp ip address in windows. I brought up the test server and changed it to unused ips on all the networks it needs in my environment.
Anyway back up and streaming all this Gumbo Mix of genres and eras here at SnakeIce’s House of Beats!






































