I had the “Rb2011UiAS-2HnD” in cascade with Vodafone Station Revolution. It worked well but for a space problem i want to fully replace this router with mikrotik’s.
So i started today to watch some tutorials on this forum and i collected the information from my isp’s site. What i got:
Username: vodafoneadsl
Password: vodafoneadsl
Required WAN interface: Gigabit Ethernet Full-Douplex Auto-Sensing with Ethernet 802.1q protocol.
Link to isp’s guide: (https://www.vodafone.it/portal/Privati/Supporto/Fibra--ADSL-e-Telefono/Installare-e-configurare/Modem-Alternativo)
According to ISP’s guide you should be running PPPoE client on top of vlan1 interface. No DHCP client needed there … And the vlan1 interface should be using VLAN ID 1036.
To keep your router safe, add dynamically created pppoe interface (by default, its name is pppoe-out1) to the interface list named WAN.
Thank you for the fast response. I modified as you said and the yellow mark on the connection properties of windows disappeared. I still can’t use internet ( tried using google and pinging 8.8.8.8 )
To correct what i did before i modified the DHCP Client to ether1 (as it was as default). I went to “Quick Set” → “Router” —> “Port: Eth1” → “PPPoE” and i setted up User and Password.
Thanks in advance.
From the screenshot I gather that the PPPoE is up and tunning. To proceed we need more information, which are hard to get from screenshots. So please proceed by exporting current configuration in text form:
open terminal window
run command /export hide-sensitive file=config20190323.rsc
fetch the output file via files menu
open it in a decent text editor (if you’re using windows, use wordpad, not notepad). Check if it shows some sensitive information (private IP addresses are not sensitive, some private usernames or WiFi SSIDs and PSKs are) and obfuscate them
copy-paste it here … inside code environment, available when editing answer as icon on the black background
While having terminal window open you can try to check for internet connectivity from the router itself. Example would be running command /tool traceroute 8.8.8.8 …
Traceroute prooves that router has working internet connectivity.
A few things to change:
from this moment, don’t use quickset anymore. Change things directly in appropriate winbox sections.
router’s LAN IP address should be defined on bridge “interface”, not on ether2… before changing that part, enable safe mode (I believe there’s a button to enable/disable it somewhere on the edge of base winbox window). After you do the change and you can still work with router via winbox, exit the safe mode. If the change breaks connectivity between router and winbox, router will revert the change after a few seconds (less than half minute)…
disable DHCP client which is running on ether1 interface
fix firewall rule with comment “defconf: drop all from WAN not DSTNATed” … it should refer to in-interface-list=WAN instead of currently configured in-interface=vlan1
the important one: fix NAT rule so that it will refer to out-interface-list=WAN (instead of currently configured out-interface=vlan1)
[edit]
Another change (which won’t change a thing but should be done for syntactical reasons): add interface vlan1 to WAN interface list …
Thank you! I succeeded in configuring the router. I would like to have a little explanation about the difference between out-interface-list and out-interface.
There’s no big difference, out-interface-list allows you to refer to multiple interfaces and it’s not necessary that all of them make sense in certain case. In your case only pppoe-out1 really carries traffic which we want to target (e.g. for masquerade rule), but it doesn’t hurt to add vlan1 (tagged interface which doesn’t have IP setup) and ether1 (physical interface without IP configuration as well).
Keep in mind that firewall usually affects IP traffic and interfaces without IP config don’t directly participate in firewall operations.
Also keep in mind that it’s routing engine which decides which interface will be used as egress (exit) interface, not firewall. Which means only one interface will be used for transmitting the packet and use of interface lists in firewall rule doesn’t change it. Either out-interface or out-interface-list is only one of criteria which a packet needs to match in order for firewall to execute the action (masquerade in your particular case).
Use of interface lists brings one very nice side effect: if e.g. WAN interface changes from vlan1 to pppoe-out1, it’s enough to adjust interface list membership, no need to change firewall rules.
