ok. I do not know much about Linux but do networking for work. Been learning BT for a few weeks, having fun with Reaver. I have never SSH'd to my ignorant shame. Just so you know what you are dealing with;
When I got my M4, I powered it up. Plugged in internet (192.) to the WAN port of the Pineapple, went to 172.16.42.1/pineapple/, logged in, activated karma and allowed a (Win7 and then Ipad2) to connect to a phantom ssid. Once I saw that the device(s) received a 172 IP, I tried from the target machines to surf. No joy. Read the forums and tried Darren's simple instructions (/etc/init.d/firewall disable; /etc/init.d/firewall stop), reboot, try again; no joy. Then tried putting the firewall command in the job tab below the karma disable but before the exit(/etc/init.d/firewall disable; /etc/init.d/firewall stop to rc.local via the Jobs), no joy.
Because I am overly methodical, I did not try ICS, change any other settings or service. Will wait for firmware;
upgrade to 1.01 was exactly as expected (reboot, 2 minutes, no error, happy pineapple.
With internet (192) in the WAN port of pineapple, i can ping 188.8.131.52, I can tracert www.google.com from the pineapple. Activate karma, connect target machine to phantom ssid, receive a 172.16.42.184 ip, but am not able to ping 184.108.40.206 from target cpu. A tracert to www.cnn.com goes; pinapple.lan, (172.16.42.1), destination host unreachable. I confirm the target machines are receiving an IP via the status in pineapple. the IP routing table has 4 entries;
default - 172.16.42.42 - 0.0.0.0
default - 192.168.1.1 - 0.0.0.0
172.16.42.0 - * - 255.255.255.0
192.168.1.0 - * - 255.255.255.0
wirless in enabled
karma is enabled
cron job enabled
all the rest disabled
(did not mess with anything other than karma)
I also tried a Ipad as the target, received a 172.16.42.157 IP but am unable to surf the internet.
No cellphone dongle to try. Use OpenDNS on my netgear router.
I know this is a firewall issue but I dont see where I am messing up or what I could have done to receive such a non-standard experience.
I had another network guy look at my process but he is unable to see the error I am making. In all, I have tried the above steps dozens of times but distilled it for clarity. Some users don't know what they are clicking but I did the above steps methodically and deliberately (not that I didn't mess-up somewhere, just I paid attention out of fear of a repeat experience of my M2.)