-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Description
Is there an existing issue for this?
- I have searched among all existing issues (including closed issues)
Issue Summary
Q: What am I trying to do?
I'd like my new "OpenWrt One" to act as a simple Wireless Access Point for the "wan", my home network. I'd also like to keep the other configuration near the same, so that connecting directly to the device via the "lan" port can be used for configuration.
Q: What happened?
The /etc/config/network section of the wan interface to use br-wan bridge incorrectly included option type 'bridge' in config interface 'wan'.
Q: What is your expertise/knowledge?
I have only basic network experience. This issue was identified by ChatGPT when I wrote the goal, documented what I did, and I pasted configuration. ChatGPT suggested removal of these two lines and this suggestion worked. Sadly, this entire chat was lost, or I'd paste it; but most of it was useless boilerplate and regurgitated blog slop.
Speaking of which, so that "OpenWRT Two" can be more easily used by causal users, it'd be helpful if there were a toggle switch on front that would let us pick between standard AP, router, and "open the hood" custom behavior. Another switch to open vs lock configuration might also be nice, only when this switch is open would ssh be open, https interface could be read only when switch is closed.
screenshots or captures
Here are screenshots, but I'm not sure how useful they may be.
...
Actual behaviour
The configuration for changing the wan interface to use br-wan bridge included option type 'bridge' in config interface 'wan'
root@wap_west:~# cat /etc/config/network
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fdbe:16df:63ee::/48'
option packet_steering '1'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth1'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
config interface 'wan'
option device 'br-wan'
option proto 'dhcp'
option type 'bridge'
config interface 'wan6'
option device 'br-wan'
option proto 'dhcpv6'
option type 'bridge'
option reqaddress 'try'
option reqprefix 'auto'
option norelease '1'
config device
option type 'bridge'
option name 'br-wan'
list ports 'eth0'
Expected behaviour
I think option type 'bridge' may be in error. When I remove those two lines, things work.
root@wap_west:~# cat /etc/config/network
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fdbe:16df:63ee::/48'
option packet_steering '1'
config device
option name 'br-lan'
option type 'bridge'
list ports 'eth1'
config device
option type 'bridge'
option name 'br-wan'
list ports 'eth0'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '192.168.1.1'
option netmask '255.255.255.0'
option ip6assign '60'
config interface 'wan'
option device 'br-wan'
option proto 'dhcp'
config interface 'wan6'
option device 'br-wan'
option proto 'dhcpv6'
option reqaddress 'try'
option reqprefix 'auto'
option norelease '1'
Steps to reproduce
- Go to Network -> Wireless
- Create/Edit an
Access Pointwireless interface that useswanandwan6networks. - Go to Network -> Devices
- Create a
Bridge devicecalledbr-wan. - Go to Network->Interfaces
- Edit
wanto usebr-wandevice. - Note that
config interface 'wan'section of/etc/config/networkhas a lineoption type 'bridge'.
Additional Information
{
"kernel": "6.6.110",
"hostname": "wap_west",
"system": "ARMv8 Processor rev 4",
"model": "OpenWrt One",
"board_name": "openwrt,one",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "24.10.4",
"revision": "r28959-29397011cc",
"target": "mediatek/filogic",
"description": "OpenWrt 24.10.4 r28959-29397011cc",
"builddate": "1760891865"
}
}What browsers do you see the problem on?
No response