acidrain
Executive Member
Unfortunately im stumped on that. sorry
-
Join the MyBroadband community
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
-
Question of the Day: If you were buying a TV today, which brand would you choose?
Mikrotik setup for Client side
- Thread starter ColinR
- Start date
Thanks to alot of help from Stolla over on ctwug We managed to get an internet connection working via the RB133c, odly enough though normal Network traffic did not get through.
Stolla's directions as follows:
1. Get Wireless Radio connected with whatever security profile is necessary.
2. Create a Bridge.
3. Add Ether1, and WLan1 using the ports tab to the bridge.
4. in IP->Addresses add an ip in the same range as the network to the bridge.
5. In IP->Firewall->Nat, create a new entry for Chain: Srcnat, and Action: masquerade.
This setup allowed the PCs on the remote side to access the internet over the WLAN, however as I say, they couldn't connect to a PC share over the WLAN, even though the ADSL Router is on the same wired (and IP range) network.
Stolla's directions as follows:
1. Get Wireless Radio connected with whatever security profile is necessary.
2. Create a Bridge.
3. Add Ether1, and WLan1 using the ports tab to the bridge.
4. in IP->Addresses add an ip in the same range as the network to the bridge.
5. In IP->Firewall->Nat, create a new entry for Chain: Srcnat, and Action: masquerade.
This setup allowed the PCs on the remote side to access the internet over the WLAN, however as I say, they couldn't connect to a PC share over the WLAN, even though the ADSL Router is on the same wired (and IP range) network.
Last edited:
savagedavid
Active Member
Sorry I only saw this thread now. Let me put you out of your misery. The RB133C cannot operate in the same way as a Senao bridge - it is just not built to do that. If you bridge the Lan and Wlan while in Station mode it will not operate as expected, because it will not transparantly translate the MAC addresses. There are 2 ways to get it to emulate a Senao:
1. Run it in Station WDS mode (requires a WDS enabled AP)
2. Update to version 3.0RC10 (potentially risky) - this has a Station-Pseudobridge mode which will properly emulate a tranparent wireless bridge
...or my preferred...
3. Upgrade your AP to a RB532 and build a properly routed network
Hope this helps...
1. Run it in Station WDS mode (requires a WDS enabled AP)
2. Update to version 3.0RC10 (potentially risky) - this has a Station-Pseudobridge mode which will properly emulate a tranparent wireless bridge
...or my preferred...
3. Upgrade your AP to a RB532 and build a properly routed network
Hope this helps...
Ah, thanks for jumping onboard to answer.
As stated I'm moving in 23 days, and once all the horrific costs involved in moving have settled down, I'll have the cash to buy the RB532 - also wanting two radios - one to connect to the WUG.
In the meantime we'd still like to make use of the RB133C.
Is the Station WDS on MT stock standard stuff? We tried the Station WDS, and out the MAC into the Senao AP, refused to connect. Any ideas?
As stated I'm moving in 23 days, and once all the horrific costs involved in moving have settled down, I'll have the cash to buy the RB532 - also wanting two radios - one to connect to the WUG.
In the meantime we'd still like to make use of the RB133C.
Is the Station WDS on MT stock standard stuff? We tried the Station WDS, and out the MAC into the Senao AP, refused to connect. Any ideas?
Solved.
The steps i followed to get Transparent Bridge Working.
Done. Had no issues with instability so far. Got immediate connectivity on all remote PC's.
The steps i followed to get Transparent Bridge Working.
- Upgrade Router to 3.0rc11
- Create any required security profiles
- Setup wireless card to connect to AP, using Station pseudobridge
- Create a bridge
- Add wlan1, and ether1 ports to bridge.
- Create an IP Address for the bridge (same as existing network) eg. 192.168.1.x/24
Done. Had no issues with instability so far. Got immediate connectivity on all remote PC's.