☰

如何让连接从他们在 RouterOS 中输入的相同网关应答？

tag-icon • tag-icon routing load-balancing nat mikrotik routeros
如何让连接从他们在 RouterOS 中输入的相同网关应答？

我有一台MikroTik RouterOS 6.23设备，我的网络如下：

Router
  |
  |-- bridge1_LAN (wlan1 + ether1) (192.168.0.210) -- LAN (192.168.0.0/24)
  |   Here is where computers are. Those include some servers and some users.
  |   Users should be able to navigate always, and servers should
  |   be reachable online always.
  |
  |-- ether2_ADSL (192.168.2.2) -- ADSL router (192.168.2.1) -- WAN
  |   Users should navigate through here because there is no traffic limit.
  |   Incoming traffic should work exactly as with ether3_3G, as a temporary
  |   backup solution in case it fails.
  |
  |-- ether3_3G (192.168.3.2) -- 3G router (192.168.3.1) -- WAN
      This connection has a traffic limit, but faster upload rate, so it's
      mainly for incoming traffic. In case ether2_ADSL fails, this should be
      used as a temporary backup connection for outgoing traffic.

现在，相关配置：

/ip firewall mangle

# This rule is disabled because, when enabled, users cannot browse Internet
add action=mark-routing chain=prerouting connection-mark=no-mark disabled=yes \
    in-interface=ether2_ADSL new-routing-mark=to_ether2_ADSL passthrough=no

# This marks all traffic coming from ether3_3G to get out through there too
add action=mark-routing chain=prerouting in-interface=ether3_3G \
    new-routing-mark=to_ether3_3G passthrough=no

/ip firewall nat
add action=masquerade chain=srcnat out-interface=ether2_ADSL
add action=masquerade chain=srcnat out-interface=ether3_3G

# This is just an example web server listening in port 8069, for testing purposes
add action=dst-nat chain=dstnat comment="Test server" dst-port=8069 \
    in-interface=ether2_ADSL protocol=tcp to-addresses=192.168.0.156 \
    to-ports=8069
add action=dst-nat chain=dstnat comment="Test server" dst-port=8069 \
    in-interface=ether3_3G protocol=tcp to-addresses=192.168.0.156 \
    to-ports=8069

/ip route

# Outgoing traffic by routing-mark
add check-gateway=ping distance=10 gateway=192.168.3.1 routing-mark=\
    to_ether3_3G
add check-gateway=ping distance=10 gateway=192.168.2.1 routing-mark=\
    to_ether2_ADSL

# Outgoing traffic by default
add check-gateway=ping distance=20 gateway=192.168.2.1
add check-gateway=ping distance=30 gateway=192.168.3.1

通过此配置，所有流量都通过ether3_3G除非以太2_ADSL失败了，并且以太2_ADSL否则（大多数时候）。

现在的问题是传入连接只能通过以太2_ADSL. 连接来自ether3_3G总是停留在syn received某个状态。

在我看来，来自ether3_3G到达目标服务器，但响应通过以太2_ADSL这就是 TCP 握手永远无法完成的原因。事实上，如果我物理拔掉以太2_ADSL电缆，然后所有连接ether3_3G开始工作好了。

我该如何修复它？

答案1

您需要标记来自 ether3_3G 的连接，以便您可以标记要通过 ether3_3G 路由回来的回复。

这是一个示例配置（未经测试）

/ip firewall mangle
add action=mark-connection chain=prerouting comment="Mark connection so packets from 3G get returned to 3G properly" disabled=no in-interface=ether3_3G new-connection-mark=3g-packets passthrough=no
add action=mark-routing chain=prerouting connection-mark=3g-packets disabled=no new-routing-mark=3g-packets passthrough=no
add action=mark-routing chain=output connection-mark=3g-packets disabled=no new-routing-mark=3g-packets passthrough=no


/ip route
add disabled=no distance=1 dst-address=0.0.0.0/0 gateway=192.168.3.1 routing-mark=3g-packets

第一条规则将connection-mark在从 ether3_3G 接口到达的任何数据包上放置一个。

第二条和第三条规则将根据该连接标记“捕获”回复，然后routing-mark在这些连接上放置。

第二条规则用于本质上转发的数据包，第三条规则用于路由器本身将发送的回复（例如 ping）

最后，最后的静态路由将通过 ether3_3G 接口路由具有适当路由标记的数据包。

相关内容