I've been spend 2 days for this problem but not getting being solved. But in Debian Bullseye there is no problem.
Oke this is for background informaton about my problem. I've installed Debian Bookworm upgrade from Debian Bullseye in my Laptop with host Fedora 35 in VMware workstation. In my vm i use 2 virtual network as a bridge then identified as ens33 and ens36 in vm. I create bridge network in Debian Bookworm(VM) guding from this tutorial. I'm using nmcli command
From official Debian:
https://wiki.debian.org/BridgeNetworkConnections
and
https://www.cyberciti.biz/faq/how-to-ad ... -on-linux/
All those guided is work, I'm successfuly create bridge interface on my VM or Debian Bookworm. But I realized this bridge interface. I named it bridge0 only can konek to my ip address in my lan, I tried to ping google this bridge0 interface receive destionation network unreachable. This is how i setup brigde in VM:
This is my active connection:
Code: Select all
$ sudo nmcli connection show --active
[sudo] password for afiadi:
NAME UUID TYPE DEVICE
Sambungan kabel 1 d2335cdb-a578-3d3e-be00-a32570b17cf9 ethernet ens33
lxdbr0 2b8f65ba-b2d8-4a0f-b115-d9404edddba5 bridge lxdbr0
Sambungan kabel 2 6874079f-515f-3917-b7fe-31738885369a ethernet ens36
docker0 4648a17f-c225-47cd-8da8-7bdbd23566c3 bridge docker0
virbr0 b0a32516[code]
[/code]
Then I created bridge interface bridge0
Code: Select all
$ sudo nmcli connection add ifname bridge0 type bridge con-name bridge0
Koneksi 'bridge0' (1ca1e60c-7f1c-4fe4-88f4-d1387d2337b1) sukses ditambahkan.
$ sudo nmcli connection add type bridge-slave ifname ens33 master bridge0
Koneksi 'bridge-slave-ens33' (6cf8314b-103e-4f42-abd0-628e00de92e8) sukses ditambahkan.
Code: Select all
$ sudo nmcli connection modify bridge0 bridge.stp no
$ nmcli -f bridge connection show bridge0
bridge.mac-address: --
bridge.stp: tidak
bridge.priority: 32768
bridge.forward-delay: 15
bridge.hello-time: 2
bridge.max-age: 20
bridge.ageing-time: 300
bridge.group-forward-mask: 0
bridge.multicast-snooping: ya
bridge.vlan-filtering: tidak
bridge.vlan-default-pvid: 1
bridge.vlans: --
$ sudo nmcli connection down "Sambungan kabel 1"
Koneksi 'Sambungan kabel 1' sukses dinonaktifkan (path aktif D-Bus: /org/freedesktop/NetworkManager/ActiveConnection/1)
$ sudo nmcli connection up bridge0
Koneksi sukses diaktifkan (master waiting for slaves) (path aktif D-Bus: /org/freedesktop/NetworkManager/ActiveConnection/8)
$ nmcli connection show
NAME UUID TYPE DEVICE
Sambungan kabel 2 6874079f-515f-3917-b7fe-31738885369a ethernet ens36
bridge0 1ca1e60c-7f1c-4fe4-88f4-d1387d2337b1 bridge bridge0
lxdbr0 2b8f65ba-b2d8-4a0f-b115-d9404edddba5 bridge lxdbr0
docker0 4648a17f-c225-47cd-8da8-7bdbd23566c3 bridge docker0
virbr0 b0a32516-07cf-44be-841a-d8cdf0f71eb1 bridge virbr0
bridge-slave-ens33 6cf8314b-103e-4f42-abd0-628e00de92e8 ethernet ens33
Aishah 042a09d5-5e10-4e91-8037-c1fa4fd5089e wifi --
Aishah 1 e6657586-6a99-4b2e-980e-39625ea94b09 wifi --
Aishah 2 6e3df94b-2de4-4361-ad35-3c011f264a73 wifi --
Aishah 3 b13c066f-405c-43ea-9bf7-1bdcab53ff15 wifi --
Sambungan kabel 1 d2335cdb-a578-3d3e-be00-a32570b17cf9 ethernet --
$ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast master bridge0 state UP group default qlen 1000
link/ether 00:0c:29:6a:7e:cb brd ff:ff:ff:ff:ff:ff
altname enp2s1
3: ens36: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 00:0c:29:6a:7e:d5 brd ff:ff:ff:ff:ff:ff
altname enp2s4
inet 192.168.1.9/24 brd 192.168.1.255 scope global noprefixroute ens36
valid_lft forever preferred_lft forever
inet6 fe80::47f4:afe5:bc7b:b239/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 52:54:00:e0:b0:be brd ff:ff:ff:ff:ff:ff
inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0
valid_lft forever preferred_lft forever
5: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default
link/ether 02:42:2c:27:ea:68 brd ff:ff:ff:ff:ff:ff
inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
valid_lft forever preferred_lft forever
6: lxdbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether 00:16:3e:15:5c:6d brd ff:ff:ff:ff:ff:ff
inet 10.160.20.1/24 scope global lxdbr0
valid_lft forever preferred_lft forever
inet6 fd42:a02e:7c83:d83c::1/64 scope global
valid_lft forever preferred_lft forever
7: bridge0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 22:92:36:84:25:8f brd ff:ff:ff:ff:ff:ff
inet 192.168.1.5/24 brd 192.168.1.255 scope global dynamic noprefixroute bridge0
valid_lft 86331sec preferred_lft 86331sec
inet6 fe80::2280:d9bf:7329:95ff/64 scope link noprefixroute
valid_lft forever preferred_lft forever
afiadi@debian-bookworm:~$
$ sudo bridge link show
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master bridge0 state forwarding priority 32 cost 100
This after ens36 default route I delete with ip route delete default
My bridge0 still can connect to ip address in lan but always destination host unreachable if tried to ping to google.com or to internet. I don't know how to solve this problem I tried to Debian Bullseye that works perfectly and normally.. How to solve this problem so I can use bridge interface normally?
Thanks You in Advance
Best regards,
Afiadi