Linux

Expected behaviour

I expected the VM to come up normally, just exchanging NAT IP by bridge IP

Actual behaviour

When adding the bridge="br0" line to the conf file, when trying to start VM immediately a "Connect to SPICE" window pops up asking for Hostname, Port, TLS Port and showing recent connections that obviously now don't work anymore.

As don't know much about spice, maybe

I think it would be good to describe/list the capture technologies Wireguard is using for each platform. e.g. Windows it using wintun.net driver, Linux it is using /dev/tun etc.

Likely an advanced topic.

Hi,

Seems like I couldn't use this script to install Wireguard sucessfully on CentOS Stream 8.

I have encountered this error during execution:

Error:
 Problem: cannot install the best candidate for the job
  - nothing provides kernel(__skb_flow_dissect) = 0xd82bed9c needed by kmod-wireguard-3:1.0.20210424
  - nothing provides kernel(flow_keys_basic_dissector) = 0xa7e38f12 needed b

User Story

If a large download fails using curl it does not cause a fatal error instead it simply carries on.

Basic info

• Command: Install

Further Information

It is worth checking how all downloads handle when failing to ensure they cause a fatal exit.

To Reproduce

Use a game server that is non-steam and cause the download to fail

Expected behaviour