Hi everyone,
I’m new and I don t have a lot of experience on networks and mikrotik.
I m here to know if the network that I m posting can be configurated or not. My goal is to have the client with that static ip connected to internet and the possibility to reach it via its ip by other devices connected to the network. I don t know the public ip of the router but i know that it gives me a ip with 192.168.1.*. The mikrotik is the Mikrotik map 2nd
Thank you all
Sounds like your PC needs to be transparently connected to the ISP router, as its on the same LAN subnet.
Thank you for the answer. So you think there is a way to have this network?
Maybe assigning 192.168.1.2/30 to eth1, 192.168.1.4/30 to eth2, 192.168.88.1/30 with dhcp to wlan1?
Anyone can support me please?
Create a WAN bridge, put both ether1 and ether2 on the bridge as ports.
Do you have a starting config you can share??
Very good picture to explain your request.
It’s perfectly possible.
Have you already configured something on that device ?
If not, start clean.
Then for ONE TIME use Quickset - WISP AP
On the left side you can configure wireless settings.
On the right side choose Bridge mode and Dynamic address acquisition.
Then NEVER enter Quick set again.
All config changes afterwards, have to be done using Webfig or Winbox.
I think using WISP AP, you’re already going to have largely what you want.
So holvoe basically using the map2nd as an AP/switch?
The OP wants a second subnet for local internal use, which should be easy to do… as well.
Yup.
Where did you see that requirement ?
Still, it is easy to add but I don’t see it (unless I missed something).
EDIT: Ah … the .88 subnet. Easy to add that once started with WISP AP.
Yup I normally don’t make wild-assed assumptions, I leave that to MKX and Sob. 
In any case will address both scenarios!
This config assumes ALL on same subnet, all dhcp provided by First Router - the map is just an AP/Switch.
The IP address of the map2ND is assigned statically via the IP address setting…
/interface bridge
add ingress-filtering=no name=bridge
/interface list
add name=management
/interface wireless
as required
/interface wireless security-profiles
as required
/interface bridge port
add bridge=bridge interface=ether1
add bridge=bridge comment=defconf interface=ether2
add bridge=bridge comment=defconf interface=wlan1
/ip neighbor discovery-settings
set discover-interface-list=management
/interface list member
add interface=bridge list=management
/ip address
add address=192.168.1.x/24 interface=bridge network=192.168.1.0
/ip dns
set allow-remote-requests=yes servers=192.168.1.1
/ip route
add disabled=no dst-address=0.0.0.0/0 gateway=192.168.1.1
/ip service
set telnet disabled=yes
set ftp disabled=yes
set www disabled=yes
set ssh address=x.x.x.x
set api disabled=yes
set winbox address=as-required
set api-ssl disabled=yes
/tool mac-server
set allowed-interface-list=none
/tool mac-server mac-winbox
set allowed-interface-list=management
In this scenario, I will assume that the WLAN subnet needs to be separate and thus some DHCP service.
This is a big guess so @holvoe relying on you to keep it real.
/interface bridge
add ingress-filtering=no name=bridge
/interface list
add name=management
/interface wireless
as required
/interface wireless security-profiles
as required
/interface bridge port
add bridge=bridge interface=ether1
add bridge=bridge comment=defconf interface=ether2
/ip neighbor discovery-settings
set discover-interface-list=management
/interface list member
add interface=bridge list=management
add interface=wlan1 list=management
/ip address
add address=192.168.1.x/24 interface=bridge network=192.168.1.0
add address=192.168.88.1/24 interface=WLAN1 network=192.168.88.0
/ip pool
add name="DHCP - dab" ranges=192.168.88.2-192.168.88.50
/ip dhcp-server
add address-pool="DHCP - dab" disabled=no interface=wlan1
/ip dhcp-server network
add address=192.168.88.0/24 dns-server=192.168.88.1gateway=\
192.168.88.1
/ip dns
set allow-remote-requests=yes servers=192.168.1.1
/ip route
add disabled=no dst-address=0.0.0.0/0 gateway=192.168.1.1
/ip service
set telnet disabled=yes
set ftp disabled=yes
set www disabled=yes
set ssh address=x.x.x.x
set api disabled=yes
set winbox address=as-required
set api-ssl disabled=yes
/tool mac-server
set allowed-interface-list=none
/tool mac-server mac-winbox
set allowed-interface-list=management