Maximum number of bridges limited to 4. Why?


oby-1k

Networkin' Nut
Member
I'm trying to create additional VLans on my network, but it seems FT has a limitation of maximum 4 bridges in the basic-network.asp page.

I understand this is a hardcoded limitation from the asp code itself as pictured below, but is there any reason this number of bridges has been hardcoded? Hardware limitations maybe?

I'd think that having up to 8 would be congruent with the maximum number of physical + virtual Wireless you can implement in FT so each Wifi can be mapped to an independent bridge.

1620077148032.png

Workaround for me is to implement additional AP in the network so I can overcome this limitation and having APs bridged to different VLans, but I was wondering the reason behind this value.

I'm clear this is not a common use case for home usage, but just wanted to raise the question.

Thank you!
 
Last edited:

Sean B.

LI Guru
Member
I'm trying to create additional VLans on my network, but it seems FT has a limitation of maximum 4 bridges in the basic-network.asp page.

I understand this is a hardcoded limitation from the asp code itself as pictured below, but is there any reason this number of bridges has been hardcoded? Hardware limitations maybe?

I'd think that having up to 8 would be congruent with the maximum number of physical + virtual Wireless you can implement in FT so each Wifi can be mapped to an independent bridge.

View attachment 8883

Workaround for me is to implement additional AP in the network so I can overcome this limitation and having APs bridged to different VLans, but I was wondering the reason behind this value.

I'm clear this is not a common use case for home usage, but just wanted to raise the question.

Thank you!
I would assume it's less of a "limit" and more for consistency and prioritizing.

A. Not all routers support virtual interfaces.

B. 4 ports, 4 VLAN's. It's a logical end point for a convenience feature such as this in the GUI.

C. Someone that needs/uses/knows how to properly configure VIF's and VLANs to use with them, can likely handle the shell commands to do it as well.
 

rs232

Super Moderator
Staff member
I also would like to add, for every bridge there are a number of NVRAM variables named after the bridge itself e.g. for br0:

Code:
bwl_br0_prio
bwl_br0_ulc
bwl_br0_ulr
bwl_br0_udp
bwl_br0_tcp
bwl_br0_dlc
bwl_br0_dlr
limit_br0_prio
bwl_br0_enable

It seems like most of them are linked to bandwidth limit or QoS. Any ways, assuming a user will use bandwidth limit it might be a big hit on on NVRAM demand especially on MIPS devices.
 

oby-1k

Networkin' Nut
Member
Thank you all, yes I guess it's for convenience and nvram limitations.

Will see what I can do with additional APs to overcome this.
 

Top