My setup for ROS 6.49.17 (on an hAP lite) has only a few additions from the default configuration, just to add a PPTP Client and includes the following:
Likewise, my setup for ROS 7.15.3 (on a hAP ax3) also only includes the following additions (I discovered that I had to create the “routing-mark” first in the “routing table”):
My PPTP tunnel is created successfully, and I can use Tools > Ping to ping sites using their IP addresses, however, when I attempt to ping using a “name” e.g. www.google.com (which works under ROS6), under ROS7 I get “Error in Ping To - ip address expected!”
It appears that the router (192.168.90.1) although still pingable is being treated differently in ROS7, and hence DNS lookups are not working.
I read in thread (http://forum.mikrotik.com/t/routing-mark-and-route-traffic-to-a-different-gw/160754/1) that something changed in handling of packets with routing marks, however I am still quite a novice with RouterOS and would appreciate a tip on what I need to change/add to regain ROS6 style handling of the router itself (i.e. 192.168.90.1 in my case).
If you use WinBox, then DNS resolution happens on client (PC where it runs). It’s not clear what it uses as DNS server. But in case the problem really is caused by routing marks, you can always exclude router by adding dst-address=!192.168.90.1 to mangle rule (or dst-address-type=!local to cover all router’s addresses).
I’m trying to follow this tutorial https://www.youtube.com/watch?v=2pFcVRaoscE to add a VPN connection using Wireguard to warp Cloudflare.
But when I try to add mangle rules, on action “mark routing”, the ‘new routing mark’ doesn’t show the routing tables that I already add.
I’m adding routing tables on Routing → Tables, menu.
I already rebooted the router, and then the routing tables came up.
But there is more problem, I’m using recursive failover, wan 1 to my main internet, and wan 2 to my second internet as backup.
When I follow the last tutorial it
add mangle “chain prerouting, src. address range of default-dhcp, action mark-routing, new routing mark to-Cloudflare”
add routes that “Dst. Address 0.0.0.0/0 to gateway wireguard1, and routing table to-Cloudflare”,
It works, and my internet connection follows the wireguard VPN, but after apply route my winbox disconnected from my routerboard and can’t connect via IP, only via mac address, any suggestion ?
here is my new configuration that I already follow that tutorial
Way before wireguard you have to fix the errors in your config…
Firstly, you state ether2 is a WAN port and yet you have ether2 on the bridge… It should be removed.
It also states that you ahve ether3, and ether4 on the bridge but earlier you have them bonded and you also have the bond on the bridge.
Im no expert but one does not put all of them on the bridge and I would hazard a guess just the bond.
Now you have the bonding on the bridge and bridge doing dhcp hands out iP addresses for .88 subnet.
Why do you have the bond associated with vlan22 on the single interface bridge vlan rule??
/interface bridge vlan
add bridge=bridge tagged=bridge,bonding1 vlan-ids=22
It should be… /interface bridge vlan
add bridge=bridge tagged=bridge untagged=wlan2 vlan-ids=22
Fix interface list members. /interface list member
add comment=defconf interface=bridge list=LAN add interface=vlan22 list=LAN
add comment=defconf interface=ether1 list=WAN
add interface=ether2 list=WAN
Recommend adding this mangle rule to ensure help with potential MTU issues.
/ip mangle
add action=change-mss chain=forward new-mss=1380 out-interface=wireguard1 protocol=tcp tcp-flags=syn tcp-mss=1381-65535
++++++++++++++++++++++++++++
What is going on IP addresses between 192.168.88.2-192.168.88.9 >>>>???
/ip dns static
add address=192.168.88.1 comment=defconf name=router.lan type=A
add address=192.168.88.2 name=switch1.logi.lo type=A
add address=192.168.88.3 name=switch2.logi.lo type=A
add address=192.168.88.5 name=tlmr1.logi.lo type=A
It also states that you ahve ether3, and ether4 on the bridge but earlier you have them bonded and you also have the bond on the bridge.
Im no expert but one does not put all of them on the bridge and I would hazard a guess just the bond.
Now you have the bonding on the bridge and bridge doing dhcp hands out iP addresses for .88 subnet.
Why do you have the bond associated with vlan22 on the single interface bridge vlan rule??
/interface bridge vlan
add bridge=bridge tagged=bridge,> bonding1 > vlan-ids=22
It should be… /interface bridge vlan
add bridge=bridge tagged=bridge > untagged=wlan2 > vlan-ids=22
Fix interface list members. /interface list member
add comment=defconf interface=bridge list=LAN add interface=vlan22 list=LAN
add comment=defconf interface=ether1 list=WAN
add interface=ether2 list=WAN
Im trying to follow you, remove bonding1 from tagged vlan bridge, and add vlan22 on lan interface list, but it doesn’t work. My access point using vlan to divide wireless. The diagram its on image attachments. Or do I made mistakes here ?
Why is vlan22 disabled??
Its on already enabled.
++++++++++++++++++++++++++++
What is going on IP addresses between 192.168.88.2-192.168.88.9 >>>>???
/ip dns static
add address=192.168.88.1 comment=defconf name=router.lan type=A
add address=192.168.88.2 name=switch1.logi.lo type=A
add address=192.168.88.3 name=switch2.logi.lo type=A
add address=192.168.88.5 name=tlmr1.logi.lo type=A
by adding dst-address=!192.168.90.1 to mangle rule my problems vanished. Problem solved.
