When I use BGP technology, the virtual machine cannot connect to external gateways and networks

When I set the configuration of a bridge network as follows:

incus network show dzn-test
  bgp.peers.myfrr.asn: "398765"
  ipv4.nat: "false"
  ipv6.address: fd42:fa1e:7602:e69e::1/64
  ipv6.nat: "true"
description: ""
name: dzn-test
type: bridge
- /1.0/instances/dzn-bri
managed: true
status: Created
- hci01

The key attributes are ipv.nat=false,in which the virtual machine can access the host, but cannot access the host gateway and www.google.com.

The reason why I set ipv4.nat=false is to use Incus’s BGP technology,here are the settings for my incus cluster

What does FRR see as far as received routes?

This is my FRR configuration:


This is my FRR received routes:

This is my FRR ip routes:


Cant the frr system ping

Of course, the FRR system can ping, as well as ping the addresses of virtual machines such as

Okay, so things are working as intended then.

Incus is advertising its network to your FRR router, that router received the route and properly put it in its routing table, allowing it to reach the instances running on Incus.

It sounds like your FRR router isn’t your primary router though, as that is at whereas your primary router likely is at

So your problem seems to be that your primary router itself isn’t aware of that subnet and how to route to it, which is then why your VMs can properly interact with their host as well as with but not with or anything behind it (the global internet).

How should I set up or have any method to enable my VMs to communicate with or anything behind it (the global internet)?

Well, normally you’d want your router to run BGP so it can receive the routes.

If that’s not an option, then the whole BGP thing isn’t all that useful to you as you’d need to put a static route in place on your router.

Do you mean that I should add static routing on the main router of or the BGP router of

The main router.

Your BGP router doesn’t do anything as far as I can tell.
It does receive the routes from Incus but because it’s not the actual router for your network, it knowing the route to Incus doesn’t really do anything. You need your actual router to know how to route to Incus.