Hi
user
Admin Login:
Username:
Password:
Name:
Automated firewall testing
--client
lca
--show
lca2019
--room c2 14610 --force
Next: 13 Clockwork: Programming with rules
show more...
Marks
Author(s):
Kristof Provost
Location
C2
Date
jan Mon 21
Days Raw Files
Start
14:25
First Raw Start
14:15
Duration
0:20:0
Offset
0:09:57
End
14:45
Last Raw End
15:15
Chapters
00:00
0:17:55
Total cuts_time
18 min.
https://2019.linux.conf.au/schedule/presentation/257/
raw-playlist
raw-mp4-playlist
encoded-files-playlist
host
archive
public
tweet
mp4
svg
png
assets
release.pdf
Automated_firewall_testing.json
logs
Admin:
episode
episode list
cut list
raw files day
marks day
marks day
image_files
State:
---------
borked
edit
encode
push to queue
post
richard
review 1
email
review 2
make public
tweet
to-miror
conf
done
Locked:
clear this to unlock
Locked by:
user/process that locked.
Start:
initially scheduled time from master, adjusted to match reality
Duration:
length in hh:mm:ss
Name:
Video Title (shows in video search results)
Emails:
email(s) of the presenter(s)
Released:
has someone authorised pubication
Unknown
Yes
No
Normalise:
Channelcopy:
m=mono, 01=copy left to right, 10=right to left, 00=ignore.
Thumbnail:
filename.png
Description:
markdown
We're all convinced that automated tests are a good idea. For some applications (e.g. grep, awk, cc, ...) this is very straightforward. Others are a lot harder to test, for example firewalls. Typically testing firewalls takes two to three hosts. One to send traffic, the firewall test host and one to receive traffic. This makes automated test orchestration complex and brittle. This in turn means that tests either don't get written, are difficult to write and/or suffer random failures unrelated to issues in the firewall itself. Virtualisation has made this all somewhat easier, but it's still fiddly and difficult to make robust. It's also slow. The new FreeBSD network stack virtualisation lets us build on the existing jails system to build test setups, execute tests and clean up in mere seconds, without any requirement for additional hardware, or even hardware virtualisation support.
Comment:
production notes
2019-01-21/14_15_03.ts
Apply:
14:15:03 - 14:25:28 ( 00:10:25 )
S:
14:15:03 -
E:
14:45:03
D:
00:30:00
(
End:
625.0)
show more...
vlc ~/Videos/veyepar/lca/lca2019/dv/c2/2019-01-21/14_15_03.ts :start-time=00.0 --audio-desync=0
Raw File
Cut List
14:15:03
seconds: 0.0
Wall: 14:15:03
Duration
00:30:00
14:45:03
seconds: 625.0
Wall: 14:25:28
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2019-01-21/14_15_03.ts
Apply:
14:25:28 - 14:43:23 ( 00:17:55 )
S:
14:15:03 -
E:
14:45:03
D:
00:30:00
(
Start:
625.0) (
End:
1700)
show more...
vlc ~/Videos/veyepar/lca/lca2019/dv/c2/2019-01-21/14_15_03.ts :start-time=0625.0 --audio-desync=0
Raw File
Cut List
14:15:03
seconds: 625.0
Wall: 14:25:28
Duration
00:30:00
14:45:03
seconds: 1700.0
Wall: 14:43:23
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
2019-01-21/14_45_03.ts
Apply:
14:45:03 - 14:45:29 ( 00:00:26 )
S:
14:45:03 -
E:
15:15:02
D:
00:29:59
(
End:
26.558145)
show more...
vlc ~/Videos/veyepar/lca/lca2019/dv/c2/2019-01-21/14_45_03.ts :start-time=00.0 --audio-desync=0
Raw File
Cut List
14:45:03
seconds: 0.0
Wall: 14:45:03
Duration
00:29:59
15:15:02
seconds: 26.558145
Wall: 14:45:29
Comments:
mp4
mp4.m3u
dv.m3u
Split:
Sequence:
:
delete
Rf filename:
root is .../show/dv/location/, example: 2013-03-13/13:13:30.dv
Sequence:
get this:
check and save to add this
2019-01-21/14_15_03.ts
2019-01-21/14_45_03.ts
Veyepar
Video Eyeball Processor and Review
