Hello everyone,
I have an ADSL modem with the subnet 192.168.1.1/24. I set up the repeater bridge mode in the Mikrotik and I created a new wireless network, called Repeater, and the ADSL’s wireless network is called Zyxel.
The very first time, the wireless network Repeater is only repeating the Zyxel and when I connect to Repeater, I have internet access and my private IP is something like 192.168.1.20, and I can visit all websites like google.
Now I create a DHCP server on my Mikrotik within the subnet 192.168.73.1/24. Now if I connect to Repeater, my private IP is 192.168.73.2 for example, and in the Mikrotik > IP > DHCP Server > Leases, I see I’m connected. I see in my ipconfig[i/] in my Windows CMD that my gateway is 192.168.73.1 and when I open the gateway, I see the Mikrotik admin page.
But the issue is I don’t have any internet access in this case.
I see in IP > Firewall > Connections that my laptop is sending an ICMP request but I don’t have any internet access.
This is how I created an activated the repeater mode in Mikrotik: I created a security profile to connect to my ADSL modem. I created a Wireless interface to connect to my Zyxel modem, then I created a virtual interface called Repeater so I can connect to my Mikrotik.
Are there anything I didn’t do or did I do anything wrong in this case?
I hope I said the required data to see what’s done up to now.
Indeed config is needed. Many things can be missing.
I see the Mikrotik admin page.
But can you get to the modem (192.168.1.1) from 192.168.73.2 ?
What is used? Masquerade/srcnat on the modem/MT line? Or Modem has been told 192.168.73.0/24 is via the MT router ?
Some modems don’t have IP route settings for the LAN, then Masquerade/srcnat is needed on the MT, for the return path. (Typical default WAN connection case on MT to modem, not bridge mode)
decide as in the above story about using either
the bridged solution (with station-pseudo bridge)
or
the routed solution with masquerade/SRCNAT as the ADSL modem is limited in settings
SRC-NAT is done in the FW (the default masquerade rule was there, for all traffik going out the WAN-interfacelist).
“Bridge NAT” is for MAC addresses, not usefull here.
use mode “station” for the routed solution, no station-pseudobridge
WLAN1 should not be a port on the bridge, for the routed solution. WLAN2 is port on the bridge
add WLAN1 to the WAN interface list
add bridge to the LAN interface list
ports on a bridge are slave interfaces only. The handling (like DHCP and and interface list) is defined by the bridge only, not by the interface membership.
LAN and WAN interface lists are used by the default configuration settings ( eg: deny incoming if not from LAN list (!LAN) , masquerade if outgoing interface is in WAN list)
WLAN1 gets a 192.168.1.x IP address (or has a DHCP client there.)
The bridge has the 192.168.73.1 IP address.
(ether1 address is maybe used correctly by bridge, but is a sub-optimal configuration. Address setting not refused by ROS, like the DHCP server would be refused)
Source NAT (or masquerade for automatic NAT address selection) is OK. It is for all destinations (0.0.0.0/0), and source filter 192.168.73.0/24, if outgoing interface is on the WAN interface list.
DST nat seems not usefull here. (is for forwarding incoming requests from the modem to a MT LAN connected device)