I am trying to use the RB133 as a mobile client, but since it is set in station mode, (because the AP does not support WDS) I cannot bridge the interfaces. Has anyone had experience using an MT unit as a mobile client?
you have to use WDS … replace AP
normis, so with a LVL3 lic, you can NOT use the 133c as a wds, wifi repeater as AP bridge is not allowed, Right?
tks
It is not practical to replace the AP; it is proprietary and provides outstanding functionality. I was hoping you were going to suggest a routing solution???
Well, you tell us that you’re AP can’t use WDS and you hope that Normis would suggest a routing solution.. !?.. I am a little bit confused here..
To get back to the topic.. Yes you can use RB133c as a mobile client as you can with every routerboard and if you insist on making an transparent solution you can do that as well with ROS V3. What kind of functionality are you requesting when you say “mobile client”?
Regards
Henrik
Basically I am trying to utilize each of the Ethernet ports on the 133 board for a different device. Each device needs to be able to be addressed or logged in to separately. So of course one option is to assign each of the interfaces with a different subnet, or essentially its own network, but if there were more than a hundred mobile clients, than that would be a very large of networks to manage.
It appears that I can use proxy arp and simply carve up a class “C” block with static addresses used for the R133 units, and then just put a corresponding ip address on each of the different Ethernet ports with a different mask. I am not sure if this will work, and as of yet have not found the commands to setup proxy arp in the 133. I have found examples of what it should look like when I am done, but have not found the commands yet. If you think that might work, can you point me to the command list?
If you take Winbox and look at each particuar interface you can choose how you want ARP on that particular interface to behave. In the terminal you write: /interface ethernet set <interface_name> arp= <disabled | enabled | proxy-arp | reply-only>
Regards
Henrik
Ok thanks, I was missing the equal sign. It would apear that this configuration would be for a normal access point, but I am trying to use this as a mobile device, so shouldnt I configure the wireless port with Proxy ARP as that is the path to the network/internet?
When you say mobile device, do you then mean being able to roam between multiple accesspoints with a static ip configuration?
If yes, then i am sorry to say that this cannot be done if the AP isn’t able to provide WDS or be part of some VLAN configuration. Maybe it can be done by OSPF, but i’m not sure your AP can do this? You see, its no problem setting up a client (RB133) with different subnets on each interface and route or masquerade through the wireless interface on 1 AP, but if you start to move around, your AP’s and infrastructure needs to be able to handle either one broadcast domain on all AP´s (All AP’s bridged in one VLAN) or some dynamic routing (OSPF). You cannot go with the bridge part as your AP doesn’t support WDS.
However if you are on one single AP it’s quite easy, just set up the client with the subnets you need on each port, give the WLAN interface (in station mode) a static IP and set up routing on the Routerboard with the AP as default gw. In your infrastructure you of course need to set up routing the other way and then it will work.
Regards
/Henrik
Thanks Henrik. The wireless network is set up with APs that will support the roaming feature. It works fine with a laptop. The issue is that I need to provide multiple ethernet ports. The RB133 supports this fine and I am very pleased with MT gear in general as I am using it in many places and applications. Again the challange here is to deliver multiple ip addresses through physicial ethernet ports in a mobile application. If I set a static ip on the wlan interface (or it is capable of pulling down a dhcp adress, I have tested this) of 192.168.100.123/24, and set up one ethernet interface on the RB133 with 192.168.100.17/28, and set the default gateway as 192.168.100.1/24 (which is the ip of the access point) then it should work? I also need to set up a return route in the wired network system (which the AP is connected to). Can you tell me what you think the static rout in the RB133 shoulc look like? Should it just be a 0.0.0.0/0 with a gateway of 192.168.100.1?
First of all you can put a DHCP client on the Wireless interface. Just make sure that the “add default route” box is ticked. However your routing won’t work if you use a /24 net as WAN of the client and make smaller subnets in the same range on your LAN ports. You have to either make different subnets on each port (perhaps 192.168.101.x/28 or whatever) or make the WAN (192.168.100.x/24) net smaller so that subnets doesnt overlap. Otherwise if your Ap can handle it you could bridge all (WLAN + Eth 1-3) together and then put the IP adresses you want on the ethernet ports and enable Proxy arp on the bridge.. Haven’t tested that but i guess it should work, otherwise you can try out the Beta3 software and use the “Station Pseudobrigde feature”.
/Henrik
Ok Great, now we are getting to the meat of the matter. I realy want the same IPs from the 192.168.100.x network on the ethernet ports and the devices. I havent found anyone that has used Proxy ARP and I havent had any success with it. Have you used the Beta3 versoion with the “Station Pseudobrigde feature”.