akramnajjar. It looks like iptables is dropping incoming packets unless the connection has already been established.
Quote from my other post earlier today on a similar issue:
Is your device rooted? If so, please read on, or else this entire post does not apply to your case.
Do you have Droidwall running or another app that can change iptables rules (root required)
I had a similar issue yesterday, which was caused by iptables dropping all incoming (new) packets.
In my case the rules were created by droidwall upon install.
The following steps fixed the issue for me:
Install and run Terminal Emulator (or other shell boxes)su (you need root to change iptables)run 'iptables -A INPUT -j ACCEPT' run airdroid and connect via web browser on your computer.
Litte sidenote, this is an ugly fix, you should limit the accept rules to known and trusted ports/subnets, but i am lazy to be honest and needed a fix five minutes ago when applied.
Quote from my other post earlier today on a similar issue:
Is your device rooted? If so, please read on, or else this entire post does not apply to your case.
Do you have Droidwall running or another app that can change iptables rules (root required)
I had a similar issue yesterday, which was caused by iptables dropping all incoming (new) packets.
In my case the rules were created by droidwall upon install.
The following steps fixed the issue for me:
Install and run Terminal Emulator (or other shell boxes)su (you need root to change iptables)run 'iptables -A INPUT -j ACCEPT' run airdroid and connect via web browser on your computer.
Litte sidenote, this is an ugly fix, you should limit the accept rules to known and trusted ports/subnets, but i am lazy to be honest and needed a fix five minutes ago when applied.