Case #1: Crack the Case for Switch (Answer Revealed)

Zyxel_Richard

Join the Hunt Now

Attention, all gaming enthusiasts and tech-savvy Zyxel detectives!

The moment you've been waiting for has arrived - Case #1: Crack the Case for Switch is officially open! Are you ready to put your problem-solving skills to the test and embark on an exciting journey to uncover the mysteries behind network errors on the Switch? If so, read on to discover how you can crack this case and have the chance to win fantastic prizes.

Your Collaborative Efforts

Don't feel like you're in this alone! We encourage you to discuss your findings and strategies with other enthusiasts who are also hot on the trail of these network errors. Feel free to share your insights and ask for help right below this announcement if you're stuck.

Here, you can engage in conversations with fellow enthusiasts, share your progress, and discuss your findings. Remember, teamwork makes the dream work.

Good luck, Zyxel detectives!

Leave Your Findings.

dot_EXE

Sounds like a VLAN issue 🧐

Zyxel-Watson

Hello Detectives,

I'm here to deliver you your Public Service Announcement!

💡Facts about Cloud Managed Switches💡

 

Did you know that cloud managed switches support Access Control List (ACL) to implement policies on specified client traffic?  

The Switch ACL Policies only include:

   - ALLOW

   - BLOCK 

Additionally, unlike your cloud managed firewalls, the switch ACL rule ends with a Default Rule rule that bypasses (allows) all traffic. This means that traffic not matching any of your previous ACL rules are forwarded by your Ethernet switch.

 

Keep up the investigation,

Watson 🕵️

SamerShream

Hello everybody…

The first question is whether it can be IP subnet for vlan100 is 192.168.100.0/24 and lan1 is 192.168.1.0/24؟

They're from two different networks

the second question

What are the options in a VLAN(in ACL OPTIONS) ?

Zyxel-Watson

Hello @SamerShream

That's correct! The VLAN100 subnet is defined as 192.168.100.0/24 while LAN1 subnet is 192.168.1.0/24.
So the expected subnet for Switch and AP Management should be in 192.168.100.0/24. But the customer's network seem to be directing it to 192.168.1.0/24, instead.

Switch ACL rules allows users to define VLANs as a criteria. And as stated in the previous post, Switch ACL actions include "Allow" and "Block" only. There should be no option to change VLAN tags.

Good Luck,
Watson🕵️

Zyxel-Watson

Are you chasing shadows or have you cracked this case with concrete evidence?

Check out the revealed answer here.

See you in Case #2: Crack the Case for WiFi Network, Zyxel Detective

Watson🕵️