WifiShadow

1 My Devices
2 Working On
3 DD-WRT
4 TomatoUSB
5 Links
6 Wiki Links
7 Users

AKA Dark_Shadow and DHC_DarkShadow on the dd-wrt forums.

60k nvram (like e2000 and e3000) or normal 32k

My Devices

Working On

Content

Testing

Templates

DD-WRT

Fix for new broadcom Wireless Driver

You can set it manually for now:

nvram set wl0_nbw_cap=1
nvram set wl1_nbw_cap=1
nvram commit
reboot

ad-blocking with DD-WRT revisited (simple)

Source = http://www.dd-wrt.com/phpBB2/viewtopic.php?t=47515

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.

First enable local dns and add the line

addn-hosts=/tmp/dlhosts

And put this in startup code.

_rogue=0.0.0.0
echo -e "#!/bin/sh\nn=1\nwhile sleep 60\ndo\n\twget -q -O - http://www.mvps.org/winhelp2002/hosts.txt | grep \"^127.0.0.1\" | grep -v localhost | awk '{print \"$_rogue\\\t\"\$2}' | tr -d '\\\015' >/tmp/dlhosts\n" >/tmp/write_dlhosts
echo -e "\t[ \`grep -il doubleclick /tmp/dlhosts\` ] && break\n\t[ \$n -gt 5 ] && break\n\tlet n+=1\ndone\nkillall -HUP dnsmasq" >>/tmp/write_dlhosts
chmod +x /tmp/write_dlhosts
/tmp/write_dlhosts &

or this one (which gives the possibility to add some custom hosts in either /opt/etc/hosts or /jffs/hosts):

_rogue=0.0.0.0
echo -e "#!/bin/sh\nn=1\nwhile sleep 60\ndo\n\twget -q -O - http://www.mvps.org/winhelp2002/hosts.txt | grep \"^127.0.0.1\" | grep -v localhost | awk '{print \"$_rogue\\\t\"\$2}' | tr -d '\\\015' >/tmp/dlhosts\n" >/tmp/write_dlhosts
echo -e "\t[ \`grep -il doubleclick /tmp/dlhosts\` ] && break\n\t[ \$n -gt 5 ] && break\n\tlet n+=1\ndone\n[ -e /jffs/hosts ] && cat /jffs/hosts >>/tmp/dlhosts\n[ -e /opt/etc/hosts ] && cat /opt/etc/hosts >>/tmp/dlhosts\nkillall -HUP dnsmasq" >>/tmp/write_dlhosts
chmod +x /tmp/write_dlhosts
/tmp/write_dlhosts &

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

Per GeeTek:

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 save startup

ifconfig br0:1 192.168.1.2 netmask 255.255.255.0

In save firewall

iptables -t nat -I POSTROUTING -o br0 -d 192.168.1.0/24 -j MASQUERADE

Samba2

http://www.dd-wrt.com/phpBB2/viewtopic.php?t=86926 - Samba2 dd-wrt

Commands

nvram size and amount free

nvram show|grep free

ext filesystem support

ls -R /lib/modules/ | grep ext

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:

myPage="/jffs/store/mypage-files-v0.16-20100129-00520.tgz"
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
  do
    pages="${pages} /tmp/www/mypage${pageIndex}.sh"
  done
  nvram set mypage_scripts="`echo $pages`"
fi

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.

wl commands

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:

Asus RT-N16
 wl -i eth1 cap = Wireless Capabilities of radio at "eth1"
Netgear WNDR3300
 wl -i eth2 cap = Wireless Capabilities of radio at "eth2"
 wl -i eth3 cap = Wireless Capabilities of radio at "eth3"

reference: Wl command

Getting the current up and down bandwidth

If anyone is interested u can get the amount sent and received by using grep and ifconfig:

RX=`ifconfig br0 | grep "RX bytes:" | cut -d ':' -f2 | cut -d "(" -f1 | tr -d ' '`
TX=`ifconfig br0 | grep "RX bytes:" | cut -d ':' -f3 | cut -d "(" -f1 | tr -d ' '`

If you can get the amount sent then u can get the current by just doing it again and subtracting them

http://www.dd-wrt.com/phpBB2/viewtopic.php?t=90467

USB HDD spindown

echo 1 > /sys/block/sda/device/scsi_disk:0:0:0:0/allow_restart

D-Link Recovery ?

Reference

The procedure is the following:

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.