Here We are trying to configure multiple VLAN on single physical port. We bridged all those VLAN interfaces.So, Whenever configured end to end ping is not working because multiple ARP packets are generated by device.
For Suppose, My PC ipaddr is 192.168.5.55 with vlan 55 and My device ipaddr is 192.168.5.2 with Vlans 55,65,75 and they are connected through Switch. Whenever My PC is sending ARP Broadcast Packet with Vlan 55, my device is also sending Replicated ARP broadcast request with same src and dest but different VLAN such as 65, 75 to switch. Due to Replication switch is blocking the arp replies as it doesnot understand where 5.2 device is connected.
This is not from the Official OpenWrt project. Please reach out to the vendor of the device and/or the maintainer of the fork that you are using for assistance.
We downloaded openwrt snapshot, but we want to download openwrt 23.05 released version source code. Could you please share us the link to the repository?
Look, it's not forbidden to search for it yourself. It's really not hidden and it would have taken you fewer key strokes to search for- and find it, than typing either your inquiry or my response.
Hi,
we have build openwrt 23.05 snapshot version. we are able to load the final image into the sama5d2 xpalined board. we have configured vlan. but we are seeing the same problem we faced in 19.07 version.
but when we tested the official binary of 23.05.2 as you suggested earlier it was working fine.
what could be the difference? is there any package that need to be selected for proper operation of vlan?
root@OpenWrt:/# ubus call system board
{
"kernel": "5.15.147",
"hostname": "OpenWrt",
"system": "ARMv7 Processor rev 1 (v7l)",
"model": "Atmel SAMA5D2 Xplained",
"board_name": "atmel,sama5d2-xplained",
"rootfs_type": "ext4",
"release": {
"distribution": "OpenWrt",
"version": "23.05-SNAPSHOT",
"revision": "r23719-72421d973e",
"target": "at91/sama5",
"description": "OpenWrt 23.05-SNAPSHOT r23719-72421d973e"
}
}
root@OpenWrt:/# cat /etc/config/network
config interface 'loopback'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
option device 'lo'
config interface 'lan'
option type 'none'
option proto 'static'
option ipaddr '193.168.1.52'
option netmask '255.255.255.0'
option gateway '193.168.1.1'
option device 'br-lan'
config interface 'debug'
option type 'none'
option proto 'static'
option ipaddr '172.18.0.18'
option netmask '255.255.255.0'
option device 'usb0'
config device
option type '8021q'
option ifname 'eth0'
option vid '55'
option name 'eth0.55'
option ipv6 '0'
option macaddr 'FC:C2:3D:0B:B2:E5'
option mtu '1500'
config device
option type '8021q'
option ifname 'eth0'
option vid '65'
option name 'eth0.65'
option mtu '1500'
option macaddr 'FC:C2:3D:0B:B2:E5'
option ipv6 '0'
config device
option type 'bridge'
option name 'br-lan'
list ports 'eth0'
list ports 'eth0.55'
list ports 'eth0.65'
option bridge_empty '1'
option mtu '1500'
option macaddr 'FC:C2:3D:0B:B2:E5'
option ipv6 '0'
root@OpenWrt:/#
Moved to the developer section since the OP is building from source.
@admin1 - are you making modifications of the source code that you download, or are you just doing a straight compile? If there are changes, you'll need to describe what those changes are and why. If it's a straight compile, it would be good to download the snapshot as available on the firmware-selector page to see if it works properly.
No, We are not making modifications to the source code. We downloaded snapshot, only selected luci for http access that's it and compiling staright. As you mentioned, the configurations are wrong were not configured by us. We just configured vlan though luci HTTP.
But where did this bridge stanza come from? Did you configure it? It is entirely invalid and will cause problems.
A bridge is the software equivalent of an unmanaged hardware switch. It must only ever have a single network/VLAN associated with it -- here there are three. This should not have worked in any version of OpenWrt... if it did work in a previous experiment, it is likely that the testing was not sufficiently detailed as to reveal the problems that this will present.