Configuring EWRT NoCatSplash
- There is a discussion at
regarding how to configure the EWRT NoCatSplash captive portal
screen. Seems the developers have provided no documentation on that
feature, yet it's the primary advantage to their firmware. Power to
PortLess Networks for developing the firmware, but those of us who
aren't Linux programmers need additional assistance. Here's how one
of the EWRT developers responded to my request for additional info:
--->>Re: [Firmware] WRT54G Captive Portal with EWRT .3
Hi guys, Irving here of Portless networks. Hopefully I can help clear
up some confusion. I am working on an updated FAQ and these are all
good frequently asked questions.
First off, let me explain the three different filesystem types in
Ewrt and how they are used:
/ (root) - r/o squashfs. This is the main filesystem containing all
Ewrt data and you can only mount this filesystem readonly. /etc is
contained here and is readonly as well.
/tmp - r/w memfs. /tmp is a filesystem held in RAM, meaning that if
you fill it you will run out of RAM. the contents of /tmp are lost
with every reboot. Some files from /etc are symlinked to /tmp/etc,
and the /tmp/etc versions are written at boot time based on nvram
/opt - r/w jffs2. This is the new one we added for 0.3. /opt uses the
leftover flash for a non-volatile journalled filesystem. you get
about 1 meg on a 54G and 5 megs on a GS with Ewrt. This is a good
place to store files like your custom splash pages and other content
you wish to survive a reboot. /opt gets wiped when you reflash newer
version of Ewrt, because the partition boundaries change.
So: to change your /tmp/etc/nocat.conf permanently, you have to
change the nvram variables. You can do a "nvram show | grep NC_" on
the command line or go to Access Restrictions -> Captive Portal in
the web gui.
Hopefully that will answer your first question, and this will go in
Second question: We saw this bug during our 0.2 development but
haven't seen it since. turn up your verbosity in nocat to 9 and
cat /tmp/services.out. email us the info to the ewrt-devel @
third question: We've captured WDS clients with 0.2 no problems, but
we haven't tried it with 0.3. Again, try the steps above. Let us know
if this works with 0.2 for you.<<---
TO WHICH I REPLIED:
So, keeping in mind that 99% of us are Windows users and know nothing
about Linux except for Linus's name, and
referring to the web GUI in this user's example:
1. Gateway Name: Is this your router SSID? Or what?
2. Home Page: So, this is NOT the location for our custom splash
page, since it's stored in "/opt - r/w jffs2". What is this domain
3. Allowed Web Hosts: What should we set this to?
4. You write, "can do a "nvram show | grep NC_" on the command line
or go to Access Restrictions -> Captive Portal in the web gui." From
the above GUI example, are you saying we will change Document Root
to "/opt - r/w jiffs2"? I think one user mentioned above that
whenever he changes the root location here, it defaults back to that
displayed in the link above.
5. Should we leave Exclude Ports, Login Timeout, and Verbosity at
their default values since most of us haven't a clue what these mean?
Thanks for your help.
So, if any of you out there have the splash screen up and running
with your own splash, please provide step-by-step instructions on how
to do likewise ourselves. For example, I have a web server hosted by
one of the big outfits. I have uploaded my preferred splash site to
that server. But I can't call it from the EWRT page.
Marc in Taos, NM