I went to SCaLE last weekend, and was very happy to talk to the people at the IPv6 booth. I also jacked one of their "getipv6.info" stickers cause it looked neato & unixy. A day later I stuck it on my laptop (along with some other nice linux/gnu/openvz buddies); and a day after that I started on my journey to IPv6.
I've been working through IPv6 Essentials in my free time, and actually implementing it at home! I started out by bricking my router (earlier post), followed by epic failure when trying to configure IPv6 on my router. I was rewarded with a little success before I had to call it quits late at night. I manually assigned my IPv6 address to my mac and everything worked wonderfully (ipv6.google.com for example)
Well I was dis-satisfied, and spent the better part of my day at home (Thursday 25, 2010) getting it to work on my router. Now everything works & I can reboot my router & expect everything to come back when it's back up. I will post how I got everything working ASAP since the current IPv6 articles are dated & chock full of mis-information.
In the process of moving to IPv6 at home I needed to make my dyndns IPv6 compatible. Well dyndns isn't IPv6 compatible (for free anyways), so I decided to switch to FreeDNS. It provides AAAA record support (IPv6), and allowed me to pass onto the next level of the HE.net certification:
Yay! I'm an IPv6 Enthusiast...
After reading through IPv6 Essentials I can see the real plusses to IPv6, and can't wait to take advantage of all it's neat features.
Wow, so last night I tried to flash an unsupported ddwrt image on my WRT350N & I bricked it :(. I would have been golden, except for some reason boot-wait wasn't working. I spent about 30 minutes looking what new router I should purchase, when I thought, ah there are no good routers out that will accept DD-WRT; I'll just unbrick my current router...
Well to start I had to figure out how to open the darn thing. I ended up ripping off the top & bottom plastic where some nice torx security screws greeted me... Well a few came out with some nice twists of my torx driver. Yet a couple actually had the center pin proper height. Easy way to get around this, is to find a small phillips screwdriver. I was able to easily unscrew them with a phillips.
After removing the screws I was now able to access the board; most importantly the serial header:
From Left to Right (Yellow = 3.3V; White = Tx; Red = Rx; Black = GND)
I used my handy dandy CA-42 Serial to USB adapter:
It also has colored wires, and I should have matched them up, but I kinda just plugged some alligator clips in & plugged them into the right wires for the CA-42. The CA-42 layout is like this (Black = GND ; White = Rx ; Green = Tx ; Red = +V)
After connecting everything up, you should be able to see "output" & be able to hit Ctrl-C to be dropped into CFE>
nvram set boot_wait=on
nvram commit
reboot
Now prepare to copy the image over. I had three windows open. A window with the serial output, a window pinging 192.168.1.1, and a window to execute my push command. I would also recommend that you set (IP Address = 192.168.1.10 ; Subnet = 255.255.255.0; Gateway = 192.168.1.1) Once you receive a ping after rebooting run the following command:
where 'dd-wrt.v24_mini_generic.bin' is the image you would like to flash (it took me about 6 different images until this one worked [ this is the web flash image on the wrt350n page])
After running the following you should get something that looks like this:
If everything went as planned, then you should end up with a working router :) Yay!
There are plenty of resources on the internets. I found this wonderful link: http://dg.cascade.dyndns.org/wrt350n.html which perfectly outlines EVERYTHING I needed to do. It was very helpful in this process.
That is unrelated, you DO NOT need to cut open the CA-42. Just get some alligator clips & clip them to their respected places on the router motherboard, and then connect those to the correct wires of the CA-42. http://www.flickr.com/photos/68444690@N00/4385664594/
Router: From Left to Right (Yellow = 3.3V; White = Tx; Red = Rx; Black = GND)
Ca-42: (Black = GND ; White = Rx ; Green = Tx ; Red = +V)
Ok, I know how to connect the CA-42 to the board with alligator clips, like you say. I already seen that page but I still doubt. (http://dg.cascade.dyndns.org/wrt350n.html)
1) The question I have is the following:
If I strip the USB connector (like you pic) and use the alligator clips with the board. How connect the other end (Pop-port) to the computer?
2) Another question. I can use the wires of the Pop-Port (phone connector) with alligator clips to the board and then connect USB port to the PC?
I already made the connection with the cable to the router and I can see the booting but when I write something only strange characters appear or letters that do not match the letters you press in CFE mode.
I dislike .bin/.cue combinations for a few reasons. But the biggest is that Mac doesn't natively support mounting them. Good thing I have macports to install linux programs.
Firstly lets install bchunk (use your favorite package manager, or macports on the mac)
# Mac Installation
sudo port install bchunk
Then locate your .bin/.cue combinations and CONVERT!
jg_mbp:CBT NUGGETS CISCO CCNA CCENT EXAM-PACK 640-822 ICND1 jgerold$ bchunk agcnccci.{bin,cue} CCENT
binchunker for Unix, version 1.2.0 by Heikki Hannikainen <hessu@hes.iki.fi>
Created with the kind help of Bob Marietta <marietrg@SLU.EDU>,
partly based on his Pascal (Delphi) implementation.
Support for MODE2/2352 ISO tracks thanks to input from
Godmar Back <gback@cs.utah.edu>, Colas Nahaboo <Colas@Nahaboo.com>
and Matthew Green <mrg@eterna.com.au>.
Released under the GNU GPL, version 2 or later (at your option).
Reading the CUE file:
Track 1: MODE1/2352 01 00:00:00
Writing tracks:
1: CCENT01.iso 338/338 MB [********************] 100 %
jg_mbp:CBT NUGGETS CISCO CCNA CCENT EXAM-PACK 640-822 ICND1 jgerold$ ls
CCENT01.iso agcnccci.bin agcnccci.cue
# ^Yay a new .iso
Mike, 
JJ, 
Christian 10:28 pm on February 25, 2010 Permalink
Yeah. That is awesome. I wish I had your skillz!
JJ 5:47 pm on March 8, 2010 Permalink
Hi, I brick my route last week :S and searched everywhere, but i dont know how to hack a CA-42 and connect to the router.
You can help me? I have alligator clips and CA-42 Serial to USB adapter. You cut the USB port like http://www.flickr.com/photos/68444690@N00/4384883733/in/set-72157623377212337/ but, how i connect the other end?? as a serial port?
If you have a some pic or a tutorial in how to do it would very grateful to you.
I do not understand, I found this https://forum.openwrt.org/viewtopic.php?id=22620 and this http://buffalo.nas-central.org/index.php/Use_a_Nokia_Serial_Cable_on_an_ARM9_Linkstation but as you can see, they cut the Pop-Port (phone connector).
thanks in advance,
JJ
Jonny Gerold 9:41 am on March 10, 2010 Permalink
Oh hai,
That is unrelated, you DO NOT need to cut open the CA-42. Just get some alligator clips & clip them to their respected places on the router motherboard, and then connect those to the correct wires of the CA-42.
http://www.flickr.com/photos/68444690@N00/4385664594/
Router: From Left to Right (Yellow = 3.3V; White = Tx; Red = Rx; Black = GND)
Ca-42: (Black = GND ; White = Rx ; Green = Tx ; Red = +V)
I would take a look at this link also: http://dg.cascade.dyndns.org/wrt350n.html
Let me know if you need any more help…
JJ 12:57 pm on March 10, 2010 Permalink
Hey tranks men,
Ok, I know how to connect the CA-42 to the board with alligator clips, like you say. I already seen that page but I still doubt. (http://dg.cascade.dyndns.org/wrt350n.html)
1) The question I have is the following:
If I strip the USB connector (like you pic) and use the alligator clips with the board. How connect the other end (Pop-port) to the computer?
2) Another question. I can use the wires of the Pop-Port (phone connector) with alligator clips to the board and then connect USB port to the PC?
Thanks
JJ
Mike 11:08 am on April 12, 2010 Permalink
Hello,
I already made the connection with the cable to the router and I can see the booting but when I write something only strange characters appear or letters that do not match the letters you press in CFE mode.
any advice?
regards