Ace  Freshman Member

I know the answer! It is Nebula!

I assume your environemt has no DHCP server. because AP keep in 192.168.1.2 Check your router's ip address and login into AP to configure ip address as same with router's subnet. For example: router ip address is 192.168.1.254 You can set AP ip address is 192.168.1.100 mask 255.255.255.0 default gateway 192.168.1.254 DNS :…

I think device reset to factory default already. Because the AP's default ip is 192.168.1.2 if you don't have DHCP server in networking environment. I just plug and play then AP can connect to nebula successfully.what's problem you met?

Did you register AP on nebula? By default AP's NCC discovery is enable and it will keep trying connect to Nebula after factory reset. If you don't unregister AP from NCC, it will be managed by NCC again.

My experience is the same with @PeterUK , the GS1920 support ACL feature but 1900 doesn't have such features. @JackLeach if you don't need to use classifier to control traffic, I think GS1900 is enough for you.

You can use nebula app to scan QR code to register device.

Looks like device control by ncc, you can go to Site-wird > General setting to check local credentials.

Because you change GS1900's ip to DHCP and it should get the new ip address from DHCP server then you will not be able to login via 192.168.1.1 ip address. Since switch was not saved the configuration that is why you can use 192.168.1.1 to access after GS1900 rebooted. I suggest that you can download the ZON Utility to…

Loading.....

@imaohw Did you enable the CPU protection on your XGS3700? My experience is that CPU high may cause by ARP packet. Maybe you can enable it to limit for ARP to see if the problem can resolve or not.

@Tiron No, your source ip mask is 255.255.255.0, its allow 192.168.5.0/24 to access switch. If you want to allow only for 192.168.5.20 to remote access, source ip mask should be "255.255.255.255".

Did you check port interface whether have CRC error count? Did you swap another ethernet cable to verify cable issue? I suggest you can use command "show running-config" to export your configuration first. Then use command "erase running-config" to reset switch currently configuration back to default. After that, notebook…

If your router only send the vlan 1 traffic then it may not be able to communicate between port 25/26 because your vlan 1 is setting forbidden on port 25/26. Could you share your mac table information? Go to Management > MAC table I think it will more clear what the vlan traffic is sending from routers.

You can remove all vlans (exclude default vlan 1) on your switch and enable vlan-trunking on the ports. Switch receives incoming packets with vlan tag will keep then forward to vlan-trunking ports.

If you don't want to be tagged out from port 25/26, why did you configure VLAN-Trunking? You want to untag for VLAN2 on port 25/26, other vlans need to be tagged out?