Devuan image in Qemu (8)
(No. 0) No. 1 No. 2 No. 3 No. 4 No. 5 No. 6 No. 7 No. 8 No. 9 No. 10 No. 11 No. 12 No. 13 No. 14
I've attempted more tentatives, all unsuccessful as yet, at running Devuan (non-Refracta) in a virtual machine.
Here are the records obtained with my https://github.com/miroR/uncenz program plus the corresponding syslog, this time.
The traces, and the syslogs, are minimally anonimized (just the MAC addresses --and IAID in the syslogs--, see my script dump_perl_repl.sh, and, today's work: dump_perl_repl_log.sh --both part of uncenz--)
I haven't run any tshark scripts of mine on these so far, hardly did I look them up in Wireshark either yet, I concentrated on what the syslog was telling me.
But I didn't figure out what was missing, and I can only post the data and turn to Devuan devs and show them, and see if this is of any help...
It could be something simple and that will be resolved soon, even by me, and it could be completely distant yet, what do I know?...
Also good to point out and the syslog shows it (only by, say, absense of previous, " denied " lines), that I was tweaking some grsecurity RBAC policies settings, but I can't expand on that. It's all too extensive to arrive anywhere with that yet.
Apparently out of place, because it belongs, by the timestamp, in the previous page, this is the syslog when I ran Refracta in virtual machine:
But it's for comparison.
I haven't however been able to figure out much (yet) from comparing of that working Refracta image with the failing attempts of mine below...
My endurance is at end for this (investigating it the whole day, well a couple of hours on: MAC/IAID anonymization for syslog), but maybe some of the devs could get a clue from them.
And I am only just posting them...
Also there weren't any SSL conversations at all. I simply couldn't connect the Devuan VM to the internet at all.
Also, read here: default live Devuan username and password not easily available? where I got the qcow2 image from, and understand that the minor initial issue, has been solved in the first session below.
So, here we go, by the timestamp.
This is the syslog:
messages_170224_1325_g0n---
So, here we go, by the timestamp.
This is the syslog:
messages_170224_1327_g0n---
So, here we go, by the timestamp.
This is the syslog:
messages_170224_1401_g0n---
So, here we go, by the timestamp.
This is the syslog:
messages_170224_1429_g0n---
So, here we go, by the timestamp.
This is the syslog:
messages_170224_1524_g0n---
The files necessary for this study are listed in:
messages_170217_2231_g0n Screen_170224_1325_g0n.webm messages_170224_1325_g0n dump_170224_1325_g0n.pcap Screen_170224_1327_g0n.webm messages_170224_1327_g0n dump_170224_1327_g0n.pcap Screen_170224_1401_g0n.webm messages_170224_1401_g0n dump_170224_1401_g0n.pcap Screen_170224_1429_g0n.webm messages_170224_1429_g0n dump_170224_1429_g0n.pcap Screen_170224_1524_g0n.webm messages_170224_1524_g0n dump_170224_1524_g0n.pcapand verify to: ls-1pg8.sum signed by: ls-1pg8.sum.asc
You might find dump_dlo.sh script from my uncenz program more useful then downloading each file separately.