the wlan0 and eth0 are added to the bridge with the same method, this works fine as once this is done I can ping the client connected on the ethernet interface by the client connected over wifi.
I don`t think the problem with the legato framework, as once the bridge is created I can’t ping anymore the client connected on the ethernet interface from shell:
root@fx30:~# ping 192.168.0.141 (before the eth0 and wlan0 are added to the bridge)
PING 192.168.0.141 (192.168.0.141): 56 data bytes
64 bytes from 192.168.0.141: seq=0 ttl=64 time=1.823 ms
64 bytes from 192.168.0.141: seq=1 ttl=64 time=1.222 ms
64 bytes from 192.168.0.141: seq=2 ttl=64 time=1.227 ms
root@fx30:~# ping 192.168.0.141 (after eth0 and wlan0 are added to the bridge)
PING 192.168.0.141 (192.168.0.141): 56 data bytes
(no reply…)
I am not using the legato app which connects to the client over eth0 at this stage, the eth0 is initialized to the default ip 192.168.0.31 according to the /etc/network/interfaces file.
root@fx30:~# route
Destination Gateway Genmask Flags Metric Ref Use Iface
default 100.118.214.141 0.0.0.0 UG 0 0 0 rmnet_data0
100.118.214.140 * 255.255.255.252 U 0 0 0 rmnet_data0
192.168.0.0 * 255.255.255.0 U 0 0 0 br0
192.168.2.0 * 255.255.255.0 U 0 0 0 ecm0
192.168.225.0 * 255.255.255.0 U 0 0 0 bridge0
and this shows that both interfaces are added to the bridge interface (br0):
root@fx30:~# bridge link show master br0
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0 state forwarding priority 32 cost 19
11: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0 state forwarding priority 32 cost 100
Same steps with the R14 (legato 19) and it works well:
root@fx30:~# ping 192.168.0.141 (after the bridge is created)
PING 192.168.0.141 (192.168.0.141): 56 data bytes
64 bytes from 192.168.0.141: seq=0 ttl=64 time=1.717 ms
64 bytes from 192.168.0.141: seq=1 ttl=64 time=1.771 ms
64 bytes from 192.168.0.141: seq=2 ttl=64 time=2.304 ms
64 bytes from 192.168.0.141: seq=3 ttl=64 time=2.307 ms
root@fx30:~# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
default 10.106.129.113 0.0.0.0 UG 0 0 0 rmnet_data0
10.106.129.96 * 255.255.255.224 U 0 0 0 rmnet_data0
192.168.0.0 * 255.255.255.0 U 0 0 0 br0
192.168.2.0 * 255.255.255.0 U 0 0 0 ecm0
192.168.225.0 * 255.255.255.0 U 0 0 0 bridge0
root@fx30:~# bridge link show master br0
3: eth0 state UP : <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0 state forwarding priority 32 cost 19
13: wlan0 state UP : <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 master br0 state forwarding priority 32 cost 100
I am trying to understand if this is related to some additional filtering which doesn`t allow to bridge traffic between wlan and eth, maybe some safety path which is present in the latest legato version (yocto) and not on the previous one?
Have been looking into different forums but so far have found no solution to the problem, therefore asking here hoping that someone will kindly reply to this providing indication for the possible solution…