Problem with configuring bridge interface (stopped working after device change)

B

bsu

New Member
Sep 8, 2020
3
0
1
55
Hello,
as said in the topic. It was running before I had to take the server to another place where I cannot connect the machine to the network via cable (now its wireless adapter). Yes, I know, don't laugh at me, it's only my private testing machine :)
So, interfaces:
- vmbr0 - bridge interface
- wlxd037452259c0 - wireless adapter
Command results:
1. ip a
Code: 
2: eno1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 74:46:a0:90:d1:35 brd ff:ff:ff:ff:ff:ff
3: enp1s0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 74:46:a0:90:d1:36 brd ff:ff:ff:ff:ff:ff
8: wlxd037452259c0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master vmbr0 state DOWN group default qlen 1000
    link/ether d0:37:45:22:59:c0 brd ff:ff:ff:ff:ff:ff
11: vmbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
    link/ether d0:37:45:22:59:c0 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.200/24 brd 192.168.0.255 scope global vmbr0
       valid_lft forever preferred_lft forever

2. /etc/network/interfaces (config is exactly the same as in the docs: https://pve.proxmox.com/wiki/Network_Configuration)
Code: 
auto lo
iface lo inet loopback

iface wlxd037452259c0 inet manual

auto vmbr0
iface vmbr0 inet static
    address 192.168.0.200
    netmask 255.255.255.0
    gateway 192.168.0.1
    bridge_ports wlxd037452259c0
    bridge_stp off
    bridge_fd 0

3. brctl show
Code: 
bridge name    bridge id        STP enabled    interfaces
vmbr0        8000.7446a090d135    no        wlxd037452259c0

4. journalctl -u networking.service
Code: 
Sep 08 22:55:40 proxmox systemd[1]: Stopping Raise network interfaces...
Sep 08 22:55:41 proxmox systemd[1]: networking.service: Succeeded.
Sep 08 22:55:41 proxmox systemd[1]: Stopped Raise network interfaces.
Sep 08 22:55:41 proxmox systemd[1]: Starting Raise network interfaces...
Sep 08 22:55:41 proxmox ifup[4374]: Waiting for vmbr0 to get ready (MAXWAIT is 2 seconds).
Sep 08 22:55:41 proxmox systemd[1]: Started Raise network interfaces.

5. /car/log/kern.log
Code: 
Sep  8 22:53:23 proxmox kernel: [  449.832306] vmbr0: port 2(wlxd037452259c0) entered blocking state
Sep  8 22:53:23 proxmox kernel: [  449.832309] vmbr0: port 2(wlxd037452259c0) entered disabled state
Sep  8 22:53:23 proxmox kernel: [  449.832406] device wlxd037452259c0 entered promiscuous mode
Sep  8 22:54:09 proxmox kernel: [  495.672893] device wlxd037452259c0 left promiscuous mode
Sep  8 22:54:09 proxmox kernel: [  495.672925] vmbr0: port 2(wlxd037452259c0) entered disabled state
Sep  8 22:54:09 proxmox kernel: [  495.700333] device eno1 left promiscuous mode
Sep  8 22:54:09 proxmox kernel: [  495.700415] vmbr0: port 1(eno1) entered disabled state
Sep  8 22:54:09 proxmox kernel: [  495.801040] vmbr0: port 1(wlxd037452259c0) entered blocking state
Sep  8 22:54:09 proxmox kernel: [  495.801044] vmbr0: port 1(wlxd037452259c0) entered disabled state
Sep  8 22:54:09 proxmox kernel: [  495.801131] device wlxd037452259c0 entered promiscuous mode

After changing location I've only changed bridge_ports in /etc/network/interface file, so I have no idea what is wrong now. I'm sure wireless adapter is working because it works when I use it directly, not via bridge.
I have no idea what those lines in kern.log mean:
- interface enters blocking/disabled state
- promiscuous mode (even turned it off on wireless interface using ip link command, didn't help)
Any ideas? :)

Regards
 
Moayad said:
Hello,
AFAIK: this message is about STP, so the bridge is blocked that means not forwarding packets see here for more details [1].
http://www.microhowto.info/troubleshooting/troubleshooting_ethernet_bridging_on_linux.html#idp36544
Click to expand...
Yup, you're right.

Stoiko Ivanov said:
Most wireless adapters cannot be used in a bridge when in station/client mode - in that case I'd consider using a routed setup:
https://pve.proxmox.com/pve-docs/chapter-sysadmin.html#_routed_configuration
Click to expand...
Thanks, it works but only in terms of machine's presence in the network. I am able to access Proxmox via GUI (on vmbr0 interface address) but the problem is that network traffic to VM's is not being routed to/from them - they are not able to ping the rest of the network and vice versa. I'm not sure if I get it. Where is the link between vmbr0 interface that VM's use and wireless adapter (i.e. bridge_ports is set to none)? It's forwarding packets but where. Or such setup needs some additional configuration? How should I set up the routing table? Currently, it's set up that all traffic goes through wireless adapter interface.
 
Problem solved but in some other way – I decided to buy a cheap router with WISP mode, that means wireless WAN and wireless/cable LAN, then plugged a cable to machine's ethernet port and then set it all up.
 
hi guys,

i solved problem change to harddisk. (For entered disable state and locking state)

i was using sata ssd

i changed nvme disk and solved.

i think sata not enough for 10 or 1 gigabit lan

sory for my bad english
 
You must log in or register to reply here.
Top Bottom