Jump to content

Magnum

Members
  • Posts

    2
  • Joined

  • Last visited

Posts posted by Magnum

  1. Just read the OP. Reserving this spot. Pulling a pineapple off the factory line and testing. Standby.

    Edit: Just read the rest of the comments. This is weird. In all of my tests I've been using the mk3.sh (now renamed to mk4.sh) on linux and tethering has always worked. First thought: Go to the advanced page in the web UI and in the text area at the bottom type "/etc/init.d/firewall stop" then click Execute Commands. Ok, grabbing a pineapple and looking for a Windows 7 machine now...

    Edit 2: Issue /etc/init.d/firewall disable; /etc/init.d/firewall off from the Execute Commands text area a the bottom of the advanced page.

    Ok I grabbed a pineapple off the shelf, powered it, connected the spiffy little retractable ethernet cable between the pineapple's PoE LAN port and my laptop, booted Ubuntu (My Windows install is on a HDD collecting dust), connected to the WiFi on wlan0 and ran mk4.sh. It pinged 172.16.42.1 no problem. I browsed to http://172.16.42.1/pineapple, logged in, enabled karma. Went to the advanced page and verified that 172.16.42.42 is the default gateway. Entered 8.8.8.8 in the ping box and got replies, so it's online. Entered example.com in the ping box and also got replies, so DNS is working. Entered cat /etc/config/network; cat /etc/conf/dhcp in the execute commands box and everything looked great.

    Then I put my phone in airplane mode (so it's off the 3G network), enabled wifi, added an SSID called "is_ics_working" and instantly it connected. Tried to pull up example.com in my browser, no dice.

    Remembered this happening with 3G tethering and how the 3G tether scripts disable the firewall. Of course my testing didn't reveal this bug because I tested 3G first, then tethering...

    Went to the Advanced page, issued /etc/init.d/firewall disable; /etc/init.d/firewall off using the "Execute Commands" box and refreshed example.com on my phone. It worked.

    We'll squash this for good in the update coming out shortly. In the mean time run that command, or better yet add it to rc.local -- that's the startup script and you can edit it directly from the Jobs page.

    Man, I can't believe I missed that one. Ugh. Reminds me of trying to host a Quake 3 server at a LAN party on a Windows XP box with the firewall up. *sigh*

    Good work Darren! Thanks!

×
×
  • Create New...