New Build - 06/23/2014 - r24461

Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2, 3 ... 17, 18, 19 ... 25, 26, 27  Next
Author Message
Yoda32
DD-WRT Novice


Joined: 08 Aug 2014
Posts: 7

PostPosted: Thu Aug 21, 2014 16:53    Post subject: Reply with quote
Meaulnes wrote:
@Yoda32

I believe I'll also have to take same decision for now with my WNDR3700v4. Can you please tell me how you reverted back to stock firmware or point me to instructions? Thx in advance.




1. Download and run TFTP2.exe
2. Set PC IP to 192.168.1.20
3. Set TFTP2 server: 192.168.1.1
Set TFTP2 password: password
Set TFTP2 File: download the firmware from netgear.com
4. Press RESET button x 45 seconds, green light start blinking
5. Press TFTP2 UPLOAD button.
6. After file uploaded it will start reboot cycles, wait 20 minutes.
7. Unplug power and wait 1 minute.
8. Plug power.
Sponsor
wir13dd
DD-WRT Novice


Joined: 23 Aug 2014
Posts: 5

PostPosted: Sat Aug 23, 2014 3:11    Post subject: Reply with quote
Router Model: TP-LINK WR741ND V1
Status: Mostly OK
Reset: No
Errors: lan connectivity between computers on eth ports does not work.
smoochie1
DD-WRT Novice


Joined: 07 Aug 2014
Posts: 6

PostPosted: Sat Aug 23, 2014 18:55    Post subject: Reply with quote
Yoda32 wrote:
Meaulnes wrote:
@Yoda32

I believe I'll also have to take same decision for now with my WNDR3700v4. Can you please tell me how you reverted back to stock firmware or point me to instructions? Thx in advance.




1. Download and run TFTP2.exe
2. Set PC IP to 192.168.1.20
3. Set TFTP2 server: 192.168.1.1
Set TFTP2 password: password
Set TFTP2 File: download the firmware from netgear.com
4. Press RESET button x 45 seconds, green light start blinking
5. Press TFTP2 UPLOAD button.
6. After file uploaded it will start reboot cycles, wait 20 minutes.
7. Unplug power and wait 1 minute.
8. Plug power.


Hi there yoda and thanks for this information. i was wondering if this same process should work for my tp link tl-wr2543? i have tried it but it just keeps retrying saying that it is erasing flash and could take a long time. i would like to return to stock, or an earlier version of ddwrt if possible as i need to use qos and can't seem to get it to work in ddwrt. many thanks in advance Smile
smoochie1
DD-WRT Novice


Joined: 07 Aug 2014
Posts: 6

PostPosted: Sun Aug 24, 2014 16:21    Post subject: Reply with quote
smoochie1 wrote:
Yoda32 wrote:
Meaulnes wrote:
@Yoda32

I believe I'll also have to take same decision for now with my WNDR3700v4. Can you please tell me how you reverted back to stock firmware or point me to instructions? Thx in advance.




1. Download and run TFTP2.exe
2. Set PC IP to 192.168.1.20
3. Set TFTP2 server: 192.168.1.1
Set TFTP2 password: password
Set TFTP2 File: download the firmware from netgear.com
4. Press RESET button x 45 seconds, green light start blinking
5. Press TFTP2 UPLOAD button.
6. After file uploaded it will start reboot cycles, wait 20 minutes.
7. Unplug power and wait 1 minute.
8. Plug power.


Hi there yoda and thanks for this information. i was wondering if this same process should work for my tp link tl-wr2543? i have tried it but it just keeps retrying saying that it is erasing flash and could take a long time. i would like to return to stock, or an earlier version of ddwrt if possible as i need to use qos and can't seem to get it to work in ddwrt. many thanks in advance Smile


I don't suppose anyone can recommend maybe an alternate method to flash another firmware over this latest one in as easy steps to follow as yoda32's please, i am using a TP link WR2543. Any help is muchly appreciated Smile
danymarc
DD-WRT Guru


Joined: 04 Nov 2012
Posts: 525
Location: Acapulco, Mexico

PostPosted: Sun Aug 24, 2014 18:49    Post subject: Reply with quote
smoochie1 wrote:
an alternate method to flash another firmware over

1. You will have to flash via WinScp and before enable the ssh daemon (service)? If not, SSH administration will be greyed out and disabled. You need to enable both the service and the administration.
2. Upload the file using Winscp in the /tmp folder of your router.
3. Connect with Putty and give this commands:
cd /tmp
mtd -r write xxx.bin linux
Every command at once hitting Enter.
Note: you posted to flash another firmware over in case you want to revert to. stock use a stripped FW or you will brick your router

_________________
TP-Link: TL-WR741ND V4
TP-Link: TL-WR842ND V2
smoochie1
DD-WRT Novice


Joined: 07 Aug 2014
Posts: 6

PostPosted: Sun Aug 24, 2014 22:52    Post subject: Reply with quote
danymarc wrote:
smoochie1 wrote:
an alternate method to flash another firmware over

1. You will have to flash via WinScp and before enable the ssh daemon (service)? If not, SSH administration will be greyed out and disabled. You need to enable both the service and the administration.
2. Upload the file using Winscp in the /tmp folder of your router.
3. Connect with Putty and give this commands:
cd /tmp
mtd -r write xxx.bin linux
Every command at once hitting Enter.
Note: you posted to flash another firmware over in case you want to revert to. stock use a stripped FW or you will brick your router


Just wanted to say a big thanks danymarc i really appreciate your time to help Smile .It might sound stupid but ive learnt loads since installing ddwrt and then going through the trouble to revert back to stock fw but couldn't have done it without your direct pointers so many thanks Smile
smoochie1
DD-WRT Novice


Joined: 07 Aug 2014
Posts: 6

PostPosted: Mon Aug 25, 2014 17:32    Post subject: Reply with quote
smoochie1 wrote:
danymarc wrote:
smoochie1 wrote:
an alternate method to flash another firmware over

1. You will have to flash via WinScp and before enable the ssh daemon (service)? If not, SSH administration will be greyed out and disabled. You need to enable both the service and the administration.
2. Upload the file using Winscp in the /tmp folder of your router.
3. Connect with Putty and give this commands:
cd /tmp
mtd -r write xxx.bin linux
Every command at once hitting Enter.
Note: you posted to flash another firmware over in case you want to revert to. stock use a stripped FW or you will brick your router


Just wanted to say a big thanks danymarc i really appreciate your time to help Smile .It might sound stupid but ive learnt loads since installing ddwrt and then going through the trouble to revert back to stock fw but couldn't have done it without your direct pointers so many thanks Smile


I don't suppose someone may be able to link me to the most stable version of ddwrt or at least a more favourable version over the latest build for my tp link tl-wr2543nd pleeease and thanks in advance.
SimonB79
DD-WRT User


Joined: 02 Aug 2014
Posts: 52

PostPosted: Tue Aug 26, 2014 4:12    Post subject: Reply with quote
I was messing around with my wndr3700v4 (with brainslayers latest release) last night & found summit strange! Smile

When I use my wnda3100v2 USB adapter I get between 75 & 100mbps on speedtests & with my A6200 I get my full 152mbps! ... It was the USB adapter slowing my connection down not ddwrt! Shocked ... I have dynamic 20/40 (& auto channel) enabled on both 2/5ghz! Smile

(The WNDR3700v4 is fantastic with ddwrt!) Very Happy
mittelhessen
DD-WRT User


Joined: 26 Jan 2012
Posts: 458

PostPosted: Tue Aug 26, 2014 7:08    Post subject: Reply with quote
SimonB79 wrote:

... (with brainslayers latest release) ...


You mean r24461?! Or is there any other newer release?

I'm looking forward to the best revision for a TP-Link WDR3600, but it seems that there're very many issues with r24461 so that an older build would be the better choice.

I'm hopefully that there'll be a new build with fixed issues of r24461 soon.
SimonB79
DD-WRT User


Joined: 02 Aug 2014
Posts: 52

PostPosted: Tue Aug 26, 2014 7:22    Post subject: Reply with quote
mittelhessen wrote:
SimonB79 wrote:

... (with brainslayers latest release) ...


You mean r24461?! Or is there any other newer release?

I'm looking forward to the best revision for a TP-Link WDR3600, but it seems that there're very many issues with r24461 so that an older build would be the better choice.

I'm hopefully that there'll be a new build with fixed issues of r24461 soon.


Yes r24461 is what I'm using! Smile

I'm gonna send my netgear r7000 back to amazon for a refund cause I don't need it anymore! Smile

(the wndr3700v4 (& A6200) does everything I need ATM) Smile
rlindon
DD-WRT Novice


Joined: 03 Jan 2012
Posts: 2

PostPosted: Wed Aug 27, 2014 1:58    Post subject: Reply with quote
Here goes my downgrading contribution to the community, based on danymarc and everyone here! Thanks!

1 On DD-WRT:
1.1 Under Services, Secure Shell, SSHd: check enable, then click Apply Settings button;
1.2 Under Administration, Remote Access, SSH Management: check enable, then click Apply Settings button;

2 Download and install WinSCP (http://winscp.net);

3 Download corresponding firmware from ftp://tplink-forum.pl/orgin_bez_boot/

4 Download putty (http://www.putty.org/)

5 On WinSCP:
5.1 Select New Site;
5.2 File protocol: SCP;
5.3 Hostname: 192.168.1.1 (or your router IP);
5.4 Username: root
5.5 Password: your admin pass
5.6 Drag downloaded firmware from Download folder and drop in /tmp
5.7 (Important, I think...) On Transfer Settings, select Binary
5.8 Transfer;

6 On putty;
6.1 Login on 192.168.1.1 (user root and pass);
6.2 Type:
cd /tmp (Enter)
mtd -r write xxxxx.bin linux (Enter) (Sure, replace xxxx with your firmware filename...)

7 It worked for me in a tp-link wr740n v4.22;

8 Use at your own risk. (I cannot confirm if it will work on your model, router, etc.)

9 Sorry for my poor english;

10 My sucessfull log downgrading a tp-link wr740n v4.22:

login as: root
DD-WRT v24-sp2 std (c) 2014 NewMedia-NET GmbH
Release: 06/23/14 (SVN revision: 24461)
root@192.168.1.1's password:
==========================================================

____ ___ __ ______ _____ ____ _ _
| _ \| _ \ \ \ / / _ \_ _| __ _|___ \| || |
|| | || ||____\ \ /\ / /| |_) || | \ \ / / __) | || |_
||_| ||_||_____\ V V / | _ < | | \ V / / __/|__ _|
|___/|___/ \_/\_/ |_| \_\|_| \_/ |_____| |_|

DD-WRT v24-sp2
http://www.dd-wrt.com

==========================================================


BusyBox v1.22.1 (2014-06-23 09:09:57 CEST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

root@DD-WRT:~# cd /tmp
root@DD-WRT:/tmp# mtd -r write wr740nv4.bin linux
Unlocking linux ...
Writing from wr740nv4.bin to linux ... [w]
root@DD-WRT:/tmp#
smoochie1
DD-WRT Novice


Joined: 07 Aug 2014
Posts: 6

PostPosted: Wed Aug 27, 2014 23:47    Post subject: Reply with quote
rlindon wrote:
Here goes my downgrading contribution to the community, based on danymarc and everyone here! Thanks!

1 On DD-WRT:
1.1 Under Services, Secure Shell, SSHd: check enable, then click Apply Settings button;
1.2 Under Administration, Remote Access, SSH Management: check enable, then click Apply Settings button;

2 Download and install WinSCP (http://winscp.net);

3 Download corresponding firmware from ftp://tplink-forum.pl/orgin_bez_boot/

4 Download putty (http://www.putty.org/)

5 On WinSCP:
5.1 Select New Site;
5.2 File protocol: SCP;
5.3 Hostname: 192.168.1.1 (or your router IP);
5.4 Username: root
5.5 Password: your admin pass
5.6 Drag downloaded firmware from Download folder and drop in /tmp
5.7 (Important, I think...) On Transfer Settings, select Binary
5.8 Transfer;

6 On putty;
6.1 Login on 192.168.1.1 (user root and pass);
6.2 Type:
cd /tmp (Enter)
mtd -r write xxxxx.bin linux (Enter) (Sure, replace xxxx with your firmware filename...)

7 It worked for me in a tp-link wr740n v4.22;

8 Use at your own risk. (I cannot confirm if it will work on your model, router, etc.)

9 Sorry for my poor english;

10 My sucessfull log downgrading a tp-link wr740n v4.22:

login as: root
DD-WRT v24-sp2 std (c) 2014 NewMedia-NET GmbH
Release: 06/23/14 (SVN revision: 24461)
root@192.168.1.1's password:
==========================================================

____ ___ __ ______ _____ ____ _ _
| _ \| _ \ \ \ / / _ \_ _| __ _|___ \| || |
|| | || ||____\ \ /\ / /| |_) || | \ \ / / __) | || |_
||_| ||_||_____\ V V / | _ < | | \ V / / __/|__ _|
|___/|___/ \_/\_/ |_| \_\|_| \_/ |_____| |_|

DD-WRT v24-sp2
http://www.dd-wrt.com

==========================================================


BusyBox v1.22.1 (2014-06-23 09:09:57 CEST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

root@DD-WRT:~# cd /tmp
root@DD-WRT:/tmp# mtd -r write wr740nv4.bin linux
Unlocking linux ...
Writing from wr740nv4.bin to linux ... [w]
root@DD-WRT:/tmp#


Wow cool downgrading guide dude, in-depth yet easy to follow! I followed danymarcs pointers to downgrade mine but im sure this will be a big help to anyone who doesn't know how to downgrade but wants too, so i deffo appreciate the time you put in.
johnnyho1415
DD-WRT Novice


Joined: 13 Aug 2014
Posts: 6

PostPosted: Thu Aug 28, 2014 6:21    Post subject: Reply with quote
Found an interesting issue... can anyone help confirm? Thanks!

Router Model: Linksys WRT300N v1.1
Status: working
Reset: Done
Build: dd-wrt.v24_vpn_generic.bin (r24461)
Errors:

[Conditions]
Default VLAN = vlan1
WAN VLAN = vlan2
Extra VLAN: VLAN12
Physical WLAN: wl0 (eth0)
VAP: wl0.1, wl0.2
br0 includes eth0, vlan1
br1 includes vlan12, wl0.1, wl0.2
br0 in subnet 192.168.1.0/24
br1 in subnet 192.168.12.0/24
DNSmasq used as DHCP server
(i.e. dnsmasq_options='interface=br1
dhcp-range=192.168.12.100,192.168.12.149,255.255.255.0,1440m
')
NAS daemon killed and restarted properly according to http://www.dd-wrt.com/wiki/index.php/VLAN_Detached_Networks_each_with_Wireless_and_Internet

[Symptom]
As long as wl0.1 and wl0.2 are on VLAN12, they won't get connected even if I have reset NAS.

If I manually set wl0.1 on br0 (keeping wl0.2 on br1), with the NAS daemon reset (in fact it will restart by itself) WITHOUT rebooting, I can connect to wl0.1 but not wl0.2, but after reboot (also NAS is reset at startup), none of the VAPs can be connected.

If I set it at the very first place wl0.1 to be on br0 and set the NAS reset startup script, devices cannot be connected to any of the VAPs after the FIRST bootup.

Sounds not the problem of DHCP settings because typing a wrong password for connecting to VAP does not prompt wrong password message.

However, removing wl0.2 interface (so all (though it is the only one) VAP(s) are on br0) resolves the problem.

The physical WLAN wl0 (or eth0) has no abnormal observation along the way (though I didn't try to put it on br1).

Basically I type the following code after 30/30/30 hard reset:

Code:

nvram set router_name=WRT300N_DD-WRT
nvram set router_style="green"
nvram set time_zone="+08"
nvram set daylight_time="1"
nvram set ntp_server="cn.pool.ntp.org"

nvram set telnetd_enable="0"
nvram set remote_mgt_telnet="0"
nvram set sshd_enable="1"
nvram set sshd_forwarding="0"
nvram set sshd_passwd_auth="1"
nvram set sshd_port="22"
nvram set remote_mgt_ssh="1"
nvram set sshd_wanport="22"
nvram set http_enable="1"
nvram set remote_mgt_https="0"
nvram set http_wanport="8080"

nvram set vlan1ports="1 2 3 4 5*"
nvram set vlan0ports="5"
nvram set vlan2ports="0 5"
nvram set vlan2hwname="et0"
nvram set port5vlans="0 1 2 16"
nvram set port0vlans="2 18 19"
nvram set port1vlans="1 18 19"
nvram set port2vlans="1 18 19"
nvram set port3vlans="1 18 19"
nvram set port4vlans="1 18 19"
nvram set lan_ifnames="eth0 vlan1"
nvram set vlan1_bridged=1

nvram set rc_startup='
PATH="/sbin:/usr/sbin:/bin:/usr/bin:${PATH}"

ifconfig vlan0 down

nvram set wan_default="vlan2"
nvram set wan_ifname="`nvram get wan_default`"
nvram set wan_ifname2="`nvram get wan_default`"
nvram set wan_ifnames="`nvram get wan_default`"
nvram set wandevs="`nvram get wan_default`"
nvram set pppoe_wan_ifname="`nvram get wan_default`"
ifconfig `nvram get wan_default` up

brctl addif br0 vlan1
brctl addif br0 eth0
brctl delif br0 vlan0
'

nvram set bridges="br1>Off>32768>1500"
nvram set br1_bridged=0
nvram set br1_ipaddr=192.168.12.1
nvram set br1_netmask=255.255.255.0
nvram set br1_mtu=1500
nvram set br1_multicast=0
nvram set br1_nat=1
nvram set vlan12ports="5"
nvram set vlan12hwname="et0"
nvram set port5vlans="0 1 2 12 16"
nvram set vlan12_bridged=0
nvram set vlan12_ipaddr="`nvram get br1_ipaddr`"
nvram set vlan12_netmask="`nvram get br1_netmask`"
nvram set vlan12_mtu=1500
nvram set vlan12_multicast=0
nvram set vlan12_nat=1
nvram set bridgesif="br1>vlan12>63"
nvram set local_dns=1
nvram set dnsmasq_options='interface=br1
dhcp-range=192.168.12.100,192.168.12.149,255.255.255.0,1440m
'

nvram set rc_startup="`nvram get rc_startup`"'
brctl addbr br1
ifconfig vlan12 up
brctl addif br1 vlan12
ifconfig br1 192.168.12.1 netmask 255.255.255.0 up
'

nvram set rc_firewall='
iptables -I INPUT -i br1 -j ACCEPT
iptables -I INPUT -i vlan1 -j ACCEPT
iptables -I FORWARD -i br1 -o vlan2 -m state --state NEW -j ACCEPT
iptables -I FORWARD -i br1 -o ppp0 -m state --state NEW -j ACCEPT
#iptables -I FORWARD -i br0 -o br1 -j logdrop
'

nvram set bridgesif="`nvram get bridgesif` br1>wl0.1>63 br1>wl0.2>63"

nvram set wl_mode=ap
nvram set wl_bss_opmode_cap_reqd=1
nvram set wl_net_mode=ng-only
nvram set wl_nband=2
nvram set wl_gmode=2
nvram set wl_nmode=2
nvram set wl_channel=8
nvram set wl_nreqd=0
nvram set wl_ssid=SF-test

nvram set wl0_mode="`nvram get wl_mode`"
#nvram set wl0_infra=1
nvram set wl0_net_mode="`nvram get wl_net_mode`"
nvram set wl0_gmode="`nvram get wl_gmode`"
nvram set wl0_nmode="`nvram get wl_nmode`"
nvram set wl0_ssid="`nvram get wl_ssid`"
nvram set wl0_radio=1
nvram set wl0_nbw=40
nvram set wl0_nband="`nvram get wl_nband`"
nvram set wl0_channel="`nvram get wl_channel`"
nvram set wl0_nctrlsb=lower
nvram set wl0_closed=0
nvram set wl0_distance=2000
nvram set wl0_ap_isolate=0
nvram set wl0_bridged=1
nvram set "`nvram get wl0_ifname`"_multicast=0
nvram set "`nvram get wl0_ifname`"_nat=1
nvram set wl0_ipaddr=0.0.0.0
nvram set wl0_netmask=0.0.0.0
nvram set wl0_akm=psk2
nvram set wl0_security_mode="`nvram get wl0_akm`"
nvram set wl0_crypto=aes
nvram set wl0_wpa_psk=*********
nvram set wl0_wpa_gtk_rekey=3600
nvram set wl0_macmode=disabled
nvram set wl0_maclist=

nvram set wl0_vifs="wl0.1 wl0.2"

nvram set wl0.1_mode=ap
#nvram set wl0.1_infra=1
nvram set wl0.1_ssid=ST-test
nvram set wl0.1_closed=0
nvram set wl0.1_ap_isolate=0
nvram set wl0.1_bridged=0
nvram set wl0.1_multicast=0
nvram set wl0.1_nat=1
nvram set wl0.1_ipaddr="`nvram get br1_ipaddr`"
nvram set wl0.1_netmask="`nvram get br1_netmask`"
nvram set wl0.1_akm=psk2
nvram set wl0X1_security_mode="`nvram get wl0.1_akm`"
nvram set wl0.1_crypto=aes
nvram set wl0.1_wpa_psk=*********
nvram set wl0.1_wpa_gtk_rekey=3600

nvram set wl0.2_mode=ap
#nvram set wl0.2_infra=1
nvram set wl0.2_ssid=guest-test
nvram set wl0.2_closed=0
nvram set wl0.2_ap_isolate=0
nvram set wl0.2_bridged=0
nvram set wl0.2_multicast=0
nvram set wl0.2_nat=1
nvram set wl0.2_ipaddr="`nvram get br1_ipaddr`"
nvram set wl0.2_netmask="`nvram get br1_netmask`"
nvram set wl0.2_akm=psk2
nvram set wl0X2_security_mode="`nvram get wl0.2_akm`"
nvram set wl0.2_crypto=aes
nvram set wl0.2_wpa_psk=*********
nvram set wl0.2_wpa_gtk_rekey=3600

nvram set rc_startup="`nvram get rc_startup`"'
ifconfig wl0.1 up
brctl addif br1 wl0.1
ifconfig wl0.2 up
brctl addif br1 wl0.2

stopservice nas
killall nas
nas -P /tmp/nas.wl0lan.pid -H 34954 -l br0 -i "`nvram get wl0_ifname`" -A -m 128 -k \
"`nvram get wl0_wpa_psk`" -s "`nvram get wl0_ssid`" -w 4 -g "`nvram get wl0_wpa_gtk_rekey`" &
nas -P /tmp/nas.wl0.1lan.pid -H 34954 -l br1 -i "`nvram get wl0.1_ifname`" -A -m 128 \
-k "`nvram get wl0.1_wpa_psk`" -s "`nvram get wl0.1_ssid`" -w 4 -g "`nvram get wl0.1_wpa_gtk_rekey`" &
nas -P /tmp/nas.wl0.2lan.pid -H 34954 -l br1 -i "`nvram get wl0.2_ifname`" -A -m 128 -k \
"`nvram get wl0.2_wpa_psk`" -s "`nvram get wl0.2_ssid`" -w 4 -g "`nvram get wl0.2_wpa_gtk_rekey`" &
'

nvram set wan_domain=*******
nvram set wan_proto=pppoe
nvram set pppoe_username=***********
nvram set ppp_username="`nvram get pppoe_username`"
nvram set pppoe_passwd=*******
nvram set ppp_passwd="`nvram get pppoe_passwd`"
nvram set fromvdsl=0
nvram set vdsl_state=0
nvram set reconnect_enable=1
nvram set reconnect_hours=0
nvram set reconnect_minutes=1
nvram set mtu_enable=1
nvram set wan_mtu=1492

nvram commit
reboot



Build 21153 does not have such problem.


Last edited by johnnyho1415 on Mon Sep 01, 2014 7:24; edited 3 times in total
Mile-Lile
DD-WRT Guru


Joined: 24 Feb 2013
Posts: 1634
Location: Belgrade

PostPosted: Thu Aug 28, 2014 6:26    Post subject: Reply with quote
I think that Linksys WRT300N v1.1 is broadcom based unit. This is Atheros. Maybe it would be better to post on Broadcom although some people here has broadcom units as well...
tricade
DD-WRT Novice


Joined: 19 Sep 2011
Posts: 2

PostPosted: Thu Aug 28, 2014 9:13    Post subject: Reply with quote
Router Model: Linksys WRT160NL 1.0
Status: Working
Reset: Yes
Errors: Wlan dropp outs
Goto page Previous  1, 2, 3 ... 17, 18, 19 ... 25, 26, 27  Next Display posts from previous:    Page 18 of 27
Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum