tap interfaces disabled in linux bridge - Carrier (IFF_RUNNING)
https://serverfault.com/questions/540831/tap-interfaces-always-disabled-in-linux-bridge
tap interfaces always disabled in linux bridge
I have a physical interface eth0, and I want to create two virtual interfaces and bridge them with eth0. For this purpose I do:#Create the virtual interfaces
tunctl -t tap0
tunctl -t tap1
ifconfig tap0 up
ifconfig tap1 up
#Create the bridge
brctl addbr br0
brctl stp br0 off
brctl addif br0 eth0
brctl addif br0 tap0
brctl addif br0 tap1
#Turning up the bridge
ifconfig br0 up
However my problem if that the tap interfaces always appear disabled in the bridge, and no traffic flows to them.
$brctl show br0
bridge name bridge id STP enabled interfaces
br0 8000.080027cabeba no eth2
tap0
tap1
$brctl showstp br0
br0
bridge id 8000.080027cabeba
designated root 8000.080027cabeba
root port 0 path cost 0
max age 20.00 bridge max age 20.00
hello time 2.00 bridge hello time 2.00
forward delay 15.00 bridge forward delay 15.00
ageing time 300.01
hello timer 0.00 tcn timer 0.00
topology change timer 0.00 gc timer 298.42
flags
eth2 (1)
port id 8001 state forwarding
designated root 8000.080027cabeba path cost 4
designated bridge 8000.080027cabeba message age timer 0.00
designated port 8001 forward delay timer 12.97
designated cost 0 hold timer 1.24
flags
tap0 (2)
port id 8002 state disabled
designated root 8000.080027cabeba path cost 100
designated bridge 8000.080027cabeba message age timer 0.00
designated port 8002 forward delay timer 0.00
designated cost 0 hold timer 0.00
flags
tap1 (3)
port id 8003 state disabled
designated root 8000.080027cabeba path cost 100
designated bridge 8000.080027cabeba message age timer 0.00
designated port 8003 forward delay timer 0.00
designated cost 0 hold timer 0.00
flags
Is there any way to set the tap interfaces in forwarding state? I do not understand why they are not because STP is disabled.
Cheers
Daniel
==========================================================================================Answer
Carrier (IFF_RUNNING) is only set on a tap when a user has the device handle open.
For a persistent tap created with tunctl, you need an application which attaches to the tap, eg:
http://blog.csdn.net/ztguang/article/details/72890346
【推荐】国内首个AI IDE,深度理解中文开发场景,立即下载体验Trae
【推荐】编程新体验,更懂你的AI,立即体验豆包MarsCode编程助手
【推荐】抖音旗下AI助手豆包,你的智能百科全书,全免费不限次数
【推荐】轻量又高性能的 SSH 工具 IShell:AI 加持,快人一步
· 基于Microsoft.Extensions.AI核心库实现RAG应用
· Linux系列:如何用heaptrack跟踪.NET程序的非托管内存泄露
· 开发者必知的日志记录最佳实践
· SQL Server 2025 AI相关能力初探
· Linux系列:如何用 C#调用 C方法造成内存泄露
· 无需6万激活码!GitHub神秘组织3小时极速复刻Manus,手把手教你使用OpenManus搭建本
· Manus爆火,是硬核还是营销?
· 终于写完轮子一部分:tcp代理 了,记录一下
· 别再用vector<bool>了!Google高级工程师:这可能是STL最大的设计失误
· 单元测试从入门到精通