Hi all.
Tell me how to properly organize / configure the priority for Telegram, based on the existing 2 WAN?
Current setup 2 ISP from: https://youtu.be/nlb7XAv57tw?si=X2Ll9hTYdZNGlpn4
For priority, I take from: https://youtu.be/aTLzhQHisSc?si=D4357QbyddFdkVFY
/ip/firewal/mangle print
Flags: X - disabled, I - invalid; D - dynamic
3 ;;; add dist to Telegram list
chain=prerouting action=add-dst-to-address-list address-list=Telegram address-list-timeout=4w2d
in-interface=bridge content=.telegram.org log=no log-prefix=""
4 chain=prerouting action=add-dst-to-address-list address-list=Telegram address-list-timeout=4w2d
in-interface=bridge content=.telegram.me log=no log-prefix=""
5 chain=prerouting action=add-dst-to-address-list address-list=Telegram address-list-timeout=4w2d
in-interface=bridge content=.t.me log=no log-prefix=""
Doesn’t catch packets. There is nothing in “Address Lists”
But something went wrong.
Lead on the right path
Here is what I use. Although, this is for the ECMP. However, one can change that.
/ip firewall address-list add address=149.154.160.0/22 comment="Telegram Messenger Inc" list=AS62041
/ip firewall address-list add address=149.154.164.0/22 comment="Telegram Messenger Inc" list=AS62041
/ip firewall address-list add address=91.108.4.0/22 comment="Telegram Messenger Inc" list=AS62041
/ip firewall address-list add address=91.108.56.0/22 comment="Telegram Messenger Inc" list=AS62041
/ip firewall address-list add address=91.108.8.0/22 comment="Telegram Messenger Inc" list=AS62041
/ip firewall address-list add address=95.161.64.0/20 comment="Telegram Messenger Inc" list=AS62041
/ip firewall mangle add action=mark-connection chain=prerouting comment= connection-state=new dst-address-list=AS62041 new-connection-mark=Telegram passthrough=yes
/ip firewall mangle add action=mark-routing chain=prerouting connection-mark=Telegram new-routing-mark=ISP2 passthrough=no
@own3r1138, version ROS? Not working:-(
ROS 7, The address list is 100% correct. You should work on your mangles.
/ip firewall address-list
add address=91.108.4.0/22 list=Telegram
add address=91.108.8.0/22 list=Telegram
add address=91.108.12.0/22 list=Telegram
add address=91.108.16.0/22 list=Telegram
add address=91.108.56.0/22 list=Telegram
add address=95.161.64.0/20 list=Telegram
add address=149.154.160.0/22 list=Telegram
add address=149.154.164.0/22 list=Telegram
add address=149.154.168.0/22 list=Telegram
add address=149.154.172.0/22 list=Telegram
,
/ip firewall mangle
add action=mark-connection chain=prerouting comment=\
"mark connection all Telegram address list" dst-address-list=Telegram \
new-connection-mark=Telegram-Conn passthrough=yes protocol=tcp
add action=mark-packet chain=prerouting comment=\
"mark packet all Telegram address list" connection-mark=Telegram-Conn \
new-packet-mark=Telegram-Packet passthrough=no
add action=mark-connection chain=prerouting comment=\
"all new connections from ISP1 marked with ISP1_conn" connection-mark=\
no-mark connection-state=new in-interface=ether1 \
new-connection-mark=ISP1_conn passthrough=yes
add action=mark-connection chain=prerouting comment=\
"all new connections from ISP2 marked with ISP2_conn" connection-mark=\
no-mark connection-state=new in-interface=lte1 \
new-connection-mark=ISP2_conn passthrough=yes
add action=mark-routing chain=output comment=\
"route ISP1 connections back through ISP1" connection-mark=ISP1_conn \
new-routing-mark=ISP1 passthrough=yes
add action=mark-routing chain=output comment=\
"route ISP2 connections back through ISP2" connection-mark=ISP2_conn \
new-routing-mark=ISP2 passthrough=yes
add action=mark-connection chain=prerouting comment=\
"divide traffic from LAN into two groups ISP1" connection-mark=no-mark \
connection-state=new dst-address-type=!local in-interface=\
bridge new-connection-mark=ISP1_conn passthrough=yes \
per-connection-classifier=src-address-and-port:3/0
add action=mark-connection chain=prerouting comment=\
"divide traffic from LAN into two groups ISP1" connection-mark=no-mark \
connection-state=new dst-address-type=!local in-interface=\
bridge new-connection-mark=ISP1_conn passthrough=yes \
per-connection-classifier=src-address-and-port:3/1
add action=mark-connection chain=prerouting comment=\
"divide traffic from LAN into two groups ISP2" connection-mark=no-mark \
connection-state=new dst-address-type=!local in-interface=\
bridge new-connection-mark=ISP2_conn passthrough=yes \
per-connection-classifier=src-address-and-port:3/2
add action=mark-routing chain=prerouting comment=\
"route ISP1 connections through ISP1" connection-mark=ISP1_conn \
in-interface=bridge new-routing-mark=ISP1 passthrough=yes
add action=mark-routing chain=prerouting comment=\
"route ISP2 connections through ISP2" connection-mark=ISP2_conn \
in-interface=bridge new-routing-mark=ISP2 passthrough=yes
,
/queue simple
add comment=Telegram name=queue-Telegram packet-marks=Telegram-Packet \
priority=1/1 target=""
Even if I turn off the PCC rules
;;; marked packets from Telegram address list
chain=prerouting action=mark-packet new-packet-mark=Telegram-Packet passthrough=no
dst-address-list=Telegram log=no log-prefix=""
below rules PCC
Why bother, I have never had to prioritize traffic. Assuming your pipe is extremely small???
Quite right, very “narrow” at the moment.
Until a new provider arrives, I am practicing on mice.