133 setup as a client

The application is traveling using the 133 in a weather proof enclocure and good antenna on the roof of a motor home and a wired network inside the motor home. So, I want to use a 133 with a single radio to connect the wired network to a wireless AP. The problem is I have no control over the wireless network (both hardware or configuration). It works ok with some AP’s using ap/bridge mode and WDS altho the setup overhead is a pain. It fails with any AP that does not support WDS like Senao and many Belkins. It seems that one should be able to set the MT up in client mode, connect to the ap and route or bridge the Ethernet. What am I missing here? Could one put another radio in and set it up as an AP so I can go wireless to my laptop?

Thanks!

Setup the wireless of the RB133 as “station” and blank SSID, it should then attempt to connect to the AP with the strongest signal. If there are multiple APs use the Scan feature to determine the SSID and enter that in the SSID field.

The MT as a client registers fine but no traffic is routed between the ether1 and wlan1. I have them both in bridge1 and would like dhcp from wired machines connected to ether1 to get an IP from the wlan1 network. It seems some other routing/Nat/Bridging configuration needs to be set up to connect the wlan1 client to ether1 or unlimatly from “wlan1 client” to “wlan2 AP:smiley:

update to v3.

bridge doesn’t work in station mode on a 133c.

Oldman says
bridge doesn’t work in station mode on a 133c.

fball says he’s using 133, not 133c.

fball does your router have one Ethernet port or three? RB133c has one Ethernet port in which case what Oldman says is true, RB133 has three Ethernet ports in which case you should be able to Bridge wlan1 and ether1.

Make sure the IP address(es) you’re using for the Router is/are set against the Bridge, there should be no addresses allocated to wlan1 or ether1.

To receive IP addresses via DHCP from the ISP’s Access Point to PCs on the Ethernet side of the MT router you need to switch off NAT. Personally I’ve had problems with this method of working, I think you’d be better off setting up NAT and DHCP on the MT router and supply addresses to wired PCs from there.

There may be incompatability issues with some APs if you try to setup without NAT, as in this mode the AP will have to accept traffic from multiple IP addresses per wireless session. Many ISPs limit the number of connections over a wireless session. Using NAT you are hiding the fact you have mutiple downstream systems from the ISP, so is more likely to work.

1)Go to /System/reset-conf to undo all the bridging, etc.
2)See if DHCP is enabled under /System/Packages
3)Set an IP on the network you’re connected to under /ip/addresses, assigned to wlan1
4)Go to /ip/routes and set a default gateway (dest=0.0.0.0/0) to the network you’re connecting to (same subnet as IP above)
5)Set an IP for LAN card, e.g. 192.168.0.1/24 under /IP/addresses
6)go to /ip/firewall, under NAT tab, add new rule src-nat, outgoing interface=wlan1 and under actions, masquerade
7)/ip/dns setup DNS with Allow remote requests ticked on
:sunglasses:Now under IP/DHCP server, click setup to configure your DHCP and in DNS, put in your local IP (192.168.0.1 as above)
9)Just setup the wlan1 as station with SSID, band, etc and you’re done.

All your ether1 connected PC will get IP automatically and NATted behind 1 IP
When you change networks, change the SSID, Wlan1 IP address and default gateway (maybe DNS) and you’re off and away!

Ekkas

hey man can you tell me were i make some mistake
cant make it this station mode working corectly
i am connect to the network but dont have internet from cable
help.png

Your 10.185.108.150 interface, what is it connected to? What is the IP of this device? Subnet mask?

You have the RB133 set as its own gateway. It has to have a gateway other than itself to get out of the local subnet.