Here's a simple bridge I simply cannot get to work.

A--------B---------C

A is a small network
B is a Mikrotik router on a hilltop
C is the internet gateway A cannot see directly.

B has a wireless AP for the clients A and a station connecting to an AP on C.

The routing table is pretty simple but wouldn't using B to bridge A and C be even simpler?

Yet if I bridge the two wireless interfaces on B (A<>B, B<>C) give it an IP address = C/24 and my own CPE in A an address from the C/24 network (and take the original addresses off B's interfaces) I can ping B from A and C from B but I cannot ping C from A, which just times out.

My default gateway at A = C. Should it = B/bridge? Is it a problem with MAC addresses on the bridge and ARP? Or do I need to get technical with firewall rules or proxy ARP for this to work, in which case I probably won't bother.

Thanks for your time.

Or do I need to change the mode of B's wireless to C from "station" to "bridge" to enable it to form a bridge with B's (ap-bridge) wireless to A? Sounds counter-intuitive to me, but then much of MT's config labelling is. (ie 'access' list and 'connect' list. I have to look up to remind myself which is which every time.)

Heres a setup that might help you that I have done in the past.

Lets assume A is CPE
Lets assume B is the Wireless AP
Lets assume C is our gateway.
Lets also assume we are using all Mikrotik devices loaded with RouterOS.

Setup1

A is to be set in Station mode (Now you can set this up with a DHCP if you want to seperate your infrastructure from the clients behind A)
B is to be set in AP Bridge mode
C is directly connected to B wired.

Setup1

A is to be set in Station mode (Now you can set this up with a DHCP if you want to seperate your infrastructure from the clients behind A)
B is to be set in AP Bridge mode
C is directly connected to B wired.

Thanks, but B is 14 Km from C, and on top of a mountain.

I'm trying to turn the two wireless interfaces on B (currently an AP for network A and a station linked to AP/gateway C) into a bridge which makes A subnet of C, so if C has the address 192.168.0.1/24 all the clients in A could have an address in the 192.168.0.0/24 network and use 192.168.0.1 as the default gateway. I'm led to believe by the literature that the bridge on B doesn't need an IP address at all, but that I can give it one from the 192.168.0.0/24 set for admin (Winbox) access.

This would also enable me to set up PPPoE links from A to C as the bridge simply passes PPPoE requests through to the server on C.

As said, I can create the bridge and with addresses on A, B and C all from the 192.168.0.0/24 network A can ping B and B can ping C but A can't ping C, so traffic isn't passing through (or is that over?) the bridge.

Its in the bridge. Did you bridge both ports on B together? Give the IP on B to the Bridge interface.

Its in the bridge. Did you bridge both ports on B together? Give the IP on B to the Bridge interface.

I created the bridge, added the wireless interfaces on both sides of B to it and gave the bridge an IP address from C's subnet. Also a node on A an address from the same subnet, from which I could ping B but not C, although B could ping C. I even took the 'old' addresses off the ports making up the bridge.