pfSennse,switch replacement from tplink to Zyxel,VLans not working

2»

All Replies

  • ArmoredPCs
    ArmoredPCs Posts: 11  Freshman Member
    First Comment Friend Collector
    edited September 10

  • ArmoredPCs
    ArmoredPCs Posts: 11  Freshman Member
    First Comment Friend Collector
    https://community.zyxel.com/en/discussion/comment/69322#Comment_69322

    I am the one that installed the Switch and configure it, they did nothing on the switch…

  • ArmoredPCs
    ArmoredPCs Posts: 11  Freshman Member
    First Comment Friend Collector
    https://community.zyxel.com/en/discussion/comment/69260#Comment_69260

    Can we check anything else,does this switch have a CLI or something?

  • PeterUK
    PeterUK Posts: 3,456  Guru Member
    100 Answers 2500 Comments Friend Collector Seventh Anniversary
    edited September 10

    Be interesting to see if all works with the TP switch again

    unless you got port 10 and 12 mixed up

  • Zyxel_Melen
    Zyxel_Melen Posts: 2,567  Zyxel Employee
    Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Administrator - Switch Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate
    Answer ✓

    Hi @ArmoredPCs,

    Thanks for the MAC table. Thanks for the MAC table. I apologize for replying late I was doing a lab in my office.

    From your MAC table, I noticed the GS1900 only learns your pfSense on VLAN1 but no other VLANs like VLAN200. In my lab, my GS1900 learns my pfSense not only VLAN1 but also 20 and 100. My Client connects to port 18 which is in VLAN100.

    image.png

    And my PC gets IP from VLAN100.

    image.png

    Also, there is traffic on VLAN100.

    image.png

    Could you help to check your pfSense setting and its NIC card setting, like VLAN and priority? Your issue is more likely on pfSense. The switch configuration should be good.

    Zyxel Melen


  • ArmoredPCs
    ArmoredPCs Posts: 11  Freshman Member
    First Comment Friend Collector
    https://community.zyxel.com/en/discussion/comment/69405#Comment_69405

    Hello,sorry for the late reply

    I did happen to find the fix for the issue and works exacly as i wanted it.

    Somehow when i uninstalled Suricata (IDS-IPS) it started to give the correct IPs - subnets and VLANS to the devices.

    Suricata was configured to work only for VLAN1 (Internal)

    I have really no idea why would this happen with zyxel switch and no with the tp-link one, what difference it makes on how they communicate.

    I haven't add vlan priority as you asked, What NIC settings would you require me to check?

    Could it be NIC and Switch ports compatibility?

  • Zyxel_Melen
    Zyxel_Melen Posts: 2,567  Zyxel Employee
    Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Administrator - Switch Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate

    Hi @ArmoredPCs,

    Thanks for updating the result with us~

    The VLAN priority is the configuration of my NIC card. In your case, it is more likely related to "Suricata". So, you don't need to change this configuration on your side.

    Zyxel Melen


Categories

Switch Help Center

EnglishTiếng ViệtРусскийไทย中文（台灣）