Rocky Linux 9.2 KVM bridging issue - pfSense not passing connectivity.

binbashtesting

Hi,

It's been a pain in the A for a while now so decided to ask community how to properly configure it. In my case it works on occasions ( mostly not working and I was unable to id the problem )
there is no prblems on Centos7 but I need to start using Rocky linux. I configured my bridging with nmcli

My bridges
br0 (external ) with slave eno1
br1 ( internal ) -> VMs

 brctl show
bridge name     bridge id               STP enabled     interfaces
br0             8000.d094666923a9       yes             eno1
                                                     vnet0
br1             8000.fe5400f2ea33       yes             vnet1
docker0         8000.0242a350a792       no
virbr0          8000.5254005f9d2f       yes

# ip link show | grep master
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master br0 state UP mode DEFAULT group default qlen 1000
11: vnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 state UNKNOWN mode DEFAULT group default qlen 1000
12: vnet1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br1 state UNKNOWN mode DEFAULT group default qlen 1000

face             MTU    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
br0              1500    31242      0      0 0          3548      0      0      0 BMRU
br1              1500     7242      0      0 0          7251      0      0      0 BMRU
docker0          1500        0      0      0 0             0      0      0      0 BMU
eno1             1500    34041      0      0 0          3895      0      0      0 BMRU

pfsense vnet's are assigned to correct bridge but I'm not even able to ping from pfsense shell to WAN net or any LAN host ip (pfctl -d also no good).
virt-manager ip address would be set to unknown despite it's visible from shell and I can reach it from the KVM host.

rocky ~]# curl -v 10.20.38.228
*   Trying 10.20.38.228:80...
* Connected to 10.20.38.228 (10.20.38.228) port 80 (#0)
> GET / HTTP/1.1
> Host: 10.20.38.228
> User-Agent: curl/7.76.1
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
< Server: nginx
< Date: Tue, 03 Oct 2023 11:29:35 GMT
< Content-Type: text/html; charset=UTF-8

Also I have no idea why would it work on occasions, perhaps docker is messing it up; anyone using pfsense on Rocky linux with similar combination ?