-
Notifications
You must be signed in to change notification settings - Fork 105
Configuration
Configuration file for TempestaFW is a simple text file. The file location is passed to TempestaFW kernel module as parameter and can't be changed until the module is unloaded. See Run & stop for complete instructions.
The configuration file is C-program-like: you must define something before using it. E.g. a server group must be defined before it's first use in load balancing rules:
srv_group static {
server 10.10.0.1;
}
sched_http_rules {
match static uri prefix "/static/";
}
Configuration directives are described on TempestaFW Wiki pages and the brief description is provided as a sample configration file.
Install Tempesta FW from sources or binary packages. Don't forget to check the system requirements.
You can use this configuration file to quickly start Tempesta FW in a configuration like we've showed in the FOSDEM talk:
# cat etc/tempesta_fw.conf
listen 192.168.100.4:443 proto=https;
listen 192.168.100.4:80;
srv_group default {
server 127.0.0.1:8080 conns_n=4;
}
vhost debian {
tls_certificate /root/tempesta/etc/tfw-root.crt;
tls_certificate_key /root/tempesta/etc/tfw-root.key;
proxy_pass default;
}
cache 1;
cache_fulfill * *;
block_action attack reply;
http_chain {
-> debian;
}
192.168.100.4
is the listening IP address for Tempesta FW. Read more about this
configuration option in the
Handling clients
chapter.
This address must be resolved
from debian
host name. The host name is important for TLS SNI, so use the real
name of you machine. You can find the details how to configure Tempesta TLS
in the TLS chapter.
Note that you need to place your certificate and the private key into the
Tempesta FW configuration directory. In this case Tempesta FW was
built from sources,
so the configuration directory is located right in the tempesta/etc
directory.
You can generate
self-signed certificates with OpenSSL.
127.0.0.1:8080
is the address of the backend (upstream) server. Tempesta FW is a
pure HTTPS accelerator, so it requires some HTTP server to get content from.
Read more about backend configuration in the
Servers
chapter.
The cache options cache
and cache_fulfill
specify that all the content will
be cached by Tempesta FW. You can find the details how to configure the options
in the Caching
chapter.
In most of the cases you just need to
tempesta.sh --start
Check Run & Stop page for more instructions about the Linux settings and relative path of the startup script.
- Home
- Requirements
- Installation
-
Configuration
- Migration from Nginx
- On-the-fly reconfiguration
- Handling clients
- Backend servers
- Load Balancing
- Caching Responses
- Non-Idempotent Requests
- Modify HTTP Messages
- Virtual hosts and locations
- HTTP Session Management
- HTTP Tables
- HTTP(S) Security
- Header Via
- Health monitor
- TLS
- Virtual host confusion
- Traffic Filtering by Fingerprints
- Run & Stop
- Application Performance Monitoring
- Use cases
- Performance
- Contributing