Author
Message
wizin DD-WRT Novice Joined: 14 Aug 2011 Posts: 12
Posted: Fri Aug 19, 2011 2:01 Post subject: Please help: WNDR3700v2 MTU Issue
I have already bricked 2 other branded routers ( Linksys and Buffalo ) and I just purchased a brand new WNDR3700 ( still packed )
I want to set it up like http://forum.hidemyass.com/showthread.php?tid=2700&page=1
which says to get the 11/21/10 Sp2 file which I assume is here
http://www.dd-wrt.com/site/support/other-downloads
There are 3 files there, could someone guide me which one do I flash b4 bricking this one too Last edited by wizin on Sat Aug 20, 2011 3:26; edited 1 time in total
Back to top
Sponsor
amdmannen DD-WRT Novice Joined: 08 May 2011 Posts: 1 Location: sweden
Back to top
wizin DD-WRT Novice Joined: 14 Aug 2011 Posts: 12
Posted: Fri Aug 19, 2011 16:17 Post subject:
Issue is I want the 11/21/10 version since I have read the OPENVPN/Hidemyass subscriptions works but thats only for v1
Can I put a v1 version into v2?
Back to top
BlCa` DD-WRT User Joined: 16 Nov 2009 Posts: 135
Posted: Fri Aug 19, 2011 18:08 Post subject:
wizin wrote: Issue is I want the 11/21/10 version since I have read the OPENVPN/Hidemyass subscriptions works but thats only for v1
Can I put a v1 version into v2?
If you could, why would anyone bother creating a v2 version?
Back to top
jblack DD-WRT User Joined: 02 May 2011 Posts: 172
Posted: Fri Aug 19, 2011 19:48 Post subject: Re: Please help: To avoid bricking my new WNDR3700v2
This router has a a nice system to keep you from completely bricking it dead. If you unplug the power. Press and hold reset, then plug the power in and continue to hold reset for an additional 45 seconds (Green power light should be flashing), you'll put the router in recovery mode.
In recovery mode the router sets its own IP to 192.168.1.1 and you can TFTP a new firmware to it. I've semi-bricked my WNDR3700v1 a couple of times and this has saved me.
Back to top
wizin DD-WRT Novice Joined: 14 Aug 2011 Posts: 12
Posted: Sat Aug 20, 2011 3:16 Post subject:
The issue is that the newer version cannot have empty MTU and as per http://forum.hidemyass.com/showthread.php?tid=2700&pid=13288#pid13288 , I have to leave it empty but the versons available for v2 dont have any
===========================================
Server: : SUCCESS Local Address: XX.171.165.17 Remote Address: Client: CONNECTED: SUCCESS Local Address: XX.171.165.17 Remote Address:
Status
LogServerlog Clientlog 20110820 05:15:37 Expected Remote Options hash (VER=V4): 'c0103fa8'
20110820 05:15:37 I Attempting to establish TCP connection with XX.171.165.2:443 [nonblock]
20110820 05:15:38 I TCP connection established with XX.171.165.2:443
20110820 05:15:38 I TCPv4_CLIENT link local: [undef]
20110820 05:15:38 I TCPv4_CLIENT link remote: XX.171.165.2:443
20110820 05:15:38 TLS: Initial packet from XX.171.165.2:443 sid=901fe810 7aac259a
20110820 05:15:38 W WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
20110820 05:15:41 VERIFY OK: depth=1 /C=UK/ST=NR/L=Attleborough/O=Hide_My_Ass__Pro/OU=VPN/CN=vpn.hidemyass.com/emailAddress=ca@hidemyass.com
20110820 05:15:41 VERIFY OK: nsCertType=SERVER
20110820 05:15:41 VERIFY OK: depth=0 /C=UK/ST=NR/L=Attleborough/O=Hide_My_Ass__Pro/OU=VPN/CN=server/emailAddress=vpn@hidemyass.com
20110820 05:15:47 W WARNING: 'link-mtu' is used inconsistently local='link-mtu 1544' remote='link-mtu 1543'
20110820 05:15:47 W WARNING: 'comp-lzo' is present in local config but missing in remote config local='comp-lzo'
20110820 05:15:47 Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key
20110820 05:15:47 Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
20110820 05:15:47 Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key
20110820 05:15:47 Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication
20110820 05:15:47 Control Channel: TLSv1 cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA 1024 bit RSA
20110820 05:15:47 I [server] Peer Connection Initiated with XX.171.165.2:443
20110820 05:15:49 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
20110820 05:15:50 PUSH: Received control message: 'PUSH_REPLY topology subnet route-gateway XX.171.165.3 dhcp-option DNS 208.67.222.222 dhcp-option DNS 208.67.220.220 redirect-gateway def1 ifconfig XX.171.165.17 255.255.255.128'
20110820 05:15:50 OPTIONS IMPORT: --ifconfig/up options modified
20110820 05:15:50 OPTIONS IMPORT: route options modified
20110820 05:15:50 OPTIONS IMPORT: route-related options modified
20110820 05:15:50 NOTE: --mute triggered...
20110820 05:15:50 1 variation(s) on previous 5 message(s) suppressed by --mute
20110820 05:15:50 W WARNING: potential conflict between --remote address [XX.171.165.2] and --ifconfig address pair [XX.171.165.17 255.255.255.128] -- this is a warning only that is triggered when local/remote addresses exist within the same /24 subnet as --ifconfig endpoints. (silence this warning with --ifconfig-nowarn)
20110820 05:15:50 I TUN/TAP device tun1 opened
20110820 05:15:50 TUN/TAP TX queue length set to 100
20110820 05:15:50 I /sbin/ifconfig tun1 XX.171.165.17 netmask 255.255.255.128 mtu 1500 broadcast XX.171.165.127
20110820 05:15:50 /sbin/route add -net XX.171.165.2 netmask 255.255.255.255 gw 50.XX.0.1
20110820 05:15:50 /sbin/route add -net 0.0.0.0 netmask 128.0.0.0 gw XX.171.165.3
20110820 05:15:50 /sbin/route add -net 128.0.0.0 netmask 128.0.0.0 gw XX.171.165.3
20110820 05:15:50 I Initialization Sequence Completed
20110820 05:16:55 MANAGEMENT: Client connected from 127.0.0.1:5001
20110820 05:16:55 D MANAGEMENT: CMD 'state'
20110820 05:16:55 MANAGEMENT: Client disconnected
20110820 05:16:55 MANAGEMENT: Client connected from 127.0.0.1:5001
20110820 05:16:55 D MANAGEMENT: CMD 'state'
20110820 05:16:55 MANAGEMENT: Client disconnected
20110820 05:16:55 MANAGEMENT: Client connected from 127.0.0.1:5001
20110820 05:16:55 D MANAGEMENT: CMD 'state'
20110820 05:16:55 MANAGEMENT: Client disconnected
20110820 05:16:55 MANAGEMENT: Client connected from 127.0.0.1:5001
20110820 05:16:55 D MANAGEMENT: CMD 'state'
20110820 05:16:55 MANAGEMENT: Client disconnected
20110820 05:16:55 MANAGEMENT: Client connected from 127.0.0.1:5001
20110820 05:16:55 D MANAGEMENT: CMD 'state'
20110820 05:16:55 MANAGEMENT: Client disconnected
20110820 05:16:55 MANAGEMENT: Client connected from 127.0.0.1:5001
20110820 05:16:55 D MANAGEMENT: CMD 'log 500'
19700101 00:00:00
Back to top