Jim Zimmerman - ASP.NET, MVC, Ajax and ORM

I just got Verizon FIOS (15 MB down and 2MB up), fiber to the house!  They actually wired cat5 from the outside to my kitchen from the fiber connection.  So I wanted to have my 3 computers in my office be able to communicate wirelessly to the wireless router that was given to me from Verizon.  I had an old linksys WRT54G and decided to search on hacking this router.  By the way you can buy these for like $50 now if you need one.  I wanted to get my WRT54G running in client mode.  Well what do you know, I pulled up this killer open source software that turns your router into a client access point and a nice firewall.  Unbelievable.  It actually works.  I am going to post how to do it here in case this link goes bad.  Follow the instructions exactly and this will work first time.

Instructions:

1. Download the "wrt54g alchemy firmware" (google this, or go here) version 6rc5 from the Internet (it is the only one compatible with the new models wrt54g V2.2 & wrt54gs V1.1).
2. Upload the firmware to the wrt54g via the "Administration->Firmware Upgrade" option in the router's web interface.
3. Reset the device (press reset button until power led flashes - this could take 20 seconds or more). In the following steps, leave all settings which are not mentioned in the description at their default (only change the ones specifically mentioned in the step).
Note: We will use addresses that end in 128-255 for the wrt54g router and it's attached PCs. To make sure there is no overlap in the addresses assigned by the two routers, we have to make sure that your main router only assign addresses below 128 to its own clients. For example, if your main router address is 192.168.0.1, its DHCP address range could be 192.168.0.50 - 192.168.0.120. Another important note regarding the main router: some routers allow you to disable the broadcast of the SSID, but for this setup to work properly the SSID broadcast MUST BE ENABLED (which is usually the default behavior).
4a. In "Setup::Basic setup" screen, set Internet Connection Type to "Automatic Configuration - DHCP".
4b. Set the local IP to 192.168.0.129, assuming your main router is 192.168.0.x (in general, if your main router is a.b.c.d set the wrt54g to a.b.c.129).
4c. Set the Subnet Mask to 255.255.255.128.
4d. Set the "Gateway" to the IP address of your main router (e.g. 192.168.0.1).
4e. Set the DHCP Server to Enabled, and starting IP Address to something above 129 (e.g. 140).
4f. Save the settings on this page. You should reboot the attached PC, since the subnet mask has changed. Note: from now on you have to use the new local IP you set in step 4b (e.g. http:// 192.168.0.129) to connect to the router from your PC.
5. In "Setup::Advanced Routing" screen, make sure operating mode is "Gateway".
6. In "Wireless::Basic Settings" screen, set Wireless mode to "Client", wireless network mode to "mixed", and SSID to your main wireless router's SSID.
7. In "Wireless::Security" screen, set your WEP/WPA settings which match the main wireless router. You should now be connected to the main wireless router. Note: if you have MAC filtering set up on the main router (which allows only specific clients to connect), then obviously you have to add the client router to the list of allowed clients.
To verify that you've established a connection to the main router, you can check the "Status::Router" screen, which should show an IP Address assigned by the main router (which would end with a number below 128), and the "Status::Wireless" page should show the AP Signal strength together with the mac address of the main router. Also you should now be able to ping the main router and even log in to it (using h ttp://192.168.0.1) from the PC attached to the client router (the wrt54g).
8. In "Security::Firewall" screen, disable firewall protection, as this subnet is already behind your main router's firewall. Also make sure that "Block Anonymous Internet Requests" is unchecked.
9. In "Administration::Management" screen, you can leave all settings at their default. You may want to enable remote management and Telnet or SSHD, especially if you want to be able to log in to the wrt54g from a computer which is not directly attached to it.
10. To enable PCs attached to the main router to be able connect to PCs attached to the wrt54g: Login into the wrt54g using telnet or ssh by running the command "telnet 192.168.0.129" and use same root/passwd as for the web interface. Then type this command (copy it exactly):
# echo 1 > /proc/sys/net/ipv4/conf/`route | grep default | awk '{print $NF}'`/proxy_arp
Now you should be able to ping/telnet to any PC attached to the wrt54g from any PC attached to the main router. Btw, this assumes that the subnet mask of the main router is the default 255.255.255.0.

Important note about the last step : The last step (which is an optional step) allows PCs attached to the main router to be able to connect to PCs attached to the client router, by specyfing the IP of the destination PC, for example "telnet 192.168.0.150". But they are still on two different subnets which do not share their broadcast messages, therefore when browsing PCs on the local network you will not automatically see the PCs attached to the other router. But you can always connect to them by explicitly specyfing the IP. Btw, this step was added after the initial posting of this HOWTO and solves a lot of the issues people discussed later in this thread, so don't worry if you read posts in this thread about problems with communicating between PCs attached to different routers. Also note that this proxy_arp setting is not saved in the WRT54G non-volatile memory like all the other settings, so when the router is rebooted (like after a power outage), it will be cleared and you will need to repeat step 10 to set the proxy_arp back on.
Done !!! That's it !!!!

I have to admit, I was skeptical as to what good Live Writer might do.  Why would you just not log in to your blog and add drafts in there?  Well I found out it is very nice to have a free rich text editor that I can save my drafts locally and then preview them on my blog before publishing them.  I am using DasBlog1.9 and Windows Live Writer connects to it right out of the box.  It took literally 10 seconds to connect to my blog.  Pretty cool stuff and it also supports most of the top blog engine out there like:  

You can also write plug-ins to it and can see some examples at the Windows Live Gallery - Writer .  And you can find more info on Windows Live Writer SDK at the live.com blog. 

Here is a picture of Live Writer using Live Writer to add it.  Nice.

Here is a map of where I live, well close to where I live.  Wow, that was easy.  Very cool!

 

This is the first time I have used those features, and I must admit that would have taken much longer in the admin for any blog. 

And now I just downloaded an Event plug-in.  I don't have an event to add right now, but I will soon.  There aren't too many plug-ins available yet, but you know there will be a lot soon.

If you have a blog, try this out.  It has saved me some time and made blogging much more enjoyable.

I was just awarded Microsoft's MVP award this week and am very grateful to many people for helping to make that happen.  This is a great honor and feels good that the work that i have done in the community for the last 12 months is acknoledged. I really have enjoyed speaking at Code Camps and look forward to doing much more next year.   I have learned so much this last year from others in the community.

It all started when I went to my first DotNet Users Group meeting here in Tampa and met Ambrose.  We started to chat about things and I asked him about how one would speak at a Code Camp.  Well Tampa code Camp 2005 was coming up in 3 weeks and he forwarded my info to Joe Healy who has since helped me to become a confident speaker at Code Camps since last year.  Joe has definitely influenced me a lot and has introduced me to people I would not have met otherwise.  I also want to thank Shawn Burke, who has helped me be part of a very smart software team on codeplex with the Atlas Control Toolkit.  They really have taught me what it's like to be part of project bigger than just your own.

I also want to thank Keith Kabza, who is president of the DotNet Users Group here in Tampa.  Working with him has taught me some very useful tips and tricks for C# development.  We helped build a Code Camp starter Kit that has yet to be put into beta, but it has worked for at least Tampa Code Camp last July.  If there was only more time in a day.

Now that I have control over my blog using DasBlog, I plan on blogging a lot more and adding some quick demos to this site, so keep in touch and subscribe to my feed.

I finally figured out how to set up dasblog and import all of my posts from blogger to Dasblog.  I will add a post later on how i did this and what other ways there are to do this.

This is my first post on my new blog engine and am very happy with it so far.  I love the control.  Thanks so much to the dasblog team for making the software so easy to install and configure.  I am anxious to start posting from live writer also.  but i better get some sleep first.

.NetTiers has just released it's 2.0 version and it is the best architecture / code generation template ever released. For those of you who do not know about the whole code generation thing, I feel sorry for you. You will not believe the amount of time you will save generating code. I have been writing my own code generators since 1998 when i used Lingo to write html and perl. No joke! Anyway, I have been writing a vb and c# code generator the last 3 years for my own good, but ever since I stumbled across nettiers template for codesmith, I have stopped my own development. These guys knock it out for you. It is the best code generator template out there for .net 2.0. I religiously use this for every project i have had for 6 months now. The new release fixes many things and is very easy to use. You can definitely take extreme programming to the next level with this stuff.

Well as you can see I am pretty excited about this stuff and so much that I asked if I could help with nettiers. I was lucky enough to be added as a developer to the open source project. I am going to focus on adding some atlas / ajax to the admin since it is what i have the most passion for and experience playing around with the atlas control toolkit for the last 4 months.

Well the guys at Microsoft released the September release of the Atlas Control Toolkit. This is a great release with some cool features like animation and nobot along with some cool sliders. My balloon did not get in this time around because of some unforeseen bugs. Those guys are fun to work with and they work very hard. I see code check ins at midnight and sometimes 3 in the morning. They really worked hard to get this release solid and you can tell when you look at it. Have fun! The animation stuff is really amazing. You would swear its flash.

I don't know about you all , but I think the biggest ajax problem is the "back button problem". For example, I built this cool build a car application and my wife would click the next button and then when she wanted to change something and go back she would hit the back button and say, "What happened? Where did the car go?". That was when I realized that we had to come up with a solution for the back button browser problem in ajax. Well it looks as if Nikhil has come up with a good solution for this problem here: http://www.nikhilk.net/BackButtonSupport.aspx . I haven't had time to implement his stuff, but he is the father of Atlas, so I am sure it probably works as advertised. He has some great stuff on his site on how to implement it.

Scott Guthrie just announced Atlas 1.0 Naming and Roadmap. This is great because it will be released to work with vs 2005 and be fully supported. They listened to alot of people that want the new technology now and they are delivering. Here is a little excerpt of what he said:

"Many people have asked us to deliver a fully-supported 1.0 release of �Atlas� before the next release of Visual Studio. �Fully supported� means that Microsoft product support services are available 24 hours a day, 7 days a week, 365 days a year and that any customer can obtain hotfixes if they encounter a bug affecting their application. It also means that the product has a committed servicing product lifetime of 10 years � which provides companies with the ability to depend on it for mission critical applications.

I am excited to announce today that we are going to ship this fully supported �Atlas� 1.0 release on top of ASP.NET 2.0 and ensure that it works with Visual Studio 2005. Our goal is to ship the �Atlas� 1.0 release around the end of this year. The plan is to first have a Beta, then an RC, and then decide on the final date based on customer feedback."

Good stuff!