Hi @Network_Admin 

Thanks for posting in our business forum.

Have you checked if there is an arp issue on the core switch?

This is something we have never experienced before. If you isolate this switch from the core and other L3 switches, and connect it to a GW-SW-PC setup, will it work steadily?

Hi @Clive_A ,

thanks for your reply.

Wwe have other switches conntected to the core and no problem with them, when we ping it. Currently there is only 1 accesspoint connected to the TP-Link switch. This accesspoint is 100% available when we ping it. So there is no ARP cache problem.

I've change the default VLAN for the uplink port, changed it only to 1 vlan, no change.

Greetings

Christian 

Hi @Network_Admin 

Thanks for posting in our business forum.

Network_Admin wrote

Hi @Clive_A ,

 

thanks for your reply.

 

Wwe have other switches conntected to the core and no problem with them, when we ping it. Currently there is only 1 accesspoint connected to the TP-Link switch. This accesspoint is 100% available when we ping it. So there is no ARP cache problem.

 

I've change the default VLAN for the uplink port, changed it only to 1 vlan, no change.

 

Greetings

 

Christian 

 

 

I am simply asking to test this switch and to confirm if this is a firmware issue even though it might not be.

My point is to verify if the switch is intact. Otherwise, it is the config problem. And something else should be proceeded. There is basically nothing we can do from the web GUI but Wireshark on this switch as it is an L2 switch.

Hello,

sorry for the late answer, but meanwhile I have figured out where the problem is. In my eyes it's definitly a problem of the TP-Link  switch.

I've testet a lot, with changing default VLAN, tagged, untagged and so on. Finally I have resettet the switch and configured it completely new. When the interface is on DHCP everything is working. When I change to static IP the problem comes back. 

Greetings

Christian 

Hi  @Network_Admin 

Network_Admin wrote

Hello,

 

sorry for the late answer, but meanwhile I have figured out where the problem is. In my eyes it's definitly a problem of the TP-Link  switch.

 

I've testet a lot, with changing default VLAN, tagged, untagged and so on. Finally I have resettet the switch and configured it completely new. When the interface is on DHCP everything is working. When I change to static IP the problem comes back. 

 

Greetings

 

Christian 

 

 

If you say so, that's a routing issue.

Yet, the switch does not support layer 3 routing. But it does not have anything to do with the switch L3.

If you use static IP, you should definitely specify the default gateway because that's how the routing from your router comes to the switch. The default gateway should take care of it.

  @Clive_A 

Hi,

trust me, when I switch over to static IP I have entered the default gateway :-) 

With a static IP it works for 20-30 pings and then some pings not, after that again 20-30 pings and so an. 

Greetings

Christian 

Hi @Network_Admin

Network_Admin wrote

  @Clive_A 

 

Hi,

 

trust me, when I switch over to static IP I have entered the default gateway :-) 

 

With a static IP it works for 20-30 pings and then some pings not, after that again 20-30 pings and so an. 

 

Greetings

 

Christian 

You might be right. But I don't have a comment on this as I am not on the same page as you do. I am not following you because of the information gap.