Wireless Ethernet Bridge (tomato)

[broncoBrad]

I have a linksys WRT54G v1.1 running tomato 1.28.

I'm trying to use this to connect (as a wireless Ethernet bridge) to one of my OPT interfaces that is set up as an access point.
Based on the status from the tomato configuration it shows that it's connected and I can ping both from the pfSense web configurator and from the tomato configurator.

The problem I'm having though is that the wired clients on the tomato Ethernet bridge aren't obtaining a DHCP address. Based on the pfSense DHCP system logs pfSense is not seeing any DHCP requests. If I set up a wired client to have a static address it works fine (i.e. it can connect to the internet.

FYI… on the OPT interface I have a PASS any to any rule as the only rule.

Can someone please help me get this set up correctly so my wired clients can get a DHCP address?

Thanks!

[wallabybob]

Have you checked the firewall log for DHCP requests?

Firewall rules take more parameters than 3 (PASS any to any) - its possible you may have one of the parameters you didn't list set wrongly.

Did you reset firewall states after adding the PASS rule? (See Diagnostics -> States, click on Reset States tab for explanation.)

[broncoBrad]

Yes I checked the firewall log (Status –> System Logs --> Firewall Tab) as well as the DHCP tab. The DHCP tab never sees any requests.

First of all the rule I was referring to is attached.

At one point I saw in the firewall logs entries from my wireless bridge, but it specified a 169.254 address as where it was connecting to, but it also appeared to be on different port so I thought maybe it was using different ports for each ethernet port on the bridge.

Also attached is the wireshark capture of my onboard ethernet of my pc (connected through the wireless bridge) trying to obtain a DHCP address.

FYI... the address of the ethernet bridge is 10.212.24.190. the MAC of the wireless interface of the ethernet bridge is 00:0C:41:76:3C:D2.


[wallabybob]

The wireshark capture suggests the DHCP requests should have got at least as far as the Tomato. That you apparently don't see it on pfSense suggests you should look at the Tomato - perhaps it is not forwarding DHCP requests. Perhaps the Tomato has some sort of packet capture you could use to verify it is receiving the DHCP request and forwarding it,

Your firewall rule looks fine.