WRV54G firmware 2.30

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by JonAlthoff, Aug 14, 2004.

  1. JonAlthoff

    JonAlthoff Network Guru Member

    Copy of the email message on Yahoo groups for the WRV54G router.

    Nice message Mike. Does that mean that Linksys or Gemtek?? has done something in newer firmware versions to not allow users to be able to gunzip firmware?

    I was able to gunzip 2.03, 2.10, 2.21 and 2.25.2. What I found was very dissapointing. Check this webpage/url on your router. or of course substitute your own subnet/ip for your WRV54G router.

    What I found was that (as previously stated) the firmware is BETA.

    Firmware 2.03 is actually Gemtek firmware version 2.5.22Beta dated 08/24/03 11:05
    2.10 is 2.6.28 Beta-3 12/10/03 13:30
    2.21 is 3.2.20 Beta-2 02/06/04 11:41
    2.25.2 is 3.2.26 Beta-3 03-10-04 19:35 as shown below:

    WRV54G Phase II + HotSpot(US)

    Version:3.2.26Beta-3 Date 03/10/04 19:35

    Gemtek Technology Co., Ltd. http://www.gemtek.com.tw

    So now I'm even more disappointed that the firmware is and has always been BETA. I could not find the information in the 2.30 version and could not find an rd.img to be able to extract and test the firmware. I haven't loaded it. Has anyone else?

    At 08:42 PM 8/13/2004, you wrote:
    It is in here:

    Does anyone know how to determine the bs and skip values for different
    files? Here is the instructions for the 2.03 firmware. It doesn't work for
    any other version.

    dd if=wrv54g_2.03_fw.rmt of=rd.img.gz bs=1c skip=788041c


    At 12:40 PM 8/13/2004, you wrote:

    Has someone heard of a firmware version 2.30?
    I have found that http://www.dslreports.com/forum/remark,11038708~mode=flat
    on a forum.
  2. eric_stewart

    eric_stewart Super Moderator Staff Member Member

    I posted this at dslreports.com as well. I will quote below, please excuse the verbosity:

    I installed the new firmware. First thing that I note is that, unlike 2.25.2, this firmware will not allow unauthenticated access to the router when syslog is turned on.

    Incidentally, I was playing around with the hardware DMZ feature of the router. I discovered that Linksys's definition of a hardware DMZ is an interface (LAN port 1)from which the connected hosts cannot initiate connections (ex: ping) devices on the other LAN ports (2,3 and 4) or the wireless domain. It is placed on a different subnet than the rest of the interfaces, ( vs. in my case). By default a host on the DMZ can access the Internet and can be accessed from the Internet but cannot access devices in a higher security zone. This is great and a very neat feature. Thus, if someone compromised a host in the DMZ, they could not, in turn, use it to launch an attack on your inside, trusted network. Cool stuff and maybe just the feature for someone who wants to create a perimeter network on a different network segment.

    I teach Cisco courses and in monkeying around with it I also noted that the router supports IEEE 802.1d/w spanning tree on its switched ports and will become the root of the spanning tree, if the other switches have a bridge priority of higher than 32768 (its default). I was able to observe this in a lab.

    Another thing that I noted (I used the router's configuration file for clues) is that it appears to support separate VLANs on its switch interfaces, each interface in a separate subnet. For example, by default switch port 1 is in VLAN 1 with subnet, switch port 2 is in VLAN 2 with subnet and so on. Very cool which makes me wonder if Linksys is planning major changes to the interface to activate these hidden features in the OpenRG kernel.

    Anyway, all this was noted before I did the firmware upgrade which:

    a) did *not* break my router (no warranty on yours!)
    b) seems to be an incremental change in any case.

  3. JonAlthoff

    JonAlthoff Network Guru Member

    I loaded firmware 2.30. In the process of setting up my configuration I noticed that Wireless WPA Pre-Shared Key no longer has AES Algorithms. Only TKIP is available.

    I would presume no fixes have been done to VPN. I created my first tunnel and saved the configuration. Tried to ping a computer on the remote end of the VPN and just get timeouts. I went to the BEFVP41 configuration on the remote end of hte tunnel hit connect and it connected. I have to do this to establish tunnels. I may try to setup a remote port on the remote end and VNC to it and try tp ping a computer on my local lan. Then I can see if the tunnel will establish in reverse.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice