How can i turn my Rb333 to an Access Point only?
I have another custom router i need to do all the routing and everything else.
I just want to have the rb333 as an access point.
No DHCP server
No HOTSPOT server
No Firewall
No NAT
JUST access point and pass the the traffic through Ether1 to the router and back to the clients
Add ether1 and wlan1 to a bridge, run wlan1 in ap-bridge mode.
Thats what i have already but i also have a Hotspot server which of course has a dhcp server and firewall+fitler rules.
How are you running Hotspot on something you just want to use as an AP?
Then reset the RB333 back to factory defaults.. and reconfigure as a standard bridge… seems pretty straight forward and simple..
/interface bridge add
/interface bridge port add interface=ether1 bridge=bridge1
/interface bridge port add interface=wlan1 bridge=bridge1
/interface wireless set wlan1 mode=ap-bridge
Set a management IP address to the bridge interface, configure your frequencies/bands/ssids etc, and your done…
ok i sorta did that
i made the wlan1 ap-bridge (already is)
disabled hotspot
disabled dhcpserver
in bridge 1 i have ports: ether2, ether3, wlan1, wlan2
for ether1 i have it set as DHCP CLIENT (gets ip from linux router)
Ether1 then gets a DHCP IP.
but when i ping 4.2.2.2 OR the router IP (192.168.5.1) it either timesout OR gets a response then timesout and so on
I’ll try what you suggested but again shouldnt i set ether1 to a dhcp client ip?
Does it have the correct default route?
What does your routing table look like? Is there a route with a dst-address=0.0.0.0/0 and gateway=[gw_address] ?
Usually you’d assign the management IP address to the bridge, so the bridge interface would be the one acting as the dhcp-client…
Bridges function @ layer2, so the fact that you can’t ping out from the bridging device doesn’t really mean much and it is not necessary to use a DHCP-Client on the bridge unless thats how you’re assigning its management IP.
It just sound like the bridge doesn’t have a route set, and that’s why it’s unable to ping out to 4.2.2.2. It also could be because the ip address is on an interface thats apart of the bridge… try changing the dhcp-client interface to bridge1.
Thanks ..
got it working
had to do manual stuff for the bridge ip and added a static route.
[admin@MikroTik] /ip address> print
Flags: X - disabled, I - invalid, D - dynamic
# ADDRESS NETWORK BROADCAST INTERFACE
0 192.168.5.3/24 192.168.5.0 192.168.5.255 bridge1
[admin@MikroTik] /interface wireless> /ip route print
Flags: X - disabled, A - active, D - dynamic, C - connect, S - static, r - rip, b - bgp, o - ospf, m - mme,
B - blackhole, U - unreachable, P - prohibit
# DST-ADDRESS PREF-SRC GATEWAY-STATE GATEWAY DISTANCE INTERFACE
0 A S 0.0.0.0/0 reachable 192.168.5.1 1 bridge1
1 ADC 192.168.5.0/24 192.168.5.3 0 bridge1
[admin@MikroTik] /interface bridge port> print
Flags: X - disabled, I - inactive, D - dynamic
# INTERFACE BRIDGE PRIORITY PATH-COST HORIZON
0 ether1 bridge1 0x80 10 none
1 wlan1 bridge1 0x80 10 none
2 ether2 bridge1 0x80 10 none
[admin@MikroTik] /interface bridge port>
[admin@MikroTik] > /interface wireless print
Flags: X - disabled, R - running
0 R name="wlan1" mtu=1500 mac-address=00:0C:42:1B:B6:76 arp=enabled interface-type=Atheros AR5413
mode=ap-bridge ssid="Shahrazad-7702629979" frequency=2462 band=2.4ghz-b/g scan-list=default
antenna-mode=ant-a wds-mode=disabled wds-default-bridge=none wds-ignore-ssid=no
default-authentication=yes default-forwarding=no default-ap-tx-limit=0 default-client-tx-limit=0
hide-ssid=no security-profile=default compression=no
You don’t need the static route…
Ya i wouldnt need one if i had bridge1 as a dhcp-client but since its a static ip now i guess i have to…
You don’t need it regardless.
i guess you’re right
if i disable the route i cant ping anything from the /tools ping option
it would say “no route to host”
but on client pc i can browse and do anything else.
hmm…
You should be able to ping things on the same subnet. If you want to ping other IP’s you would need the static route…