Skip to main content

CoovaChilli Captive Portal on WRT54GL

This page discusses how to use CoovaChilli (openwrt-54g-squashfs.bin) with a WRT54GL as a captive portal.  It took me several times to get this to work.  During my attempts, I somehow messed up my configuration.  tried to upload a new firmware and start over, and it turns out that CoovaAP takes over the firmware, and won't let you install anything else.  SO USE COOVAAP AT YOUR OWN RISK.  The only way I was able to reflash the router was with the JTAG cable again.   This thing has been worth its weight in gold with this router, as it's helped me recover from a corrupt BIOS (CFE Image), enabled me to reflash the router when the boot-wait was not turned on, enabled me to reflash nvram that was corrupt and I couldn't fix (say with the reset button), but mostly just fix bad firmware images that like to take over the OS and lot let it go.  

Uploaded the CoovaAP WRT54GL 1.0-beta.8 openwrt-54g-squashfs.bin file to the router, and started over.   Tried to do this directly via the JTAG cable, which took over three hours, but it didn't work.   So I uploaded the original Linksys firmware, and upgraded through the GUI.  

When CoovaAP booted, I changed the default password, and then went to the Hotspot section.  Under the "Configuration Tab", I changed the Hotspot type to Internal, Wireless only, Deny, Http for configured users.  

Under the "Access List" tab, I added one guest.  

Under the Portal Tab, I selected "Login Page", and changed the HTML to what I wanted it to say.  The cool thing about this is that it allows you to customize your login page!  

I applied changes, and tested it.  It didn't work.  So I went in to the GUI and started CoovaChilli (it was installed, but not running).   This worked like a champ (after unplugging and then plugging the router back in).   

I uploaded an image for my splash screen, to test if I can modify the redirect page.  This was done by scp'ing it up with the command: 
#scp beboNoBorder.jpg root@192.168.1.1:/jffs/usr/bebo.jpg  

I tried several times to get CoovaChilli to see this image, but it wouldn't until I put it in the /etc/chilli/www/ directory.  So apparently any files that you want CoovaChilli to display have to be here.   

I then changed went to Hotspot/Portal and selected Header from the drop-down, and edited it to read: 



    ALT="Bebo HotSpot"
    TITLE="Bebo Hotspot"

A couple of items worth note is that the Coova firmware is a little buggy, and wouldn't finish applying the changes I made unless it had an Internet connection.  Also, a user has to have a browser with JavaScript enabled to see the login page.   This is a little ghetto, but I suppose that most folks have Javascript enabled on their browsers anyway, so I guess that I can live with it. 

So I have an authenticated, encrypted Captive Portal to the Internet.   Finally!   Here is a screenshot of what the portal page looks like:



Comments

Popular posts from this blog

atftpd vs tftpd-hpa

Recently I was trying to tftp files from a Windows computer to a Kali box.   One version of Windows worked, but another didn't.    After much troubleshooting, here were my symptoms:

I could tftp a file from-to any Kali box from-to another Kali box
I could NOT tftp files to a specific Windows 7 box from any Kali box
I could NOT tftp files to a Chrooted-Ubuntu-Chromebook box from a Kali box

After MUCH troubleshooting, going through every setting in atftpd, it seemed like it literally was a client OS problem.  Different clients simply would not download files---unacceptable.

Thus, I switched to tftpd-hpa.   To install:
apt-get install tftpd-hpa

files go to/come from /srv/tftp, but it needs to be a tftp user. Thus, I needed to:
chroot -R /srv/tftp

Also, if you want to be able to put files ON the tftp server (from a client), you need to modify /etc/default/tftpd-hpa:
change "TFTP_OPTIONS="--secure" to "TFTP_OPTIONS="--secure --create"

I also changed the IP li…

ADS-B plotting with Kali (and other SDR goodies)

Recently I wanted to try some Software Defined Radio stuff.   
I had a RTL-SDR, FM+DAB, DVB-T USB Stick Set with RTL2832U & R820T. that I got from: http://www.amazon.com/gp/product/B00C37AZXK/ref=oh_details_o04_s00_i00?ie=UTF8&psc=1
But, even though this dongle would break out FM radio stations, and ATC frequencies (like the local Ground Control, tower, and even ATIS), which was cool, it wouldn't break out ADS-B.   
Thus, I bought a Vantech Green Mini RTL2832U R820T DVB-T SDR DAB FM USB DIGITAL TV Tuner Receiver RTL-SDR Project + DAB dongle Tuner MCX Input from Amazon, and tried this.  
This dongle was able to listen to the 1090MHz frequency required for ADS-B (as it goes from 25MHz to 1700MHz).  There were tons of Windows programs out there for breaking out and plotting ADS-B Mode S broadcasts, but not many for Linux.  
For Kali Linux, here's how I got it running and plotting planes around my home:
0) before you start, you should do an apt-get update to ensure you hav…

Temper Temperature monitor on a Beaglebone Black

Beaglebone Black as a temperature monitor:

Recently I wanted to monitor the temperature of my shed.  I thought I'd use a small computer such as a Raspberry Pi or a Beaglebone or Odroid.

My Raspberry Pi boxes were all in use, so I grabbed my Beaglebone, which was doing nothing.

I flashed it with the Debian9.32018-03-054GB SDIoTimage, but that seemed like it was running lots of bloatware and the ethernet interface wouldn't take a static IP with /etc/network/interfaces.

So I went with the Debian9.32018-01-284GB SDLXQTi image instead.  I still had the same problem, that lots of junk was running, and I couldn't configure my interface by modifying /etc/network/interfaces

So my first step was to get rid of all the bloatware.  If you're using a Raspberry Pi or something, you can skip this and just go to the second step below

STEP 1--Remove Blotatware from Beaglebone Black:

With some searching, I came across this post:
https://www.linuxquestions.org/questions/linux-newbie-8/inte…