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

Wireless Ethernet Bridge with pfSense

Discussion in 'Tomato Firmware' started by broncoBrad, Sep 4, 2011.

  1. broncoBrad

    broncoBrad Networkin' Nut Member

    Alright, so I have a WRT54G v1.1 that I just flashed with Tomato 1.28 because I wanted to make use of the wireless ethernet bridge.

    Here's what I'm trying to accomplish:

    pfSense Router -- (wired) --> Buffalo AP -- (wireless) --> WRT54G -- (wired) --> Desktop (DHCP)

    I have read several forum posts and tutorials and what not to try to get it set up and I know that it is connected to my pfSense router since I can ping the WRT54G from the router and I can also see in the configurator of the WRT54G that it is connected. Here's my problem:

    As you can see above, I want the wired client(s) on the WRT54G to obtain their addresses via DHCP, but I have not been successful at accomplishing this.

    I have my WRT54G set up with a static IP, subnet mask, and the gateway and DNS points at my pfSense router. My pfSense router has DHCP logs and when I attempt a release / renew on my desktop PC, the router does not see any DHCP requests, so this tells me that the WRT54G isn't forwarding on the requests. Is there something special I need to do? Did I miss something?

    Thanks!
     
  2. EOC_Jason

    EOC_Jason Networkin' Nut Member

    Probably the firewall blocking your client DHCP broadcasts (on the WRT54G)...

    I don't know off the top of my head if there is a checkbox to simply disable the firewall in tomato... I know there is in firmwares like dd-wrt...

    If you can't find a way to disable the firewall in the GUI (since it makes no sense to have it enabled anyhow), you might have to type a few custom commands on the scripts page to make the firewall accept all traffic (very easy to do).
     
  3. broncoBrad

    broncoBrad Networkin' Nut Member

    From what I've read the Tomato firewall doesn't block anything by default.

    Port forwarding also doesn't make sense since I'm not forwarding from the external to internal, but the other way around.

    Anyone??
     
  4. broncoBrad

    broncoBrad Networkin' Nut Member

    My question for this post is is there a way to force the routing to make sure that those requests and in turn responses make it between the wireless bridge and the pfSense router?

    Thanks in advance for any help!

    I moved to using Tomato firmware because I assumed this process of obtaining DHCP addresses for the wired devices would be easier, but it appears to be working the same way as my Linksys wireless bridge (WET200) where it only works if the wired devices have static addresses.

    Someone please help!! I really want to find a solution because I have a wired device (slingbox) that is very difficult to set to a static IP so it would be very nice to be able to have it obtain its IP via DHCP and have the pfSense box assign it a static DHCP lease so that I would always know what address the slingbox had.
     

Share This Page