using RB133 as client (station) to connect to RB133 AP-Bridg

RouterOS Wireless Networking
1

Hi Guys,

I’ve got a RB532A (IP 10.5.50.1) setup as hotspot (with DHCP server) and a RB133 (IP 10.5.50.2) setup as AP-Bridge (ssid APtest). RB532A is connected to the Internet and Radius has been set to remove server.

All boards has software version 4 and has been upgraded with ROS 3.9 MIPSL !

I would like to use another RB133 to connect to the AP (and all other AP’s that I find when I’m travelling). I have gone through following setup on the RB133:

  1. reset configuration
  2. WLAN1 wireless set to “station” frequencies “2.4Ghz B/G”
  3. Bridge1 setup with ports Ether1 - bridge and WLAN1 - bridge
  4. IP address 10.5.50.3/24 - 10.5.50.0 - 10.5.50.255 - bridge
  5. IP route 0.0.0.0/0 - 10.5.50.1 - 1
  6. Default IP Route 10.5.50.0/24 - bridge1 - 0 - 10.5.50.3

I then scan and find my AP (ssid APtest) and connects (works perfect)

I immediately get an IP address from the GW I.E. 10.5.50.224 etc.

I can ping AP (IP 10.5.50.2) and GW (IP 10.5.50.1)

Sometimes I can get a connection (very rearly) most of the time I cannot access the internet via the connection.
When I finally get a connection through this can last for hours or it can disconnect again within a few minutes.
I have noticed that the RB133 (Station) stays connected all the time and without any problems/hickups, so I’m absolutely pussled as to what create this connection/staying connected problem.

F.Y.I. there is no rules for when it connects, it can be after a reboot of the RB133 or a reboot of the pc or it can just suddenly be connectable without any explanations !

Hope one of you guys can help me on this issue.

Best regards
Jens

2

Guessing hear. Sounds to me like DNS problem. I would suggest take out default rout and let DHCP client add default route and DNS. Think that should maybe fix problem.

3

Hi Bill,

Look like you’ve tried this before mate !

Being absolutely new to Mikrotik (and no training courses yet) I’m a bit “up the creek” with this installation.
I have now done the following:

  • changed the station IP address from bridge to Ether1
  • deleted bridge1 and ports
  • setup DHCP client for Wlan1 (works fine, station gets an IP address immediately)
  • setup Firewall / NAT : Chain = srcnat - Out.Interface = Wlan1 - Action = masquerade
  • rebooted client

But my connected PC doesn’t get an IP address (from AP), could this be a problem in the above srcnat firewall setup ?

I have even tried to add IP / DHCP Relay - name = relay1 - interface = ether1 - DHCP Server = 10.5.50.1
But still no IP for the connected PC !

Looks like the “bridge” doesn’t exist between Wlan1 and Ether1.

Any ideas ?

Best regards,
Jens Kaersgaard

Onboard Partners (International) Ltd.
29 City Mill Lane
Suite 3
Gibraltar

Skype: onboardpartners

4

Your CPE (RB133 client) is a router, DHCP requests do not go outside broadcast domains (without DHCP relay). So you need your client RB133 to run a DHCP server for your locally connected PC, or set your RB133 as ‘station-pseudobridge’ (3.x only) if you want to mac-nat the client directly onto the AP. You cannot use bridge from wlan/ether without station-psuedobridge.