TCP port 853 being routed to wrong interface

PeterUK
PeterUK Posts: 3,125  Guru Member
Community MVP 2500 Comments Sixth Anniversary 100 Answers
edited May 2021 in Security

USG60W V4.62

routing rules

user-incoming-- source-  destination--   Service-- next-hop --SNAT

any--vlan4093--any ---  IP192168532-- DNS--    vlan53 -----IP1921685311

any--vlan4093--any---   IP1921685312--DNS--   vlan53----   IP1921685315

any--vlan4093--any---   any-- ---------any---  -wan2-----  none

DNS service is port 53 UDP and TCP 


Logs

Security Policy Control

Match default rule, DROP [count=3]

192.168.253.1:41822

vlan4093

192.168.53.12:853

vlan53

tcp

ACCESS BLOCK

Security Policy Control

Match default rule, DROP [count=3]

192.168.253.1:40828

vlan4093

192.168.53.2:853

vlan53

tcp

ACCESS BLOCK

The next hop for port 853 should be WAN2

All Replies

  • Zyxel_Cooldia
    Zyxel_Cooldia Posts: 1,510  Zyxel Employee
    100 Answers Sixth Anniversary 1000 Comments Zyxel Certified Sales Associate
    Is this issue been there all these while? Or it only happens occasionally? And when it happens, what did you do to recover it?
    Could you send me your configuration file in PM for further checking.

    Don't miss this great chance to upgrade your Nebula org. for free!

  • PeterUK
    PeterUK Posts: 3,125  Guru Member
    Community MVP 2500 Comments Sixth Anniversary 100 Answers
    edited May 2021

    I'm not sure when this bug happened I know every time I turn the WiFi on my phone it happens port 853 is DNS over TLS.


  • PeterUK
    PeterUK Posts: 3,125  Guru Member
    Community MVP 2500 Comments Sixth Anniversary 100 Answers
    edited June 2021

    Its one of them things you think its wrong when in fact its correct!

    Because I have a 192.168.53.0/27 it routes to that no matter what routing rules you have unless you use Overwrite Direct Route.

    Case closed


Security Highlight