Jump to content

NullNull

Active Members
  • Content Count

    210
  • Joined

  • Last visited

  • Days Won

    6

About NullNull

  • Rank
    Hak5 Zombie

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. HAHAHAHAHAHAHAHAHA :lol: :lol: :lol:
  2. Raspberry Pi 2 (Middle) Alfa NHA (Access Point, Left) Alfa 036H (Deauth, Right) Anker 3 10.000 mah Pelican Case 1040 Running Kali 1.1.0 amd64 (with autostart: hostapd, dnsmasq, nginx, php-fpm, vncserver, mdk3)
  3. Yeap, Nodogsplash can't handle php :(. So here is what i did! (using a mk4 after a clean flash) 1) save the default iptables configuration (iptables-save > default_iptables.conf) 2) edit nodogsplash.conf to include only the gateway and users-to-router rules (allowing also 1471) 3) run nodogsplash and save it's iptables configuration (iptables-save > portal_iptables.conf) 4) stop nodogsplash 5) edit your dnsmasq for the 1.1.1.1 and run it. 6) change your web server port to 2050 and restart it. 7) aply the portal iptables (iptables-restore portal_iptables.conf) 8)You should be g
  4. After some more testing i see that the captive portal notification will pop up on Android tablets (Nexus 9 on 5.0, Samsung Tab 4 on 4.4.2) and not on Android mobiles (Galaxy S4 on 4.4.2). Although when surfing the web all traffic gets redirected. (even clients3.google.com/generate_204). Only way to pop the browser on my galaxy S4 is "address=/#/1.1.1.1" along with nodogsplash. I will try to replicate the iptables nodogsplash creates. Sounds easy.. Sorry but i dont have any others devices for testing :P NOTE: I deleted the previous post until i find something more stable!!!
  5. i'm glad you figured it out ;) next days i will have some free time, i will test it and post the results :)
  6. Are you referring to Android/iOS captive portal detection?So let my get that straight :P 1) You are running dnsmasq with lets say "address=/#/8.8.8.8" 2) Then dnsspoof with "*" redirecting everything to 172.16.42.1 3) Then nodogsplash. 4) And finaly the iptables from the second post redirecting all port 80 and 53 traffic to 172.16.42.1 Am i correct?
  7. yes. this will not redirect https or hsts but i think neither will nodogsplash...
  8. yes and it is working every time ... As you can see here: https://forums.hak5.org/index.php?/topic/34663-nodogsplash/#entry257631 i did not said i managed nodogsplash to work with out internet connection. Actualy i said that none of the captive protal "managers" i used, worked with out internet connection. The above commands have nothing to do with nodogsplash. I dont even have it installed right now. I just placed a simple html file in the www folder and configured dnsmasq. Try searching the web for "dnsmasq captive portal" , "dnsmasq walled garden" "dnsmasq splash screen"
  9. Sorry for that.. You get the same 502 error on all your browsers and clients?
  10. can you post the "cat /etc/dhcp" output? EDIT: just saw your dnsmasq.conf, no opendns server there. :/
  11. No need to run nodogspalsh with all that. reboot your pineapple and try it again. Also before testing it clear you browsers cache.
  12. hey johnsteiner, if you want just to serve a splash page ssh into your pineapple and try this: /etc/init.d/dnsmasq stop cp /var/etc/dnsmasq.conf /tmp/dnsmasq.conf sed -i '/address=/a address=/#/172.16.42.1' /tmp/dnsmasq.conf /usr/sbin/dnsmasq -C /tmp/dnsmasq.conf iptables -t nat -A PREROUTING -p tcp --dport 80 -j DNAT --to-destination 172.16.42.1 iptables -t nat -A PREROUTING -p tcp --dport 53 -j DNAT --to-destination 172.16.42.1 iptables -t nat -A PREROUTING -p udp --dport 53 -j DNAT --to-destination 172.16.42.1 This will make dnsmasq to resolve all domains to your pineapple's IP (172.16.4
  13. Thank you newbi. Trying to fix it with nodogsplash or any other captive portal manager didn't work for me. After a lot of search think dnsmasq and iptables is the way to do it. address=/#/172.16.42.1 at the dnsmasq.conf and iptables -t nat -A PREROUTING -p tcp --dport 80 -j DNAT --to-destination 172.16.42.1 iptables -t nat -A PREROUTING -p tcp --dport 53 -j DNAT --to-destination 172.16.42.1 iptables -t nat -A PREROUTING -p udp --dport 53 -j DNAT --to-destination 172.16.42.1 this might work but i need to test it.
  14. Sorry but i think it can be posted here too Because thats me Thank you, i saw that post but chillispot seems way to complicate to setup for something so simple..
×
×
  • Create New...