I've been asked to start a new thread to get this add-blocking to work.
I will make 2 seperate threads. One thread is a simple one. It will resolve all those nasty domains to an IP of your choice. In my example I will use 0.0.0.0 but you can also change that to an ip on which you have pixelserv running.
I will later make another thread where I'll be using the onboard webserver to answer the webcalls.
802.11 over 2.4GHz and 5GHz
From my understanding and experincial discoveries, 802.11B, 802.11G and 802.11N are strictly modulation protocols. These protocols could be used in any frequency band.
802.11A is not a modulation specification, but instead a specific reference to the 5 Ghz RF band. Ubiquity for sure has ( and other manufacturs may have ) 802.11G and 802.11N modulated devices that operate in both the 5 Ghz and 2.4 Ghz band. If that all sound confuzing then rest assured I am just as confused as to why the same specification format represents two differnt things ( modulation scheme versus frequencey band ID )
To my knowlege no vendor or hardware manufaturer has ever produced 802.11B modulated hardware in the 5 Ghz band, although in theory it would certainly function. Ubiquity firmware has recently added 802.11B support, and since this same firmware runs on both the 2.4 Ghz and 5 Ghz hardware I could safely guess that Ubiquity would support an 802.11b device on 5 Ghz if one ever came along.
Now that the theory is out of the way, this new brand of radio is indeed extremely interesting. They appear to be a Ubiquity clone/knock-off. Enough so that I am going to purchase some of their gear and test it against Ubiquity hardwre. I already see from the documentation that they have evolved some better funtionality over their Ubiquity parent.
accessing different subnet
Phuzi0n: First off, this will only work if the router that was reset is connected via one of its LAN ports since the WAN port is firewalled by default. On the gateway router you just assign an IP to a br0 virtual interface and add NAT since the reset device won't have any route to the other network.
In the My Page thread redhat27 wrote:
...and with no nvram commits:
I noticed that the script permissions were properly set by default in the tarball.
So, a super easy way to 'install' the my page script files is just copy the tarball mypage-files-v0.16-20100129-00520.tgz over to your persistent storage (I used /jffs/store) and have this as part of your startup script:
if [ -e "$myPage" ]; then
tar -C /tmp/www -xzf $myPage
for pageIndex in 1 2 3 4 5 6 7 8 9 10 11 12
nvram set mypage_scripts="`echo $pages`"
Of course you may wish to install less: just remove the relevant page indexes. corerev comand
nvram show|grep corerev
If you have a dual radio, you will see wl0 & wl1. If you have a single radio, wl0 will contain the corerev.
Put simply, always specify the interface.
wl -i `nvram get wl0_ifname` [rest of command]
wl -i `nvram get wl0_ifname` cap = Wireless capabilities. example:
wl -i eth1 cap = Wireless Capabilities of radio at "eth1"
wl -i eth2 cap = Wireless Capabilities of radio at "eth2"
wl -i eth3 cap = Wireless Capabilities of radio at "eth3"
use an ethernet cable to connect to a lan port on the switch;
set the ethernet port ip to 192.168.0.2;
disconnect the router's power cable;
press the reset button and keep pressing it;
connect the router's power cable;
wait about 20 seconds with the reset button still pressed; the power light should be orange and blinking;
release the reset button;
use a browser and go to http://192.168.0.1;
upload one of dlink's original images.
Please note that even though the emergency webserver will be listening at 192.168.0.1, the router won't respond to pings.
The default settings are in file …./src/router/nvram/defaults.c in TomatoUSB