So you both have about the same configuration and requirements in terms that you both want to connect something to the LAN ports which has to get one of those public addresses.
(I could call you too but all my Arabic consists of "mumke bukra" so it wouldn't be helpful 
)
So based on the configuration posted by @Najifares:
First remove this bridge or keep it in place but use its name everywhere below instead of the public-ip-lan:
/interface bridge
add name=EFM protocol-mode=none
Add two bridges (or reuse the one above for one of them). You'll connect devices which need a public address to one of them and devices for which a private address is enough to the other one.
/interface bridge add name=public-ip-lan protocol-mode=none
/interface bridge add name=private-ip-lan protocol-mode=none
Now unless you are connected using Winbox via MAC address of the Mikrotik, you must enter the two following commands on a single line in the terminal window (you cannot do it by clicking) exactly as written here (except the name of the bridge if you have chosen another one, and except @rabienz as your current state may be different). And before doing it, press Ctrl-X to enter safe mode - if something fails, the change will revert after about a minute and you'll be able to get back again:
/ip address set interface=private-ip-lan [find interface=ether2];/interface bridge port add bridge=private-ip-lan interface=ether2
If the change was successful, /ip address print should show you that address 192.168.88.1/24 is on interface private-ip-lan and /interface bridge port print should show you that interface ether2 is a member port of bridge private-ip-lan. If this is true, you may press Ctrl-X again to exit safe mode.
Next, as you will be connecting the box to public addresses, define tight firewall rules limiting access to Mikrotik itself, otherwise some malware will conquer the box in no time:
/ip firewall filter
action=accept chain=input connection-state=established,related
action=drop chain=input connection-state=invalid
action=accept protocol=icmp
action=accept chain=input in-interface=public-ip-lan disabled=yes comment="permit any access from LAN with public IPs if really sure you need it"
action=accept chain=input in-interface=private-ip-lan comment="permit any access from LAN with private IPs"
action=accept chain=input in-interface=pppoe-out1 protocol=udp dst-port=520 comment="permit incoming RIP packets"
action=drop chain=input
Provide also firewall filter rules protecting the LAN devices, once everything starts working you may add rules permitting access from the internet side to those addresses for some services:
/ip firewall filter
action=fasttrack-connection chain=forward connection-state=established,related
action=accept chain=forward connection-state=established,related,untracked
action=drop chain=forward connection-state=invalid
action=accept chain=forward in-interface=public-ip-lan
action=accept chain=forward in-interface=private-ip-lan
action=drop chain=forward
Keep this in place:
_**/interface pppoe-client
add add-default-route=yes disabled=no interface=ether1 name=pppoe-out1 password=XXXXXXXXXXXXXX use-peer-dns=yes user=L407722@ogeronet-2M.com
/ip hotspot profile
set [ find default=yes ] html-directory=flash/hotspot**_
This has been already changed above:
/ip address
add address=192.168.88.1/24 interface=ether2 network=192.168.88.0
so now it says
/ip address
add address=192.168.88.1/24 interface=private-ip-lan network=192.168.88.0
replace this line
add address=77.42.216.32/29 interface=EFM network=77.42.216.32
by the following one:
add address=77.42.216.33/29 interface=public-ip-lan network=77.42.216.32
The address must be the one out of the /29 subnet which has not been assigned to you - the idea behind is that this will be the gateway in that public subnet. So maybe it is actually not 77.42.216.33 but 77.42.216.38, I cannot know.
replace this NAT rule
_**/ip firewall nat
pppoe-out1 not ready
add action=src-nat chain=srcnat out-interface=pppoe-out1 src-address=192.168.88.1 to-addresses=77.42.216.32/29**_
by the following one, so that you would only NAT addresses from private-ip-lan as they will access internet, to the address dynamically assigned by the ISP:
/ip firewall nat
add action=masquerade chain=srcnat out-interface=pppoe-out1 src-address=192.168.88.0/24
replace the following
/routing rip interface
add interface=pppoe-out1 receive=v2
add disabled=yes receive=v2
by just this:
/routing rip interface
add interface=pppoe-out1 receive=v2 transmit=v2 passive=no
Keep this:
/routing rip network
add network=77.42.216.32/29
but remove this:
add network=192.168.88.0/24
Now, add an ethernet interface or more (I don't know your device model so cannot be more precise) to the bridge named public-ip-lan:
/interface bridge port
add bridge=public-ip-lan interface=ether3
By now it should work, so if you connect a PC to ether3 and manually set one of the public IPs from the /29 subnet on it, with Mikrotik's address on the bridge as gateway, and open some "what's my IP" web page, it should show that PC's public address.
