I recently configured a Pi3B+ like you describe/want, but not in bridge-mode but routed-mode. (I just wanted a method and backup internet to prove that some regional government website is not accessible via my fiber internet, but works via 4G.)
For a downlink WiFi<->Ethernet link, broadcast packages get lost because normal WiFi chipsets drop those for those case. So you should not create a bridge (OSI layer2) but a OSI Layer3 connection with special routing and broadcast relay setup. I wanted to experience that, it worked, but too complicated to maintain. So I just created a normal routing solution, which then need 2 IP addresses in the Pi and a DHCP server on the Ethernet side. If you want help, you should post various details, I use only IPv4, info needed:
ip a ?
ip r ?
forwarding flag?
firewall/NAT rules?
I have a serial console cable connected to that Pi3B+, but I assume you have HDMI+keyboard. ssh/remote should work, but tricky if you are managing IP networking via that same ssh connection. I could reach 28Mbps DL / 2Mbps UL, it was slow 4G networking at time of testing.
For a downlink WiFi<->Ethernet link, broadcast packages get lost because normal WiFi chipsets drop those for those case. So you should not create a bridge (OSI layer2) but a OSI Layer3 connection with special routing and broadcast relay setup. I wanted to experience that, it worked, but too complicated to maintain. So I just created a normal routing solution, which then need 2 IP addresses in the Pi and a DHCP server on the Ethernet side. If you want help, you should post various details, I use only IPv4, info needed:
ip a ?
ip r ?
forwarding flag?
firewall/NAT rules?
I have a serial console cable connected to that Pi3B+, but I assume you have HDMI+keyboard. ssh/remote should work, but tricky if you are managing IP networking via that same ssh connection. I could reach 28Mbps DL / 2Mbps UL, it was slow 4G networking at time of testing.
Statistics: Posted by redvli — Tue Aug 06, 2024 3:26 pm
