1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

DD-WRT vs.HyperWrt

Discussion in 'HyperWRT Firmware' started by emax, Apr 30, 2005.

  1. emax

    emax Network Guru Member

    Can anybody tell something about the differences of DD-Wrt and Hyperwert?

    Just the most important ones will suffice...

  2. Toxic

    Toxic Administrator Staff Member

    Hyperwrt is based on the lastest firmware/src code available from linksys.

    its feature though good are limited to:

    # Adjustable Transmit Power & Antenna Select
    # 13 Wireless Channels
    # 'Boot Wait' flash protection
    # Increased Port Forwarding & Triggering Fields
    # Increased Qos Device & Application Fields
    # Increased Access Restrictions Policies & Blocked Services Fields
    # Command Shell
    # Telnet Daemon
    # Startup & Firewall Scripts
    # Uptime

    DDWRT is an Alchemy branch. if you have seen Alchemy then you'll see that this has far more features than Hyperwrt. DDWRT on the other hand has far more features than Alchemy.

    if you are a newbie to the WRT54G scene, and want some more feature then HyperWRT is by far the best otpion for you. if you are watning to play with linux scripts and use the WRT54G/gs on a bigger network then use Alchemy/DDWRT

    hope this helps.
  3. emax

    emax Network Guru Member

    Thanks you simon for your precise answer, yes it helps.

    I am trying dd-wrt this evening, and i'm stuck with it. Too much options, to much ways to mess things up.

    Perhapd hyperwrt is a better choice for me (i'm not a linux-newbee, in fact i'm a sip-developer under linux ...), but theses embedded devices are something different than a "normal" linux-platform.

    What i want to do sounds simple, but for me it seems to be a major task: set up three WRT54GS in three different houses. Each inhouse-net should have a own network-segment, and one additional segment shall be the wlan-part:

    House A, network 192.168.22.xxx
    House B, network 192.168.26.xxx
    House C, network 192.168.37.xxx

    The WLan-Part: 10.64.40.xxx

    Yes, i know i have to break the bridge, and i did so. But apparently thats not enough - some additional configuration has to be done, and i'm really confused after all that reading: WDS/infrastructure/AP/client/p2p/p2multi-p/ad-hoc/vlan0/vlan1/eth1/br0 and lots of other terms are buzzing in my head, and so i hope that i'll be happier with an easier to handle operating system for my three WRT54GS.

    Additionally it seems, that most of the postings go here, to the hyperwrt-forum, and thats why i hope to get more help here.

    Is it possible to make a configuration as i described with hyperwrt? Or does hyperwrt build a bridge on startup or even rely on a bridge?

    Any answer is very much appreciated.

  4. RTSAnime

    RTSAnime Network Guru Member

    this could probably be done with WDS and Hyperwrt (see the post at the top of this section). But leave the DHCP on all 3 WRT's on and set the WRT's for manual IP and give them the Gateway IP of the WRT with the internet connection.

Share This Page