Hi
ap is running, clients can see it, clients connected it, but no internet. internet ip-s are local LAN (192.) , and local ip is different (10.) cause otherwise connected clients would see big LAN shares.
dhcp server works therefore also 10. and so on. NAt is turned on, what im doing wrong?
of course, concept of mikrotik…mindblowing
Post your configuration with /export hide-sensitive
Reset your router with no default settings and backups and execute/paste the following configuration through terminal
/system reset-configuration skip-backup=yes no-defaults=yes
Adjust the wpa2-preshared-key and SSID to your liking
/interface wireless
set [ find default-name=wlan1 ] band=2ghz-b/g/n channel-width=20/40mhz-XX disabled=no mode=ap-bridge rx-chains=0,1 ssid=Shrek2 tx-chains=0,1
/interface wireless security-profiles
set [ find default=yes ] authentication-types=wpa2-psk mode=dynamic-keys supplicant-identity=MikroTik wpa2-pre-shared-key=password
/ip pool
add name=dhcp_pool0 ranges=192.168.88.2-192.168.88.254
/ip dhcp-server
add address-pool=dhcp_pool0 disabled=no interface=wlan1 name=dhcp1
/ip address
add address=192.168.88.1/24 interface=wlan1 network=192.168.88.0
/ip dhcp-client
add disabled=no interface=ether1
/ip dhcp-server network
add address=192.168.88.0/24 gateway=192.168.88.1
/ip firewall nat
add action=masquerade chain=srcnat out-interface=ether1
This should be the bare minimum for your access-point to work, as long as, you get an ip-address via dhcp-client on ether1
still no luck. i dont want to use these ip-s 192.168.88.2. Im filling wisp AP in quick tab area. my logic says that internet section is parameters for LAN, when local area is parameters what AP distributes its their wifi clients. (like CPE configuration is vice versa)
it distributes ip, but no internet connectivity. when i asked support from mikrotik, they recommend, that i should ask distributors where i bought the item. most dumbest suggestion ever.
You will still need to NAT if a third party router is included
bpwl explains this in more detail here: http://forum.mikrotik.com/t/dhcp-not-passing-through-wireless-link/153840/1
this theme is too messy. its working now, although i suspcect that basebox2 itself is a bit buggy, like any other mikrotik device (i havent seen device so far, wich actually working flawlessly) firstly i configured both CPE and WISP AP. it worked, but one day it didnt allow to either web login or winbox, but it responded to ping and worked as AP. strange i resetted and configured only WISP AP, as 192.168.0.10 in internet section and LAN 10.10.10.10 including dhcp and NAT. so wireless clients should have ip 10.10.10.xx and so on. its working
but i was suprised that basebox configured itself CPE section aswell, - reversing parameters, so it think that internet comes from 10.10.10.10. seems that device can explicitly work as AP or client, but not both (even though client is inactive, its still listed in quick tab) i had some experiences with mantbox, and as its dual band, its even messier. i had an idea to use netmetal ac, but now im not sure it would work as i want it.