I have been messing with one for three hours now, with not success. I think I may have done something fundamentally wrong, OR mine is broken.
I configure the thing with an I.P. address for the ethe1, a default gateway to the outside world, and setup the wlan1 card in station mode to speak back to the tower. The radio checks in, and the server gives me an address, but I cannot ping the outside world from the radio side of the connection…
Is there something fundamentally wrong that I am missing to configure, or do I have a broken 133C?
I can get the RB133C to check in with the A.P., and the RB133C does get an assigned in-network address, but I can’t get through to the outside world using it from the computer.
I can talk to the RB133C using the Winbox tool, and from the Winbox tool, it will ping anywhere on the internet without a problem.
My problem is that nothing from the outside world gets through the ethernet port to my notebook computer.
Can anyone help me here?
I have addressed the Wlan1 device, and then bridged the wlan1 to the ether1. When I connect my notebook to the ether1, I get an “in-network” address, but I can’t get to the outside world. There must be something silly wrong here. I did setup the routing config as seen through the telnet “setup” command, so I don’t know what it is that I missed.
well, when you want to set your client wireless ‘mode=station’. that’s mode can’t bridged ethernet and wireless interface on bridge. ‘mode=station-wds’ will help for your client divice will connect to your ap.
When I bridge ether1 and wlan1, then AND add a masquerade rule, then it work just fine. If I just bridge ether1 and wlan1, then the IP address is assigned from the A.P. through the CPE,but no traffic can go through.
I just went through a painful length of time with the same situation that you describe.
I submitted numerous times here at MT BB, nobody had heard of such a thing where you can attain a -65 or better connection to the AP but be able to access the internet!
This was perpelxing as I had numerous other clients already functioning with the same equipment.
When I logged into a clients device and also a device that wouldn’t pass data as described above and really began to look over the settings between the two different devices the only thing I could find that was really different was in ‘Packages’!
The device which wouldn’t pass Internet connectivitiy had packages which were required that were disabled, and to add to the mix, we had packages which were not required to be enabled that were enabled.
Once I matched the setting in Packages the problem device no longer had a problem, it connected to the Internet instantly.
Not sure that’s what your facing but just sharing my experience, wouldn’t wish that un-productive troubleshooting hell on anyone.
I can concur, troubleshooting something that is as unproductive as that is such a bear. It doesn’t follow logical thought and reason, and is located NO where in the manuals. PITA, really.
I’ll check the packages tonight on some client units.
Does anyone remember what the best way is to reset these RB133Cs when you accidentally disable the ether1 on the board? I tried the jumper deal with the power on - no dice.
Hai,
you can enabled that ethernet from wireless interface, when you have login from that wireless interface, if can’t too just one for that solution ‘serial null modem cable’ is must and hyperterminal windows program will help you to login in your router.
This is correct. DHCP client will get wlan1 address, gateway and dns info. Give ether1 a different network address and ether use a static ip on the client plugged into ether1 or setup DHCP server on ether1. The client will use the ether1 address for both gateway and dns. Make sure dns has “allow external requests” checked. Surf away. Only the 3.0 betas will allow bridging from wlan station to another interface without masquerade. Station-wds will work if the AP is also MT.
if i bridge two connections i get the ip of R52 interface; if i remove the bridge i get the dhcp assigned ip ; but in both cases no internet connection.
