friwall/web/templates/base.html

<!DOCTYPE html>
<html>
<meta charset="utf-8" />

<style>
body {
    hyphens: auto;
    max-width: 66em;
    margin: 1em auto;
}
code {
    background-color: #f8f8f8;
    padding: 0.1em 0.25em;
}
details {
    margin: 0.5em 1em;
}
details > summary {
    cursor: pointer;
}
details  > p {
    margin: 0.5em;
}
h1 {
    margin-bottom: 0.5em;
}
h1 > a {
    color: unset;
    text-decoration: none;
}
input:read-only {
    border-style: dotted;
}
pre {
    background-color: #f8f8f8;
    border: 1px solid #cccccc;
    padding: 0.5em;
}
table {
    border-spacing: 0 0.1em;
}
th {
    text-align: left;
}
th, td {
    padding-right: 1em;
    vertical-align: middle;
}
tbody > tr:hover {
    background-color: #f8f8f8;
}
ul.keys {
    margin: 0 0.5em 0.5em;
    padding-left: 1em;
}
ul.keys a {
    text-decoration: none;
}
</style>

{% block header %}{% endblock %}

<title>FRIwall</title>

{% if current_user.is_authenticated %}
<div style="float:right;">
{{ current_user['username'] }} |
<a href="{{ url_for('logout') }}">Odjava</a>
</div>
{% endif %}

<h1><a href="/">FRIwall</a></h1>

{% block content %}{% endblock %}
Make a squash 2022-01-03 10:33:02 +00:00			`<!DOCTYPE html>`
			`<html>`
			`<meta charset="utf-8" />`

			`<style>`
			`body {`
			`hyphens: auto;`
			`max-width: 66em;`
			`margin: 1em auto;`
			`}`
			`code {`
vpn: add support for custom keys Custom keys are created by admin and specify networks directly, bypassing AD permissions. They are intended to join managed devices into networks where users are not allowed to create keys themselves. Also comprehend a set directly. 2024-07-30 08:53:57 +00:00			`background-color: #f8f8f8;`
			`padding: 0.1em 0.25em;`
Make a squash 2022-01-03 10:33:02 +00:00			`}`
			`details {`
			`margin: 0.5em 1em;`
			`}`
			`details > summary {`
			`cursor: pointer;`
			`}`
			`details > p {`
			`margin: 0.5em;`
			`}`
			`h1 {`
			`margin-bottom: 0.5em;`
			`}`
			`h1 > a {`
			`color: unset;`
			`text-decoration: none;`
			`}`
Consolidate NAT and VPN settings into IP sets I have tried every possible permutation and I think this is the one. NetBox-managed IP prefixes are pushed with ansible to firewall master. The managed prefixes are added to custom IP sets defined in the app, but only NAT addresses and VPN groups can be configured for them. This way all NAT and VPN policy is (again) configured in the app. Also both NetBox-managed and user-defined networks are treated the same. Also improve^Wtweak config generation. Also templates. 2024-04-30 13:13:50 +00:00			`input:read-only {`
			`border-style: dotted;`
			`}`
Make a squash 2022-01-03 10:33:02 +00:00			`pre {`
vpn: add support for custom keys Custom keys are created by admin and specify networks directly, bypassing AD permissions. They are intended to join managed devices into networks where users are not allowed to create keys themselves. Also comprehend a set directly. 2024-07-30 08:53:57 +00:00			`background-color: #f8f8f8;`
Add some words to templates Also some tags. Also remove some other words and some other tags. 2024-05-02 21:33:13 +00:00			`border: 1px solid #cccccc;`
Make a squash 2022-01-03 10:33:02 +00:00			`padding: 0.5em;`
			`}`
vpn: add support for custom keys Custom keys are created by admin and specify networks directly, bypassing AD permissions. They are intended to join managed devices into networks where users are not allowed to create keys themselves. Also comprehend a set directly. 2024-07-30 08:53:57 +00:00			`table {`
			`border-spacing: 0 0.1em;`
			`}`
Add form for editing ipsets 2023-07-24 13:45:45 +00:00			`th {`
			`text-align: left;`
			`}`
			`th, td {`
			`padding-right: 1em;`
vpn: add support for custom keys Custom keys are created by admin and specify networks directly, bypassing AD permissions. They are intended to join managed devices into networks where users are not allowed to create keys themselves. Also comprehend a set directly. 2024-07-30 08:53:57 +00:00			`vertical-align: middle;`
Add form for editing ipsets 2023-07-24 13:45:45 +00:00			`}`
vpn: add support for custom keys Custom keys are created by admin and specify networks directly, bypassing AD permissions. They are intended to join managed devices into networks where users are not allowed to create keys themselves. Also comprehend a set directly. 2024-07-30 08:53:57 +00:00			`tbody > tr:hover {`
			`background-color: #f8f8f8;`
Consolidate NAT and VPN settings into IP sets I have tried every possible permutation and I think this is the one. NetBox-managed IP prefixes are pushed with ansible to firewall master. The managed prefixes are added to custom IP sets defined in the app, but only NAT addresses and VPN groups can be configured for them. This way all NAT and VPN policy is (again) configured in the app. Also both NetBox-managed and user-defined networks are treated the same. Also improve^Wtweak config generation. Also templates. 2024-04-30 13:13:50 +00:00			`}`
Make a squash 2022-01-03 10:33:02 +00:00			`ul.keys {`
			`margin: 0 0.5em 0.5em;`
			`padding-left: 1em;`
			`}`
			`ul.keys a {`
			`text-decoration: none;`
			`}`
			`</style>`

Consolidate NAT and VPN settings into IP sets I have tried every possible permutation and I think this is the one. NetBox-managed IP prefixes are pushed with ansible to firewall master. The managed prefixes are added to custom IP sets defined in the app, but only NAT addresses and VPN groups can be configured for them. This way all NAT and VPN policy is (again) configured in the app. Also both NetBox-managed and user-defined networks are treated the same. Also improve^Wtweak config generation. Also templates. 2024-04-30 13:13:50 +00:00			`{% block header %}{% endblock %}`

Make a squash 2022-01-03 10:33:02 +00:00			`<title>FRIwall</title>`

			`{% if current_user.is_authenticated %}`
			`<div style="float:right;">`
			`{{ current_user['username'] }} \|`
Switch to OIDC authentication 2023-09-06 12:28:06 +00:00			`<a href="{{ url_for('logout') }}">Odjava</a>`
Make a squash 2022-01-03 10:33:02 +00:00			`</div>`
			`{% endif %}`

			`<h1><a href="/">FRIwall</a></h1>`

			`{% block content %}{% endblock %}`