just write to the shop team. they will create the wiki account 4 you if needed.
If new logins are disabled on the Wiki, I would suggest changing the locin/create page to say so. That would avoid wasting the time of folks who are trying to help. (I tried several browsers, disabling security add-ons, and various other tricks before locating this thread. I confess that I was about to give up. I'm suspect I'm not the first.)
There are several ways that the account creation process might be streamlined, though I don't have enough information to know what would really work for the shop team. (Feel free to contact me if there is interest; perhaps I can even help with implementation.) The simplest of these might be to add something like this to bottom of the login page:
* In an effort to minimize spam, we have disabled automated account creation for the Wiki. If you need a login, search for an article titled The Shop Team, and use the contact information there to request it. If you only want to suggest a change and move on, then search the forum for a thread entitled Wiki Suggestions and add a note there.
Either the hardware-specific page needs to be updated, or the ASUS hardware list (and perhaps lists for other vendors as well) should be extracted into an include file to prevent this from happening in the future.
# A startup script that rivals watchdog in repeater or client mode
# When used on a Linksys WRT310N v2 that repeats a dodgy AP,
# we get 7+ day uptimes vs the 3-5h uptimes given by watchdog
# (tested with build 15940)
# After a successful ping, wait this long to check again.
# Recommend setting this to the time it takes to grab a cup of coffee
while true; do
until ping -c 2 -W 2 www.google.com; do
# When we cannot get two consecutive pongs,
# then attempt to restore connection
if [ $count -eq 3 ]; then
# If we have tried bouncing wland 3 times,
# then try rebooting the router
wland # bounce wland
sleep 45 # wait 45 seconds for association
count=`expr $count + 1`
could you create an account for me. I'd change the articly about openvpn (http://www.dd-wrt.com/wiki/index.php/OpenVPN ) myself if granted. If not, I'd like to propose the following changes:
In the point "4.1 Static Key" it should be mentioned that a static key does not work with server mode. Static keys can be used in daemon mode of the server only.
Furthermode, there is not documentation what server and daemon mode is. I'd like to add a paragraph like this:
Server Mode vs. daemon mode
In server mode, the openvpn server will allocate addresses to clients out of the given network/netmask. The server itself will take the ".1" address of the given network for use as the server-side endpoint of the local TUN/TAP interface. In daemon mode, the to be used ip addresses have to be supplied with the ifconfig command.
if [ -n "$WANIP" ]; then
V6PREFIX=$(printf $PREFIX':%02x%02x:%02x%02x' $(echo $WANIP | tr . ' '))
ip tunnel add tun6rd mode sit local $WANIP ttl 255
ip tunnel 6rd dev tun6rd 6rd-prefix $PREFIX::/32
ip addr add $V6PREFIX::1/32 dev tun6rd
ip addr add $V6PREFIX::1/64 dev br0
ip link set tun6rd mtu 1280
ip link set tun6rd up
ip route add ::/0 via ::$IP6RD dev tun6rd
ip6tables -I FORWARD -s $V6PREFIX::1/64 -j ACCEPT
kill -HUP $(cat /var/run/radvd.pid) 2>/dev/null
Posted: Sat Jan 07, 2017 16:39 Post subject: Wiki RE bridging is confused
Please unconfuse me......or the wiki........
The Repeater Bridge wiki ---
"The limitation with standard bridging is that it only allows wired clients to connect to your secondary router. Wireless clients cannot connect to your secondary router configured as a standard bridge."
It goes on to say..........
"Repeater Bridge allows wireless AND wired clients to connect to a the Repeater Bridge router, and through that device wirelessly to a primary router. You can still use this mode if you only need to bridge wired clients; the extra wireless repeater capability comes along for free; however, you are not required to use it."
Does anyone else see the conflict there??????
"Standard" is undefined. Since there are 2 bridging modes (Client & Repeater) I am assuming "standard" refers to either mode set up as a bridge. THEREFORE, a Repeater Bridge cannot have wireless clients, but then the picture shows a wireless client.
Also note that there are instances of the use of "WIRELESS BRIDGE" which is followed by "(CLIENT BRIDGE)". Why add to the confusion by adding another undefined term instead of just writing "CLIENT BRIDGE"??
Also note above the extra "a" here, "connect to a the Repeater"
Also note that the title on the "CLIENT BRIDGED" wiki probably should be "CLIENT BRIDGE". Both terms are also used indiscriminately throughout the wiki.
Part of the wiki confusion appears to be new vs old. My impressions are:
"WIRELESS BRIDGE" is old - so use should be "CLIENT BRIDGE (wireless bridge)" not reverse.
"CLIENT BRIDGED" is a lazy typo and should be changed to "CLIENT BRIDGE" in all instances. That is what the control panel says it is.
"STANDARD BRIDGE" is old - so use should be the same as Wireless Bridge as it seems to be the same things.
I would edit this all but I no longer have the appropriate account and can't create one.
Posted: Sat Jan 07, 2017 18:28 Post subject: Error in GLOSSARY
There are plenty of errors here but this one is worth mentioning and fixing:
Wake-on-LAN is an Ethernet computer networking standard that allows a shut-down computer to be booted remotely. .........."
A SHUT-DOWN computer will not WAKE. Shut-Down == dead, no power. It MUST be SLEEPING to WAKE.
Posted: Sun Jan 08, 2017 4:17 Post subject: You can't there from here
IF you get to "Linking routers" by some miracle and you click on DD-WRT wiki mainpage at the top
"You are here: DD-WRT wiki mainpage / Linking Routers" it becomes impossible to get back to Linking routers by clicking on a link -- because it is not under DD-WRT wiki mainpage
It is DD-WRT wiki mainpage / Tutorials / Linking routers.