BIRD raises Unexpected connect from unknown address error in bgp mode

[IterableTrucks]

I follow the Use OpenELB in BGP Mode page step by step but in step 7 the bird machine does not establish any route to bgp-svc service. And the journal of bird service tells Unexpected connect from unknown address 192.168.0.6 (port 39049).
There are 5 nodes in k8s: 192.168.0.2(master) 192.168.0.3(worker) 192.168.0.4(worker) 192.168.0.5(worker) 192.168.0.6(worker). And the openelb-manager pod is running on 192.168.0.6.
The bird service is running on the worker node at 192.168.0.3.
bgp-conf.yaml:

apiVersion: network.kubesphere.io/v1alpha2
kind: BgpConf
metadata:
  name: default
spec:
  as: 50000
  listenPort: 17900
  routerId: 192.168.0.2

bgp-peer.yaml:

apiVersion: network.kubesphere.io/v1alpha2
kind: BgpPeer
metadata:
  name: bgp-peer
spec:
  conf:
    peerAs: 50001
    neighborAddress: 192.168.0.3

bird configuration:

router id 192.168.0.3;

protocol kernel {
        scan time 60;
        import none;
        export all;   # Actually insert routes into the kernel routing table
        merge paths on;
}

protocol device {
        scan time 60;
}
protocol bgp neighbor1 {
        local as 50001;
        neighbor 192.168.0.2 port 17900 as 50000;
        source address 192.168.0.3;
        import all;
        export all;
        enable route refresh off;
        add paths on;
}

k8s version is 1.26.5
openelb version is v0.5.1

[renyunkang]

Are you using calico as cni plugin? Have you turned off calico’s bgp fullmesh?

BGP only allows one session to be established per pair of nodes. It is recommended that you use nodes outside the cluster to establish bgp connections.

[IterableTrucks]

I'm using the containernetworking-plugins v1.3.0 with cri-o as my container runtime

[renyunkang]

The openelb-manager pod is running on 192.168.0.6, so you should set the bgp peer configuration of the brid to 192.168.0.6 instead of 192.168.0.2.

[IterableTrucks]

I change the bird configuration with 192.168.0.6 as the neighboor and restart bird. The bird produces the route entry as expected. But the service bgp-svc still cannot be accessed by curl 172.22.0.2. The error is: curl: (7) Failed to connect to 172.22.0.2 port 80: no route to host.