Packet flow explore for main route unknown

PeterUK
PeterUK Posts: 2,655  Guru Member
First Anniversary 10 Comments Friend Collector First Answer
edited April 2021 in Security

ZyXEL VPN300 V10.02(ABFC.1)

I have a backup 4G dongle and I get in main route this I think it might be happening when the 4G renews the IP and adds another unknown to the list, it does not seem to be causing any problems however.


Comments

  • Zyxel_Cooldia
    Zyxel_Cooldia Posts: 1,426  Zyxel Employee
    First Anniversary 10 Comments Friend Collector First Answer

    Hi @PeterUK

    From the screenshot, the cellular interface gateway is 192.168.3.1, and the VPN300 interface GE6 IP/subnet is 192.168.3.1/24 by default.  

    It looks like it was caused by subnet confliction. Can you change interface GE6 IP and try it again?

  • PeterUK
    PeterUK Posts: 2,655  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer

    GE6 was already changed to 192.168.252.1/255.255.254.0.

  • Zyxel_Cooldia
    Zyxel_Cooldia Posts: 1,426  Zyxel Employee
    First Anniversary 10 Comments Friend Collector First Answer

    Hi @PeterUK ,

    Which 4G dongle are you using ? Can you send me your configuration file via private message. I would like to do some test based on your configuration file. 

  • PeterUK
    PeterUK Posts: 2,655  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer

    Just to update whats showing in Packet flow explore for main route now


  • PeterUK
    PeterUK Posts: 2,655  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer


    Router> show ip route

    Flags: A - Activated route, S - Static route, C - directly Connected

          O - OSPF derived, R - RIP derived, B - BGP derived, G - selected Gateway

          ! - reject, H - Black hole, L - Loop


    IP Address/Netmask   Gateway         IFace          Metric   Flags   Persist

    ===============================================================================

    0.0.0.0/0            192.168.3.1     cellular1      0        AS      -

    0.0.0.0/0            192.168.3.1     unknown        0        AS      -

    0.0.0.0/0            192.168.3.1     unknown        0        AS      -

    0.0.0.0/0            192.168.3.1     unknown        0        AS      -

    0.0.0.0/0            192.168.3.1     unknown        0        AS      -

    0.0.0.0/0            192.168.3.1     unknown        0        AS      -

    0.0.0.0/0            192.168.44.1    vlan443        0        ASG     -

    0.0.0.0/0            0.0.0.0         usb0           0        S       -

    0.0.0.0/0            0.0.0.0         usb0           0        S       -

    0.0.0.0/0            0.0.0.0         usb0           0        S       -

    0.0.0.0/0            0.0.0.0         usb0           0        S       -

    0.0.0.0/0            0.0.0.0         usb0           0        S       -

    0.0.0.0/0            0.0.0.0         usb0           0        S       -

    0.0.0.0/0            0.0.0.0         usb0           0        S       -

    127.0.0.0/8          0.0.0.0         lo             0        ACG     -

    127.255.255.76/30    0.0.0.0         br0            0        ACG     -

    127.255.255.80/30    0.0.0.0         br1            0        ACG     -

    192.168.2.0/24       0.0.0.0         ge5            0        ACG     -

    192.168.3.0/24       0.0.0.0         cellular1      0        ACG     -

    192.168.44.0/29      0.0.0.0         vlan443        0        ACG     -

    192.168.53.0/28      0.0.0.0         vlan53         0        ACG     -

    192.168.247.0/24     192.168.255.202 ge3            0        ASG     -

    192.168.252.0/23     0.0.0.0         ge6            0        ACG     -

    192.168.255.48/28    0.0.0.0         vlan18         0        ACG     -

    192.168.255.192/26   0.0.0.0         ge3            0        ACG     -

  • PeterUK
    PeterUK Posts: 2,655  Guru Member
    First Anniversary 10 Comments Friend Collector First Answer

    Just wanted to update this as it was fixed with 10.02(ABFC.2)ITS-WK47-r90761 but the change to V4.35 the fix might have been lost as of testing with V4.35(ABFC.0)ITS-WK47-2020-01-02-1912000979D the unknowns are happening.

Security Highlight