DDNS on WRT54G

I have an DDNS account at http://www.dyndns.com. I can't seem to locate the DDNS configuration page in the router management module. How do I configure my router to periodically update my IP address to http://www.dyndns.com?

Take a look on this article to help you: DynDNS.com - 2 Easy Ways to Notify the DDNS Servers on IP Change
Hope helps..

Similar Messages

DDNS on WRT54GS

Recently I have been trying to get ddns running on my router. Before I was having a problem where it says "Can't connect to remote site, DDNS update fail!". After updating the firmware for the router the status simply says "Updating DDNS status ..." I am able to ping the address without a problem, and all my user info for dyndns.org is filled in correctly in the router menu. Does anyone have any ideas as to what is causing this and how to fix it?

Would suggest you to assign the static DNS 1=192.168.1.1, DNS 2=4.2.2.2 & you should be able to go online wirelessly without any issue.

WRT54G v8.00.0 will not update DDNS

I just setup a new custom DDNS account with DynDNS, and got the following error on WRT54-g v8.00.0
"Name resolver fail, DDNS update fail!"
I sent DynDNS an email and they said it was not their problem, that I needed to contact Linksys.
I got a similar error on a trial TZO acct:
"TZO echo server update public ip fail"
ISP is Cox Cable, Fairfax, VA
Cable Modem: Scientific Atlanta DPC2100R2
MAC: 001AC359F962
Is it possible that the ISP is blocking this transaction? Suggestions on how to solve this problem? I really wanted to use the router rather than running some client on one of my machines on the network if possible.
Thanks,
Lee Fairfax, VA USA

Hi, I had the same problem with my WRT54G v7.00.5 firmware.
I believe the problem is because our routers are unable to resolve domain dyndns.org to its IP address.
Using the utility CD from Linksys, I got the message that my router is not connected to the internet although the computers in my network can connect to the internet.
In the admin web, I went to "Administration" tab >> "Diagnostics" sub-tab >> Ping >> enter "dyndns.org", 5 times >> click Ping and the dyndns.org was not resolved.
I then entered "dyndns.org", 10 times >> click Ping >> and strangely enough, my router is now able to resolve dyndns.org
I rechecked the DDNS settings and now it's working!!
Therefore, my suggestion is for you to play around with the diagnostics tab and hope you get the same result as I had.
You might also want to try the Traceroute. I hope this helps : )
Cheers, arief bin basuki
Message Edited by ibn basuki on 12-15-2007 02:00 AM

DDNS service on a WRT54GS router

Has anyone been able to user the DDNS service on a WRT54GS router?
Message Edited by sshahir on 12-27-2007 06:16 PM

Hello oook,
Thank you for your reply.
I have used the auto detect IP address (65.95.79.113) recommended (by LinkSys on the Setup/DDSN tab and dyndsn.com web page) to associate the host name initially prior to configure my router DDSN. In other words, first, I have associated the host name (http://sshahir.dyndns.org) to the recommended auto detect IP address (65.95.79.113), and then, I have successfully been able to configure DDNS on the WRT54GS router (according to the message appears on the Setup/DDSN tab). I believe my router DDNS doesn’t work properly regardless the successful DDNS configuration message because the IP address assigned to the host name hasn’t been changed and updated since then, and I cannot browse the web server located behind the router.
Have you assigned a static IP address to your host name (i.e. hostname.dyndsn.com)? If not, please let me know what IP address you used to associate with the host name prior to configure your router DDSN? Has your router DDSN been able to update the IP address associated with the registered host name? If you have used the same IP address (65.95.79.113) initially, and the DDSN works properly, please let me know the firmware version you are using on your router.
Thank you,
sshahir

Bizarre WRT54G, DDNS, internet connectivity problem

The other day, we lost power at home (my cable modem and router are not on a UPS - they will be shortly). The problems started soon after that (it can't be a coincidence, but I'm stumped as to how they are related). After everything powered up, we could no longer connect to the internet from any machine on the network. When I checked the WRT54G however, I found that it was connected to the outside world and had a valid IP from my ISP. Poking around from outside my network (at work, for example) showed me that if I try to connect to my web server, I instead am routed to the router setup page (I have remote config turned off and port forwarding on, and it has worked flawlessly in the past).
Further investigation showed that my DDNS service (TZO.com) was not working (the error message is "Connect to server fail"). I double-checked with TZO and they do not see an issue on their side.
Any ideas for further investigation? I'm stumped at this point. I'd almost say the power problem fried the router, but if it did, it seems to be an awfully selective frying. Thanks in advance, and please let me know if there's additional information needed to help.
My setup:
Time Warner Roadrunner cable modem (not sure of the type/model)
Linksys WRT54G router, firmware 4.21.1
TZO.com DDNS service
Solved!
Go to Solution.

Well try upgrading the firmware of the router & keep on holding tightly the reset button in such a way that power light is blinking on the router & then do a complete network power cycle i.e., unplug the power cables from the modem & from the router & then plug in the power cable to the modem first once all the lights are solid green you could plug in the power cable to the router & check out it will definately work!!

WRT54g DDNS problems

I am trying to set up FTP so family outside my network can access my files, however under the DDNS area of my router it displays the wrong internet IP address for my network. For some reason it will only display 192.168.1.7, instead of my actual IP. It will not let my change it either. I have tried to upgrade the firmware and still nothing. I am tryng to set it up to work with DynDNS.org but 192.168.1.7 will not work in place of my actual IP. So if there is a way to change this in the router then I will be ok.

Who is your ISP ?
Under the DDNS tab it will display you the IP address which you are getting it from your ISP... To find out the WAN IP address which your ISP is providing your, Login to the Router setup page and then click on the "Status Tab". I think it will the same IP address which you have mentioned in your Post...
Well its not possible to change the Internet IP address under the DDNS tab, it will be automatically released when your ISP will release that IP address.

Wrt54gs ver 2.1 DDNS issue

I have a dyndns account. I set up the ddns service on my router. The status says 'ddns is updated successfully', but the internet IP address displayed is not the current IP address of my connection. And I can not connect to the router using my dyn alias.
Can you offer any suggestions?
Message Edited by bbb2008 on 01-10-2009 01:36 PM

Kindly let me know for what purpose you are using the dyndns account ? What exactly you want to establish with the dyndns account ? Please explain in detail...

Problem with WRT54G and DSL NAT router

I have a WRT54G connected to a Westell DSL NAT router. I would like to be able to allow incoming connections to my FreeBSD server.
The Westell router allows me to set IP Passthrough (they call it "Single Static IP"). This gives the WRT54G the outside IP address given to the DSL router. I can then set up the WRT54G for DDNS and port forwarding to forward specific ports I want to my server.
This works, for about 2-3 days. Then, I start to randomly lose outside connectivity. Web pages start coming up with missing elements, or taking a long time to load. This will eventually lead to total loss of outgoing communication.
Normally, I would blame this on the Westell NAT router, but as I'm losing connectivity to the internet, I'm also losing connectivity to the WRT54G. It will try to load configuration pages but will be slow with missing elements, etc.
All communications between computers on my inside network continue to function properly, it's just connectivity to the WRT54G and the internet that seem to start to fail.
Does anyone have any idea what is going on? I just upgraded the firmware on the WRT54G from 1.01.1 to 1.02.0, but I don't imagine this will help.
Thanks,
David Chamberlain

Try setting the MTU to manual and change the value to 1450
"Only those who risk going too far can possibly find out how far one can go..."

Remote Desktop Connection with WRT54G from Novice

Well, I’m usually pretty good at using Google and forums to eventually figure out how to fix my problem but this one absolutely has me stumped and I’m hoping someone out there has an answer for me. For the record, I have probably a beginner/intermediate knowledge of computers so if you know the answer to my problem, try to explain it simply! ****TO ANYONE WHO TAKES THE TIME TO READ THIS THING AND CAN OFFER SOME ADVICE-THANK YOU!!!!***
THE PROBLEM
I would like to be able to use Remote Desktop to log into either of my home computers from basically any computer on the internet.
THE SETUP
I have two computers, whose names are LAPTOP and DESKTOP that are both running Windows Vista Ultimate. Both of the computers are connected to a Linksys WRt54G Router ; one wired, the other wirelessly. The Linksys router is then connected to a Westell DSL Modem that connects to AT&T’s internet service.
SETTINGS
My DSL service only provides me with a dynamic IP address so I signed up with no-ip.com. Through that site, I bought a domain name and downloaded their small program that runs in the background of my desktop computer. The program checks what my IP address is every couple of seconds and if it changes, it notifies their server so that anyone who types in my domain name is directed to the new IP address.
ROUTER (Firmware 4.20.6)
Basic Setup Page: The Router Name is just the model number, the Server Name is my DSL provider and the Domain Name is the name I chose and registered with No-IP.com. (www.mydomainname.com, for example.) DHCP Server is ENABLED. DDNS Service is DISABLED. Under Advanced Routing, it is set in GATEWAY mode.
Security Page: Firewall Protection is ENABLED. Block Anonymous Internet Requests is NOT checked. Filter Multicast, Filter Internet NAT Redirection and Filter IDENT ARE checked.
Applications and Gaming Page: I chose two port numbers, one for each computer that I want to connect to. On the first line, I have Application: RDP, Port Range: 49200 to 49200, Protocol: Both, IP Address (The IP address of the computer I want to connect to) and the Enable box IS checked. [I did the same thing with the second line for the other computer, but with a different port number and that computer’s IP address)
Administration Page: Access Server is HTTP, Wireless Access Web is ENABLED, Remote Management is ENABLED through Port 8080, and UPnP is ENABLED.
WINDOWS VISTA SETTINGS
First, I went to the Remote Desktop Settings of the target computer and ENABLED Remote Desktop Connection and allowed computers running any version of Windows. I also confirmed that the box labeled “Allow This Computer To Be Controlled Remotely” WAS checked. I then made sure that I had a user name, it had a password associated and that it had Administrator priveledges. I went back to the Remote Connections screen and added the user name as being allowed to connect. (I think this is redundant since it’s both the owner of the computer and has Administrator Status.)
Next, per Randomly Googled Internet Advice, I went into the registry and changed the port number that Remote Desktop listens for incoming connections to Port 49200 to match the router settings. [Registry Entry that I modified was: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp]
Finally, I went to the Windows Firewall and Added (opened) port 49200 for use as a Remote Connection. I kept the protocol as TCP and confirmed the scope was set for Any Computer.
CURRENT STATUS
If I go to Explorer and enter my IP address with a colon and the specify port 8080, I can get the login screen for the router. Same thing happens if I just enter my domain name and port 8080. However, if I switch the 8080 port and use one of the ports I chose (49200), it cannot connect, either using the Public IP address or the domain name. (I’m trying to connect using a wireless card and not connected to my local network so I know it’s the same as if I was anywhere else.)
I’m not sure why it won’t let me connect; it feels like the router will not allow the connection to pass through it to the port I’m asking it to forward to. I’m guessing someone out there who took the time to read it is shaking their head at all the information I provided and knows the one dumb thing I missed!
Thanks again!

I'm attempting to do the same thing with my home network. the only differences are that i have cable internet from comcast and i'm running vista business. my router is the wrt54gs. i'm assuming that the web page is similar for adjustmants. To be honest i cannot figure out how to do a remote destop too. so i went to www.logmein.com and installed the program. once installed to to every computer you want to have access too and log into the website. then click on the add computer icom. full control app sharing etc... even better when you connect you have the option to deactivate the local host mouse and screen to prevent anyone seeing what your doing.
If you resolve the router issue would you let me know. plz thanks
Forest

WVC200 v1.2 - Successful Wireless & DynDNS Setup with WRT54G v.6 Router

I would just like to report that after hours of tinkering, I managed to configure the camera to run wireless as well as link up with the dynDNS service. I thought I would post the method which worked for my WRT54g/WVC200 combo. Hopefully this will help anyone still stuck on setting it up.
You want to set everything up using wired connections exclusively until everything is working and you are ready to jump to wireless.
Reset your WRT54G router to factory default settings. If you can't access the admin page simply press the reset button on the back of the router and hold it down for about a minute (should reset to factory spec). I am using the latest firmware for each device (linksys phone support can help you with firmware if you don't have the latest stuff, or you can look for other threads on the topic).
Now that your router has a fresh install, unplug its power supply for now. Turn your attention to wiring. Make sure you have a powered-off PC connected to one of the ethernet ports on the router.
Power up your router first, giving it time to boot (usually under 30 seconds). Then power up your PC and pay a visit to your blank router at http://192.168.1.1 user:admin password:admin and leave your internet settings alone for now (they shouldnt affect your camera setup later as long as you have a typical dynamic IP internet connection)
In the first page for the router setup, make sure you use DHCP for the local network (I believe this is the default setting) and set a healthy DHCP user limit. *Apply/Save Settings*
In the wireless menu, broadcast on G-only, channel 6, assign an easy to remember SSID ("smithnetwork" etc) *Apply/Save Settings* . In the wireless security tab, choose WPA, TKIP, and type in a good passcode (strongest passwords are 10 or more randomly typed letters and numbers) *Apply/Save Settings*
Click on the Administration tab, set an equally strong password to access the router setup (can be the same as your wireless encryption passcode if its strong). Additionally, make sure UPnP and Remote Management are disabled, Wireless Management enabled. *Apply/Save Settings* (this should now prompt you for the password you just created in order to return to the router setup)
Go ahead and connect to your newly broadcasting network from a laptop wireless card etc. (which should still give you limited connectivity even if you haven't configured your internet settings yet) by going to http://192.168.1.1 in your browser like I said earlier. If you manage to get to the router menu then you know your wireless network is functioning at least to a certain degree. If you are stuck here, its probably not too complex of a problem for linksys phone tech support to get you back on track.
Note: If you have been tweaking camera settings prior to this attempt, you might want to turn it on without any network cables hooked up and try holding the reset button down (like we did to restore the router's factory settings earlier).
Now get your WVC200 camera and hook up the ethernet cable to one of the open ethernet ports on your router and the port on the camera. Plug in the camera's power supply. At this point, the camera should boot up, calibrate the servo motors, and attempt to join your router's LAN. If your camera does ANYTHING but connect to the network successfully and give you a local IP, you have a problem I haven't encountered and you should re-read the instructions or consider an RMA.
Default Local IPs (assuming each device joined the network in proper order)
Router: 192.168.1.1
Your ethernet-wired PC: 192.168.1.2
Your wirelessly connected laptop: 192.168.1.3
Your camera: 192.168.1.4 (this is what your camera should display on the LCD)
At this point you can confirm your camera is properly placed on the DHCP client table by getting into your router setup and clicking the status tab > local network > DHCP clients table. You should find your 3 devices connected, assigned the above IPs, and you should see the camera (named "WVC200" on the list). Again, if this is not the case for you using factory settings, I reccomend talking to linksys phone support or RMA the item.
Now close all your browsers and load a fresh internet explorer, navigating to the camera's local IP address (should be http://192.168.1.4 or whatever your client table listed). This is basically how you configured your WRT54g router earlier (even uses the same admin/admin login).
Once you're in the camera management page, click on the setup tab. Note the sub-menu that appears on the left side, click on "basic" and make sure camera name is WVC200, LCD/LED enabled, Daylight savings checked, NTP automatic server un-checked, make sure Automatic (DHCP) is set.
Wireless SSID "smithnetwork" or whatever you assigned it earlier in the router wireless setup, network type: infrastructure. *Apply/Save Settings*
In the same Setup > Basic menu, at the very bottom of the page should be the wireless security settings ( default should be "disabled" ). Click the "edit security settings" button, select WPA Personal, it should be on the TKIP algorithm, and don't forget to enter the wireless WPA password you created earlier on the router. *Apply/Save Settings* also: click *Apply/Save Settings* on the main page again too just to be sure it applied. The security settings should now display when you reload the page.
While we are in setup, click on the "users" link to the left, replace the default administrator login with your own custom one, making sure to check the "enable authentication" box. *Apply/Save Settings*
At this point, you should have your WVC200 fully configured and broadcasting video on the wired LAN, if this is not the case, I would have no clue why it wouldn't work with the same equipment and method and you are out of luck.
Now, for the moment of truth! You should have your router right next to you with wireless ready to go (you tested this earlier) and the camera antenna installed on your WVC200. Unplug the power from the camera, unplug the ethernet cable that connects the router and camera to one another, and plug the power back into the camera. After the lens calibrates and stops moving, the wireless LED should light up and probably start flickering as it negotiates a connection with your router. It should find your network and display an IP fairly quick (probably 192.168.1.4 default). If it takes longer than 15 seconds youre probably out of luck and should double-check everything in this post and move on to a different post if it still doesn't work.
I used to spend hours at this point, wondering why it wouldn't join my perfectly functional wireless network. It would try to connect to the wireless network for about 5 minutes, it would appear to successfully connect sometimes, but it would display the incorrect local IP address and would refuse to function regardless of its self-proclaimed connectivity. I learned that the router's WPA2 encryption was overpowering the puny WPA + TKIP on the camera even though I was using AES/TKIP combo on the router (which was supposed to make the router compatible with original WPA + TKIP devices while still letting you use WPA2). Maybe Linksys can include a fix for this in future router/camera firmware.
To make sure the wireless is functioning properly, open up an internet explorer window and try connecting to camera management page again (http://192.168.1.4 by default) while your camera still has no ethernet cable hooked up to it. Check to make sure you can see video etc. I never experienced signal problems like other users did. This combination of router/camera worked well (-21 dB with it sitting next to the router, -39dB in the other room)
DynDNS Service setup:
I basically figured out that while the DNS features on the camera might be useful to some, its still buggy and there is a MUCH more powerful dynDNS feature on the WRT54g router itself. Navigate to your router (default: http://192.168.1.1 ) like you did earlier and get into the setup page. Click the "DDNS" menu and select the dyndns.org, enter your username, password, and domain name. I am assuming you already have a free dyndns account created or would otherwise have no issue setting up an account with them, so I won't cover that in my post. By clicking *Apply/Save Settings* assuming you configured your internet access through the router like you always did, the router should ask your cable/DSL modem what its WAN IP is and display it (the dynamic internet IP address that was making life difficult for you). What's nice about the router handling this task is that the router is usually first to know when the modem changes the IP (therefore it will immediately log in for you and update the dynDNS).
**Important** This camera uses port 80 by default, so while youre still logged into the router managment page, click on the "Applications & Gaming" menu and type an application name like "linksys" , start port 80, end port 80, TCP only, specify the camera's local DHCP address (default: 192.168.1.4) and don't forget to enable it by checking the box then *Apply/Save Settings*
I would allow at least several hours for the dynDNS servers to apply the changes before becoming concerned, but who knows maybe it will work right away for you. At this point, you should have plenty of functionality to play with the rest of the features of the camera, enjoy! I will post any additions/revisions if need be.
-Sloth

Hello -sloth !
Very easy understanding guide !
I have made all what you suggested.
But now I cannot add the camera in the monitor > setup page.
I can see the camera in the camera list WVC200.
IP 192.168.15.101
port 80
But when I press add, I get "connection fail".
Is the port still 80 - since the Channel is set to 6
I have done no port forwarding as other has suggested.
Checking with the browser at : 192.168.15.101
Page can't be found .....
The router says:
WVC200 192.168.15.101 LAN 00:18:39:35:6A:13 23:24:26
The camera displays the same ip .......
The router setup page : Local IP 192.168.15.1
IP Address Range : 192.168.15. 100 to 149
I have made a system restore, and installed the camera sw again.
If I unplug the lan and turn to wireless the camera LCD display: 192.168.1.115 DHCP
But that page cannot be found ......

WRT54G; What is latest version of firmware ?

I have a WRT54G v4 and somehow I had noticed I upgraded to 4.30.5. When I went to web to see if I still ahd latest it said 4.21.1 was latest. So, I quickly re-flashed with 4.21.1. I went into the 4.30.5 release notes (below) and it DOES say WRT54G. What's up ?
Linksys, A division of Cisco Systems, Inc.
Product:                WRT54G
Classification:         Firmware Release History
Firmware Date:  04/27/2006
Release Date:           05/25/2006
Last Firmware Version: 4.30.5
Firmware 4.30.5
- Resolves UPnP vulnerability reported by SANE
Firmware 4.30.2
- Resolves issue with filter name
- Resolves issue where service name for PPPoE cannot be added
- Resolves issue with detecting UHP modems
- Resolves issue where DynDNS Custom and Static accounts cannot be used
- Resolves issue with WEP passphrase not recognizing spaces
Firmware 4.20.7
- Resolved issue with SecureEasySetup button delay
- Resolved issue with SecureEasySetup overwritting current wireless settings
- Resolved issue with not being able to disable SecureEasySetup button
- Resolved issue with Diag light being constantly lit after upgrading to 4.20.6 on v.1 hardware
- Resolved issue with iDefense security vulnerability
- Resolved issue with L2TP disconnect
- Resolved issue with SecureEastsetup long button push not resetting wireless settings
Firmware 4.20.6
- Resolve issues with setup wizard
- Updated wireless security menu
- Resolve issues with port based QoS
Firmware 4.00.7
- Adds SecureEasySetup push button support
- Resolves large file transfer issues
- Resolves issue with enabling TKIP after enabling WEP
- Updated QoS features
- Resolves issues with multiple Access Restrictions policies
- Resolves issue where multicast breaks when MAC filter status changes
Firmware 3.03.6
- Supports hardware version 3
- Updated help file
Firmware 3.03.1
- Wi-Fi certified
Firmware 3.01.3
- Updated wireless driver
- Supports hardware version 2.2 (cannot downgrade to previous versions)
- Resolves issue with VoIP adapters
- Resolves issue with long domain names
Firmware 2.04.4
- Updated wireless driver
- Updated certificate generation for https access
Firmware 2.04.3
- Resolves issue with disabling firewall
- Added QoS function
- Added Port Triggering function
- Added L2TP option for WAN connection type
- Added ability to back up and restore configuration files
- Added Wireless isolation function
- Added ability to filter internal NAT redirection
- Added ability to restrict access to web GUI from wireless clients
- Added ability to filter IDENT port 113
- Resolves issue with HeartBeat WAN connection
- Added support for 40/56bit cipher to support old browsers to use https
- Resolves issue with PPTP passthrough
- Changed WPA Group Key renewal time range to 600~7200 seconds
- Added IGMP proxy support
- Added ability to allow web GUI access only through https or http
Firmware 2.02.2
- Updated wireless driver to support all versions of WRT54G hardware
- Adds support to allow WAP54G connect as a repeater
- CTS protection mode set to disable by default to improve wireless performance in normal environments
- Resolved issue where the WLAN LED stays on even when wireless is disabled
- Resolved security vulnerability causing the web server in the router to crash
Firmware 2.00.8 (WRT54G v.2 only)
- Updated wireless driver
Firmware Version 1.42.2
- Updated wireless driver to 3.31.15
- Added URL and contents filters
- Added L2TP passthrough
- Added HeartBeat Signal support
- Resolved issue with Connect on Demand
Firmware Version 1.41.2
- Updated GUI format and layout
Firmware Version 1.30.7
- Adds UI control to enable/disable frame bursting
- Resolves issue with firmware upgrade error in Internet Explorer 6.0.2800.1106.xpsp2.030422-1633, on Windows XP pro.
- Send 192.168.1.1 to disable DynDNS
- Resolves issue with using the 4th tx key for WEP
- Resolves issue with disconnecting PPPoE causing WPA to be disabled
Firmware Version 1.30.1
- Adjust PPTP max MTU value from 1400 to 1460
- The router is now certifiable for the UPnP logo
- Complies with final 802.11g standard
- Improved performance asymmetry between the transmit and receive paths
- Receive Broadcast packets from renew state. Some DHCP server (Dlink 300G+) send broadcast ACK after it receives a REQUEST
- Fix: The firmware upgrade will fail, if DDNS updates while upgrading
- Fix: If first DNS address fails, the second or third DNS address will be used to resolve domain names
- Added the following items under Setup Page:
    - Router Name
    - Manual Time Server
    - MAC Clone
    - wireless domain
    - Security Settings
- Added the following items under System Page
    - UPnP enable/disable
    - Ping Test and Traceroute
- Added the following items under Wireless Page
    - CTS Protection Mode
    - Basic Rate
- Added the following items under Status Page
    - Router Name
    - Start IP Address
    - End IP Address
- Added Wi-Fi Protected Access(TM) support including AES and TKIP encryption
- Resolves issue with Port Forwarding name showing up as garbage characters
- Added "B-Only" option to wireless modes
- Added "Default" option to Basic Rate settings
Firmware Version 1.02.1
- Incorporates updates found in the Draft IEEE 802.11g version 6.1 specification
- Resolves interoperability issues with legacy 802.11b devices under Mixed Mode
- Resolves a performance bug where the performance in a mixed b, g network did not go up once the last b client disassociated
- Resolves issue where WEP degrades performance
- Resolves issue with TZO DDNS Service
- "Domain Name" replaces "name"
- TFTP server will only verify image file name "xxxx.bin"
- MAC Address Filter under the Advanced tab works on both wired and wireless clients
- Fixed a bug that prevented wireless clients from connecting to the Internet if there was no active wired PC (PPoE customers in Europe and China only)
- Support for UPnP enabled applications such as MSN Messenger
- Fixed a bug that caused computers connected to the LAN ports to be dropped at some interval only to be immediately re-connected
- Fixed Dynamic Routing issue between 2 Routers
- Allows User to name Static Route Configurations
- Modified PC List Web Page to avoid confusion
- Stabilized Wireless-G to LAN and WAN Throughput
- Stabilized Wireless-B to LAN and WAN Throughput
- Improved LAN-WAN Throughput
Firmware Ver.: 1.01
- Initial release

History.
Linksys released the 4.30 firmwares for the WRT54GL model which are compatible with the WRT54Gv1-v4.
I guess some people were confused to see WRT54GL on the web interface of the router although they had a WRT54G.
Thus they re-released the firmware for the WRT54Gv1-v4 with 4.21.* showing the correct model name.
You should be able to use either firmware for either router. If you check the release notes of 4.21.* and 4.30.* you'll notice that they basically have the identical history of changes. 4.30 is now a little bit more advanced if you look on the WRT54GL downloads page.

WEBSITE BLOCKING ON WRT54G V6

website blocking functionality of the WRT54G V6 router is working using the latest firmware 1.02.0
Step by step procedures: (Complete procedures on how the problem was replicated)
1. Setup the router (WRT54G V6) using the latest firmware 1.02.0.
2. Accessed the router’s web UI and configured Access Restrictions.The following options were set:
   Status :Enable
   Allow :Internet access during selected days and hours.
          AY (WEDNESDAY) FROM (7:50AM - 7:55AM PACIFIC TIME ZONE)
   TEST RESULT : The internet is blocked.
   Under Website Blocking by URL Address block the following sites
          a. www.myspace.com
           b. www.facebook.com
   include the Website Blocking by Keyword (myspace and facebook)
   Save the settings
   TEST RESULT : Failed .. Blocked Websites are still Accessible
3 Assigned static IP on the computer using 192.168.1.5. Clicked on “EDIT List of PCs” button and entered the IP address assigned to the PC.
   TEST RESULT : the URL can be blocked.-->>Successfull
4 Used the MAc Address on the EDIT List of PCs
   TEST RESULT : The URL can be blocked.-->>Successfull
5 Set the IP back to DHCP and used 192.168.1.100 on the EDIT List of PCs.
    TEST RESULT : The URL can be blocked.-->>Successfull
Summary: The WRT54G v6’s feature on Website Blocking by URL Address worked using firmware version 1.02.0.
I am not a teener anymore, I am a woman now - DreamGirls

Those sites have a random connection and DNS entries. Your best bet would be to use a DNS servcie like DDNS.com or OpenDNS.com service. Point your router to one of those DNS services and there DNS addresses, then set up one of those services to block FB and Twitter. If you use there DNS addresses on your router instead of the ISP DNS, and you block FB and Twitter, users should beable to get to FB or Twitter after that.

WEBSITE BLOCKING ON WRT54G V6 (Firmware Version: v1.02.8)

Hello Friends,
Short: why some webpages block and others don't using this feature in my router? As mentioned above, I run a small office and am using an ::: WRT54G V6 (Firmware Version: v1.02.8) ::: router.
For instance, I have been successful in blocking sites such as "sex.com" and others. Also, in blocking sites by keywords such as: news, music, vid, nude, etc. BUT, when I try blocking FACEBOOK or TWITTER either by URL or keyword, guess what: IT DOES NOT WORK...!
Any ideas why this happens and how can I be successful in configuring this feature??? I will appreciate this! Blessings...
Solved!
Go to Solution.

Those sites have a random connection and DNS entries. Your best bet would be to use a DNS servcie like DDNS.com or OpenDNS.com service. Point your router to one of those DNS services and there DNS addresses, then set up one of those services to block FB and Twitter. If you use there DNS addresses on your router instead of the ISP DNS, and you block FB and Twitter, users should beable to get to FB or Twitter after that.

Wrt110 ddns reporting incorrect ip address

Replaced my dead wrt54g with a wrt110 last night. Went through normal setup, re-enabled settings to mirror the old setup, including dynamic dns. wrt110 reported a successful ddns update and diplayed the correct ip address through the linksys admin gui. However, I logged into my dynamic dns account and found that the ip address reported was 192.168.1.100 instead of my 173.xx.xx.xx address. Is there a known bug? I searched the forum and didn't find any related issues. I'm running on the latest firmware, fwiw. Any idea how to correct?

When you login to the Router GUI and login to the DDNS tab, under DDNS tab whats the Internet IP address ? Are you getting the same IP address 192.168.1.100 or 173.x.x.x ?

Strange behavior of wrt54g

hi there
I installed the ddns service from dyndns. But wrt54g cannot update the entry. The errormessage is switching: "Name resolver fail, DDNS update fail!" or " Update in progress".
Sometimes there is also no entry unter status in the dns and the Subnetmask. Althought dns servers are forwarded to the computers connected to the wrt54g and the connection is working. So the problem is only that wrt54g is unable to resolve the dyndns name.
any ideas?
running firmware v1.00.9
cheers

Try this:
http://linksys.custhelp.com/cgi-bin/linksys.cfg/php/enduser/std_adp.php?p_faqid=1040
Pay particular attention to the part about cloning the MAC address of your PC's ethernet adapter........
This is something that has worked for many of us that have experienced the same issues, including myself. Let us know how things work out.
jhw

DDNS on WRT54G

Similar Messages

Maybe you are looking for