My first doubt was that you are hacking an UTM [:)] give one in the back to your Son! No really you have to be proud, someday we will leavev the passworda
My first doubt was that you are hacking an UTM [:)] give one in the back to your Son! No really you have to be proud, someday we will leavev the passworda
My first doubt was that you are hacking an UTM [:)] give one in the back to your Son!
No really you have to be proud, someday we will leavev the passworda
No, definitely not hacking a utm. I wanted to leave the existing utm running while I was getting the new one configured. Had I tried the username and password we are using on the existing utm, it would have worked. I never tried it because it never occurred to me that my son took a look at it when he got home (late). I never got it running last night because I couldn't access webadmin. It turned out that was because the internal NIC wasn't enabled in the hyper-v server. I wanted to see how a new utm is configured from the beginning so I created a new VM from scratch, reinstalled utm 9.1 beta and set it up. I have to say, I'm impressed at how easy it is to set everything up. The unification of dhcp and dns is a big improvement. (I just wish they would do something about the *CENSORED* SSL VPN.) I'll try cutting over to utm 9.1 beta tomorrow.
