Skip to Content
Firewall

Firewall

PacketStream Firewall is a cloud firewall for Virtual Servers. Rules are bundled into a Firewall Group and applied to multiple servers at once, so you control inbound traffic from the web console instead of configuring iptables or UFW on each server.

How it works

  1. Define a group — Add inbound rules to a Firewall Group. Each rule specifies what to allow by protocol, port, and source IP.
  2. Apply to servers — Apply the group to a Virtual Server. One Firewall Group applies per server.
  3. Evaluate traffic — The default policy is deny. Only explicitly allowed traffic passes; everything else is dropped. Rules are evaluated in order.

Firewall is stateful. It tracks connection state, so response traffic for an allowed request passes without a separate rule. Rule additions, changes, and deletions take effect immediately.

Rule configuration

Each rule controls traffic coming from the internet to a Virtual Server. A rule has these fields:

  • Protocol — TCP, UDP, ICMP
  • Port — service port (e.g., 80, 443, 22, 3306)
  • Source — IP range allowed to connect (e.g., 0.0.0.0/0, 192.168.1.0/24)
  • Description — optional note on the rule’s purpose

Common rule examples

Inbound rule examples for commonly used services.

ServiceProtocolPortSourcePurpose
Web ServerTCP80, 4430.0.0.0/0HTTP/HTTPS access
SSHTCP22Admin IPRemote access
MySQLTCP3306App server IPDatabase access
DNSUDP530.0.0.0/0DNS queries
PingICMP-0.0.0.0/0Network diagnostics

Limits

  • Price: free
  • Firewall Groups: 10 per project, up to 50 per account
  • Rules: up to 50 per Firewall Group
  • Per server: one Firewall Group per server

Setup steps

  1. Create a Firewall Group — Create the group in the console and set its name and description. Default deny is recommended: it blocks any traffic not matched by an allow rule, reducing exposure.
  2. Add rules — Define the inbound rules you need by protocol, port, and source, and set their order.
  3. Apply to a Virtual Server — Select the Virtual Server to protect, apply the group, and verify its status.
  4. Test and monitor — Verify rule behavior and review access logs.

Next steps