Nodogsplash Captive Portal

[ravenium]

Hi All,

Making this post over here because I didn't find a thread that was Mark IV appropriate. I'm looking for feedback on anyone who's used the nodogsplash opkg (the one Darren featured in the Feb 2013 episode he did in Ireland - www.youtube.com/watch?v=_CfWaCtqtGA).

I've tried to install the appropriate packages but I'm getting a kernel mismatch error in some of the iptables modules (mark IV 2.8.1 here). Nodogsplash claims to be able to launch properly and has no conflicts with uhttpd (being that that's run on 1471 now).

However, it does not appear to be trapping new client requests properly, so I'm guessing it's a problem related to the iptables modules installation issue. Has anyone walked through this successfully? Not sure if there's much to be done about the iptables module kernel mismatch until an update is made to it.

I'd love to eventually turn this into an easily installable infusion for the masses - fake captive portals come in handy for client-side/wireless pen testing, and near as I can tell there isn't standardized solution in the modules list yet.

[say.what]

hi ravenium,

try reading this:

http://forums.hak5.org/index.php?/topic/28844-cant-install-nodogsplash/

is a good start point ;)

[ravenium]

Blast my searching abilities (I'll save face and note that the forum software doesn't find partial matches in words ). Thanks!

[webdirector]

Hello,

I installed Nodogsplash on 2.8.1 and I have the following issue.

After reboot if I connect over wireless to the pineapple I can go to google.com no problems.

When I then start nodogsplash via ssh and then call google.com I get the nodogsplash page. If I then press on the dog it should forward me to google.com . But I get the loading until it goes to the error pages and does not load.

any Idea what the problem could be ?

Thanks

[TylerCPU]

Hello,

I installed Nodogsplash on 2.8.1 and I have the following issue.

After reboot if I connect over wireless to the pineapple I can go to google.com no problems.

When I then start nodogsplash via ssh and then call google.com I get the nodogsplash page. If I then press on the dog it should forward me to google.com . But I get the loading until it goes to the error pages and does not load.

any Idea what the problem could be ?

Thanks

I haven't played with it for awhile, but your mircohttpd(webserver for phishing) is clashing with nodogsplash on port 80. Just change the mircohttpd to another port number like 81. Hope that helps.

Edited May 30, 2013 by TylerCPU

[webdirector]

Hello,

I do not think so i stoped it with

/etc/init.d/uhttpd stop

/etc/init.d/uhttpd disable

That did not do it.

[TylerCPU]

Hello,

I do not think so i stoped it with

/etc/init.d/uhttpd stop

/etc/init.d/uhttpd disable

That did not do it.

I'll try and mess with it and see what happens. To change your port number on uhttpd go to /etc/config/uhttpd and look for "list listen_http 0.0.0.0:80" on the top and change the 80 to like 81.

[webdirector]

Hello,

I flshed my Pinapple with 2.8.1

If I go to 172.16.42.1:1471 I can see

I changed the "/etc/config/uhttpd and look for "list listen_http 0.0.0.0:80" to list listen_http 0.0.0.0:81

I rebooted

I then installed nodogsplash as above.

If I then go to 172.16.42.1:1471 I can see I see the status page as I am suppose to

if I then SSH into pineapple and start nodogsplash

If i Then try and go 172.16.42.1:1471 I get "a blank page with the messgae " Unable to connect "

If I open another tab and type in "google.com" I get the standard splash page with the dog. If I press on the dog It says connecting to google but it never loads

any ideas what is wrong ?

Thanks

[TylerCPU]

Hello,

I flshed my Pinapple with 2.8.1

If I go to 172.16.42.1:1471 I can see

I changed the "/etc/config/uhttpd and look for "list listen_http 0.0.0.0:80" to list listen_http 0.0.0.0:81

I rebooted

I then installed nodogsplash as above.

If I then go to 172.16.42.1:1471 I can see I see the status page as I am suppose to

if I then SSH into pineapple and start nodogsplash

If i Then try and go 172.16.42.1:1471 I get "a blank page with the messgae " Unable to connect "

If I open another tab and type in "google.com" I get the standard splash page with the dog. If I press on the dog It says connecting to google but it never loads

any ideas what is wrong ?

Thanks

I always had problems with nodogsplash. So far what I was able to find out is that you don't need to change the uhttpd port to 81 from 80. Nodogsplash runs on port 2050. So no clashing there. The reason why I said that was because of what darren said

. When nodogsplash is running I can't access the pineapple web interface either. For some weird reason when I click on the dog on my phone it sits there and loads forever but if I try and load a different page my internet works fine on my phone(Samsung Galaxy SIII).On a desktop it's a different story. I get the "unable to connect" on google chrome in Windows on every site after it loads for awhile. The weirdest thing is this.

root@Pineapple:~# Invalid request path ''
Invalid request path ''
Invalid request path ''
Invalid request path ''
Invalid request path ''
Invalid request path ''
Invalid request path ''
Invalid request path ''
Invalid request path ''
Invalid request path '' 

I get this in my ssh connection when I try and load a webpage on another desktop computer but then fails to load it. I think that the nodogsplash redirect feature is broken(after you click on the dog).

I wish some of the devs would explain what is wrong or what I'm doing wrong. It just seems broken to me. I'm doing the same thing darren is doing in ep. 1401.1. I'm in the same boat as you. Never really worked for me.

Edited May 30, 2013 by TylerCPU

[ravenium]

I'm getting the "Invalid request path ''" bit even on a simple page load. I'll have to dig back into it when I have more time this week.

As for not being able to access the pineapple interface, that's a bit easier to explain - you need to review the firewall controls in your nodogsplash.conf. It's got separate classes of controls for unauthenticated users, authenticated users, and access to the pineapple itself. Make sure you have a listing for access to the administrative interface port (tcp/1471 or whatever you've set it to). If you want to be a bit more granular, you can also whitelist the MAC of a single device.

[TylerCPU]

I'm getting the "Invalid request path ''" bit even on a simple page load. I'll have to dig back into it when I have more time this week.

As for not being able to access the pineapple interface, that's a bit easier to explain - you need to review the firewall controls in your nodogsplash.conf. It's got separate classes of controls for unauthenticated users, authenticated users, and access to the pineapple itself. Make sure you have a listing for access to the administrative interface port (tcp/1471 or whatever you've set it to). If you want to be a bit more granular, you can also whitelist the MAC of a single device.

Thanks. I forgot about the firewall. *facepalm* Anyways if anybody wants to get access back on the pineapple interface just look for " FirewallRuleSet users-to-router { " in nodogsplash.conf and under that add

FirewallRule allow tcp port 1471

FirewallRule allow udp port 1471

That's it. Thanks @ravenium. I don't think you need udp but I put it there just in case.

[webdirector]

Hello,

I am sure it has to do with the conf file of nodogsplash. I am pretty sure it has to do with the " EmptyRuleSetPolicy " I just have not figured it out yet

I thought I had to use the " EmptyRuleSetPolicy preauthenticated-users passthrough " but that did not work

Edited May 31, 2013 by webdirector

[webdirector]

.......... can anyone help ?

does anybody get this working ?

[webdirector]

Bunmp :-)

[thesugarat]

DId you change the listen port back to 80? i.e. set everything back to normal? nodogsplash works for me... The part above about setting the firewall rule to allow the admin page was pure gold! One thing that's a little strange is starting and stopping nodogsplah is a little tricky. Even after I issue the nodogsplash stop command I still have to go to the processes page on the pineapple admin pages and kill the dodogsplash pid...