The strange thing is that usually the first install or two will work on any new machine but then it suddenly won't. I had this experience on QEMU 2.13 on a different machine. There is something finicky or buggy about the CUCM installer even when choosing the same virtual hardware specs.
QEMU PC emulator version 0.12.1 (qemu-kvm-0.12.1.2-2.506.el6_10.1), Copyright (c) 2003-2008 Fabrice Bellard
iw dev wlan0 station dump
This is very useful because it is helpful if you are running something like hostapd and need to see the signal strength and negotiated connection speed.
Station ff:ff:ff:ff:ff:ff (on wlan0)
inactive time: 16309 ms
rx bytes: 25451
rx packets: 325
tx bytes: 44381
tx packets: 159
tx retries: 0
tx failed: 0
signal: -72 [-72] dBm
signal avg: -72 [-72] dBm........
Unable to negotiate with 192.168.1.99 port 22: no matching host key type found. Their offer: ssh-dss
It looks like the DSS option is not considered secure so when connecting from newer Linux systems to an older one you will get the above error.
It can be fixed (but you should consider upgrading your SSH daemon):
ssh -oHostKeyAlgorithms=+ssh-dss firstname.lastname@example.org........
Iread this article and still don't understand the issue.
If I understand correctly the client negotiates after the first SSLconnection and then gets the correct hostname and thus correct certificate.
To their credit I know I'm not using SNIbecuase Iget this message in the Apache log :)
[warn] Init: You should not use name-based virtual hosts in conjunction with SSL!!
At first it was configured as a RAID 0, then I deleted the Virtual Disk Group.
I thought both drives would be shown and detected in Linux as sda and sdb but it actually shows nothing.
To make them work you have to hit Ctrl+R before the system boots (when prompted) and create a Virtual Disk Group. In my case I created each one as RAID 0 (with a single drive only) as I just wanted JBOD but there is no such option or default in these Dell Pe........
This is the Intel Atom 330 motherboard with integrated Realtek Gigabit NIC (Intel Desktop Board D945GCLF2 Motherboard W/ Atom 330 1.6 GHz Dual Core Processor - Mini-ITX)
I cannot achieve more than 15 MB/s, even doing a local transfer through eth0 to it's own IP.
100% 95MB 15.9MB/s 00:06
So this is not a cabling, switch or hardware issue, it seems like a driver or chipset limitation problem.
Here is my........