I'm attempting to make a wireless-to-ethernet bridge and can't get the first set of instructions to work. I want to relay DHCP traffic, etc. because the router "closer" to the Internet link (this is a point-to-point link between houses) already handles DHCP and traffic management. The whole network is more complex than this, but I've only included the parts that I care about. The OpenWRT wifi to ethernet bridge in the middle is what I can't get working. And it is not connecting to the other distant AP with the same SSID - I can't even get it working next to the shared router.
Unfortunately the shared router is a DIR-655 and I cannot install custom firmware on it. I otherwise have total control over it. I am sharing my internet connection with my neighbors and splitting the bill. The DIR-655 shared router has directional Yagi antennas pointed at the distant house and can get a connection fine.
The problem is, using method 1 above, I cannot get OpenWRT to act as a wifi-to-Ethernet bridge on a DIR-615 rev C1. That's all I want. I don't want it to repeat Wifi, I only want it talking to the shared router for all traffic between houses, and bridging that to Ethernet. Some clients connect directly by Ethernet and others connect using an existing access point in the distant house.
I've been through and through the wiki docs and this thread. WDS doesn't work, presumably because it's a manufacturer specific implementation. So I tried this guide, because relayd (relaying DHCP) is what I want, and I DO NOT want anything else provided by the bridge except ... a bridge. No DNS, no nothing, just a bridge.
I tried method 1 above and even so, when I connected to the bridge by Ethernet, it was still giving me DHCP IPs in 192.168.1.1 (note the DIR-655 is 192.168.35.1 and if relayd were relaying DHCP, I should be getting IPs in 192.168.35.0/24). I set the 10.0.0.240 address as described, and also the other address "not in the same subnet as the primary router" to be 192.168.36.1. But, I still get DHCP in 192.168.1.0/24, and I can't connect to or ping the bridge any more - not on 192.168.1.1, not 192.168.35.2, not 192.168.36.1, and not 10.0.0.240, whether remaining with my laptop connected to it by Ethernet as 192.168.1.x, or setting my IP manually to all the different subnets. So, I had to re-flash the bridge.
Can anyone help before I try again? I know this is possible because it's working right now with stock firmware on a Buffalo WLAE-AG300N! The only problem is that the Buffalo needs to be rebooted about twice a day, so I'm trying to use OpenWRT on a DIR-615 as a reliable replacement.
(Last edited by normblop on 9 Apr 2014, 09:57)