[PATCH 2/3] bhyve: increase number of supported consoles to 4

2025-07-13 Thread Roman Bogorodskiy
Recent versions of bhyve support 4 com ports instead of just 2. Thus, allow to use 4 console devices. Also, there was a bug previously because the condition was "if (chr->target.port > 2)", but as target.port start with 0 and "com" ports start with 1, this condition allows com3 to be used. As bhy

[PATCH 3/3] docs: drvbhyve: document TCP console support

2025-07-13 Thread Roman Bogorodskiy
Signed-off-by: Roman Bogorodskiy --- docs/drvbhyve.rst | 19 +++ 1 file changed, 19 insertions(+) diff --git a/docs/drvbhyve.rst b/docs/drvbhyve.rst index 7eec4a2123..2ecd1358a3 100644 --- a/docs/drvbhyve.rst +++ b/docs/drvbhyve.rst @@ -619,3 +619,22 @@ Example:

[PATCH 1/3] bhyve: support serial type 'tcp'

2025-07-13 Thread Roman Bogorodskiy
In addition to the nmdm consoles, bhyve also supports a tcp console. It's configured with: .. -l com1,tcp=127.0.0.1:12345 Then a user could connect to the guest console port 0 by making a tcp connection to the host's 127.0.0.1:12345. In the domain XML this configuration is represented as:

[PATCH 0/3] bhyve: TCP console support

2025-07-13 Thread Roman Bogorodskiy
Roman Bogorodskiy (3): bhyve: support serial type 'tcp' bhyve: increase number of supported consoles to 4 docs: drvbhyve: document TCP console support docs/drvbhyve.rst | 19 ++ src/bhyve/bhyve_capabilities.c| 3 +- src/bhyve/bhyve_command.c

[PATCH v2 0/1] network: introduce Packet Filter firewall backend

2025-07-13 Thread Roman Bogorodskiy
Changes since v1: - Left only firewall backend changes - Build network_pf.c only on FreeBSD - pfAddIPSpecificFirewallRules: error message for lack of IPv6 support I have also added a basic docs/drvnetwork.rst, but I think it would make more sense to include it in the follow up series with the

[PATCH v2 1/1] network: introduce Packet Filter firewall backend

2025-07-13 Thread Roman Bogorodskiy
Implement NAT networking support based on the Packet Filter (pf) firewall in FreeBSD. At this point, the implementation is very basic. It creates: - Essential NAT translation rules - Basic forwarding rules Implementation uses pf's anchor feature to group rules. All rules live in the "libvirt" a