ping my smart switch static ip not working, but logs display some activity for that ip
-
Hey,
Need some help to troubleshoot a problem.The ip (10.10.9.25) belongs to TL-SG2008P manageable switch and it's set as static in pfsense on management_9 vlan (the switch is connected to pfsense through a trunk of a few vlans, including management_9 vlan).
When I ping the switch in pfsense from the respective subnet/vlan or automatically selected (default) I'm getting 100% packet loss. At the same time the firewall logs displays,
Feb 10 23:29:19 igb4 (1000019420) 10.10.9.25:56034 255.255.255.255:29810 UDP
each few seconds.
The WiFi AP1 and other unmanageable switch connected to TL-SG2008P are working looks like OK ( I have checked by connecting to a few SSIDs with my phone and the internet was working fine.Does anybody knows why the ping for switch ip is not working, but the logs still displays some activity for that ip?
I have restarted the switch, but without luck.
The switch is disconnected in Omada dashboard and as a result my second AP2 schedule is not working, could not change the switch settings. The omada oc200 hardware controller is connected to TL-SG2008P directly through untagged management_9 vlan and I could access the omada dashboard and ping the controller, but not the switch).Any help is greatly appreciated.
-
@ady2 said in ping my smart switch static ip not working, but logs display some activity for that ip:
it's set as static in pfsense on management_9 vlan
How is it set as static in pfSense? A static DHCP mapping?
Does pfSense have an IP in that subnet?
The subnet mask could be set incorrectly in the switch. The broadcast traffic you see would still arrive.
Steve
-
. @stephenw10
Yes, static in pfsense DHCP server for management_9 interface (vlan 9), set the switch mac address and 10.10.9.25 ip . It may be that I configured something wrong (I'm not a network engineer), but it worked fine from September 2021.Maybe let me explain how it's setup:
The TL-SG2008P manageable Omada supported switch, connected to pfsense through a trunk of several tagged vlans (9, 50,51,53, 56, 59, 61) on port 7. The port 8 is untagged for vlan 9 and it's connected to oc200 omada controller. The port 6 is a trunk of several tagged vlans (9, 50, 51,59) connected to other manageable switch on other side of the house. Port 1 (POE) is connected to AP1 through a trunk of several tagged vlans (9, 50, 51, 53, 56, 61). Port 2 (POE on schedule in omada controller) connected to AP2 through a trunk of several tagged vlans (9, 50, 51, 53, 56). Port 3 (POE) is powering the AT&T ONT device through a poe converter.The AP1 is working fine (tested on my iPhone by connecting to all 5 SSIDs that using the vlans 50, 51, 53, 56, 61. The ip were correct from each vlan subnets and the internet was working.
The oc200 controller has an ip 10.10.9.15 (from vlan 9) and I could access the Omada dashboard through the ip address and the ip is ping-able from pfsense.
The AP1 ip is 10.10.9.3 (vlan 9), displayed as connected in Omada dashboard and it's ping-able from pfsense.
AP2 is not working because it's on schedule in omada controller and controller could not see the TL-SG2008P switch to turn on/off the poe port 2. Also the port 2 is off on the switch.What I did: restarted the controller -same result. Restarted the switch - same result. Disconnected the ethernet cable from port 7 on the switch and wait 10 seconds and connected back - same result.
How to troubleshoot in such situation?
I'm thinking to reset the switch (need to do that during the night as it will disrupt the internet for whole house and hope it will get it's assigned 10.10.9.25 ip from pfsense.
-
@ady2 This might be a silly suggestion, but make sure you enabled the switch to use DHCP to get the IP from pfsense. Alternatively, you can set the switch to use a static IP and you could manually assign the IP in pfsense to it.
-
@ady2 said in ping my smart switch static ip not working, but logs display some activity for that ip:
static in pfsense DHCP server for management_9 interface (vlan 9), set the switch mac address and 10.10.9.25 ip .
Imo for switches it is safer to set the management interface static mapping on the switch not a dhcp server.
The problem is with out that traffic on any of the switches port can influence what the management interface becomes on any boot.
-
If your switch is pulling a DHCP lease you can see is current but you can't connect to it it might be time to reset it.
Make sure you're using a client in the same subnet. It may well block connections from outside it's own subnet by default.Steve
