Internet Bridge not working about tinycheck

[jgee090]

Had the same issue, this worked for me

sudo apt install iptables-persistent -y

sudo iptables -F
sudo iptables -A INPUT -p tcp --tcp-flags ALL NONE -j DROP
sudo iptables -A INPUT -p tcp ! --syn -m state --state NEW -j DROP
sudo iptables -A INPUT -p tcp --tcp-flags ALL ALL -j DROP
sudo iptables -A INPUT -i lo -j ACCEPT

sudo iptables-save >/etc/iptables/rules.v4
sudo ip6tables-save >/etc/iptables/rules.v6

[fixpc82]

Hello everyone. I made the changes you indicated but they continue to not connect

tinycheck correctly generates the Wi-Fi network and the IP is assigned within the indicated range. but I still don't surf the internet with my mobile phone connected to the Wi-Fi network

you can help me?

[lightkun-yagami]

I can verify that the bridge to the internet is working as of 10/7/2022. See the link that it is working: https://imgur.com/a/wap4oho

[Malpaga]

Hello all,

I am facing the same problem, where everything works properly but network bridge doesn't.
Config has been done on a Raspberry Pi 3 Model B with OS Buster,
The Raspberry itself has internet access through eth0 interface.
Installation went smoothly, web interface is reached, ephemeral network is properly created and found by phone, but does not provide internet access.

Changes to the iptables rules did not fix the problem, any other clues ?

[claudiopolis]

I am having the same issue on Buster (hardware is a Seeed Studio reTerminal, which has CM4 - really promising hardware for this project, as it comes with the touchscreen in a nice enclosure, all at a reasonable price given supply chain issues for regular RasPi boards).

When I launch the ephemeral network and then SSH into the unit via the LAN interface, I can ping external hosts fine from the default source IP (which is the LAN port, which is plugged into upstream router), but when I specify the flag "-I 192.168.100.1" which is the IP of the ephemeral wlan, then no joy.

[claudiopolis]

I re-imaged my device with Bullseye (32-bit) instead, and it all works great. Sadly, I didn't save more data from the problem on Buster. I noticed on Buster that before using the front-end to launch the ephemeral network, ifconfig showed only 3 interfaces, but afterwards, it showed 5 or 6. Bullseye still only shows 3 interfaces (eth0, l0 and wlan0) after launching the ephemeral, so I hope that's a clue for anyone who might not have the option to switch to Bullseye.

FY & FWIWI, this is the 2nd problem I had with this solution that got fixed just by changing from Buster to Bullseye (the first being #110).

[Malpaga]

Fixed my problem by just adding a masquerade iptables rule :

iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

Make sure the output interface is the one facing your router.

[jeffman78]

I experienced the same issue (successfully connected to the ephemeral wifi - wlan1 - but no network connection to the internet).
After looking at the code, I discovered the IP range used for the ephemeral wifi is configured to used 192.168.100.0/24 and it was overlapping with the IP range allocated on wlan0. After updating my network config on a different IP range, everything worked like a charm.

[EvgenyAblesov]

Hello to everyone!

Thanks for all for participation to solve this issue. For now it seems like jeffman78 advice works well.