Join WRT54G v2.2 with reg linksys firmware to a sonicwall

Discussion in 'Networking Issues' started by raylward102, Dec 2, 2005.

  1. raylward102

    raylward102 Network Guru Member

    I have a sonicwall soho3 connected to the internet. I conneted the sonicwall to a switch. I connected the WRT54g to the same switch. I want the sonicwall to handle all of the DHCP stuff. I have disabled DHCP on the wrt54g. All I want the the wrt54g to do is allow wireless clients to connect through it to the sonicwall dhcp. I did have this working for awhile, but now it's only one direction for the traffic. The wireless client can access the internet, sonicwall gui, linksys gui, and recieve a dhcp address. The problem that I have is that my desktop computer, connected to the switch cant ping or connect to the wireless client in anyway. As strange as that sounds, the tools provided by both the wrt54g and the sonicwall cannot ping the ip of the wireless client even though the sonicwall apparently issues the ip to the client. I am confused....Seen anything like this. I think its the wrt54g.
  2. raistphrk

    raistphrk Network Guru Member

    Re: Join WRT54G v2.2 with reg linksys firmware to a sonicwal

    I've been dealing with the EXACT same situation, ironically, except that the Linksys router was a WRT54GS. I talked to an engineer who managed the SonicWall for my client, and he mentioned to me that on some versions of the device, there's a connection license limit of 5 IPs, and the licenses aren't released automatically.

    Another possibility may just be some goofy routing. The routing table for the Linksys device gets really goofy if you don't use the WAN port. Are you using the official firmware, or a modified one? Also, could you provide your IP addressing scheme and subnet masks?
  3. raylward102

    raylward102 Network Guru Member

    I am using the official firmware. (linksys firware) I have always had problems doing this with my router. I am positive that it is a routing issue. Just like you said, "the linksys device gets really goofy when you dont use the wan port". I had a BEFW11S4 once that worked perfect in the same situation. I just want the wrt54g to act like a switch for wireless clients to access my network behind the sonicwall. I manage three sonicwall devices. 2 at work and 1 at home. I have pretty good experience in using them. The connection license limit you spoke of is probably to do with the amount of nodes allowed for that particular firewall. If you have a 25 node sonicwall, it only means that 25 computers can access the internet behind the device. If you have more then 25 computers, the computers that come after the first 25 will only communicate on the lan behind the sonicwall but not to the internet. My setup is like this:

    Sonicwall lan ip =
    Sonicwall DHCP is enabled
    Linksys lan ip =
    Linksys DHCP is disabled
    Changed linksys setting from gateway to router
    Wireless client = Dell laptop IP =
    Desktop Client =
    The only other setting that I have changed on the linksys was the advanced routing setting.
    I have filled in like this:

    Operating mode = ROUTER
    RIP = Lan&Wireless
    Destination Lan IP = (Pointing it to Sonicwall) I think?
    Default gateway = (sonicwall is the gateway)
    Interface = Lan&Wireless

    That's all. Any ideas!
  4. raistphrk

    raistphrk Network Guru Member

    I'll take a look at all that when I go into the office today. Until then, I'm off to bed. I'll post again when I have some ideas.
  5. 4Access

    4Access Network Guru Member

    There's no reason to have RIP enabled since the WRT is not routing anything. I'd recommend disabling it. I'm not sure that is the cause of your trouble but it's a place to start.

    Another thing you could try is loading a custom firmware such as DD-WRT that allows you to disable the WAN interface completely. This should eliminate any potential "goofy routing" issues related to the WAN port not being used. (Although this is the first time I've heard someone mentioning trouble with this.)

    BTW if you do decide to go the custom firmware route, make sure you disable Loopback on the Administration page since it will prevent wireless clients from accessing certain resources on the the wired LAN. (Stuff like MS file & print sharing etc.)
  6. danielhaden

    danielhaden Network Guru Member

    Hyperwrt can also disable the WAN port.
    I has fast throughput and is extraordinarily easy to use. Use Tofu9 for the "G" and anything Thibor for the "GS".

    In addition, you will want to disable DHCP after you change the router's access IP address so that it doesn't conflict with anything else on your network.

    Shut off every Firewall option. Disable UPNP.

    Well, I've always used this firmware for the task and have never seen a problem with it.
  7. 4Access

    4Access Network Guru Member

    I haven't been keeping close tabs on HyperWRT lately as I prefer DD-WRT but is there any reason you recommend Tofu9 instead of Tofu10?

    Edit: I guess I found the answer based on your post here.
  8. raylward102

    raylward102 Network Guru Member

    I was looking at a chart that explained all of the functionality differences between the various types of firmwares. It can be found at this link:

    Everyone speaks of "ease of use" and what not. On the chart that I looked at, the DDWRT v23b seems to be the clear winner. The chart also explains that the functions mentioned are found in the GUI. Yes, the chart is a couple of months old, and it doesnt mention anything of the tofu firmwares. In any case, I would like to try a firmware once. I dont want to start flashing multiple firmwares on to my device. If tofu is the way to go, then let me know, but I want an opinion from someone who really knows. ( not to say the above posters don't know)
  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