Re: Switches Not Passing Packets
Posted: Fri Aug 20, 2021 8:48 am
Hello all,
I have a WS-8-150-DC Rev F running v1.5.6 in production that I believe is experiencing this issue. (not 100% sure if this was the factory firmware or not)
1) Passing traffic on a newly configured VLAN that does not have a "Watchdog" IPv4 address set consistently does not work. Traffic starts passing as soon as I add *ANY* IPv4 address to the VLAN interface on the switch. (and traffic will immediately stop for that VLAN once again if I disable the IP on that VLAN)
2) At times on switch reboot, the router would have another device's MAC address in it's ARP table instead of the Netonix's on what was supposed to be the Netonix's management IP address. (I did verify this was not a simple IP address conflict, and it occurred again when I set the Netonix IP to static on a random address nothing else has ever used on the network.)
3) Getting a DHCP lease for the management interface is hit or miss. (looks like udhcpc would get a SIGTERM in some cases) I saw what appeared to be uni-directional traffic flow at times here. (sometimes saw the DHCP discovery packets on the server interface, saw the server respond, but the Netonix seemed to not be able to receive them, and continued to send discovery packets.)
Does this sound like the same bug, or am I dealing with something else here?
Thanks.
(spent my late night maintenance window trying to debug this issue instead of the original tasks...)
I have a WS-8-150-DC Rev F running v1.5.6 in production that I believe is experiencing this issue. (not 100% sure if this was the factory firmware or not)
1) Passing traffic on a newly configured VLAN that does not have a "Watchdog" IPv4 address set consistently does not work. Traffic starts passing as soon as I add *ANY* IPv4 address to the VLAN interface on the switch. (and traffic will immediately stop for that VLAN once again if I disable the IP on that VLAN)
2) At times on switch reboot, the router would have another device's MAC address in it's ARP table instead of the Netonix's on what was supposed to be the Netonix's management IP address. (I did verify this was not a simple IP address conflict, and it occurred again when I set the Netonix IP to static on a random address nothing else has ever used on the network.)
3) Getting a DHCP lease for the management interface is hit or miss. (looks like udhcpc would get a SIGTERM in some cases) I saw what appeared to be uni-directional traffic flow at times here. (sometimes saw the DHCP discovery packets on the server interface, saw the server respond, but the Netonix seemed to not be able to receive them, and continued to send discovery packets.)
Does this sound like the same bug, or am I dealing with something else here?
Thanks.
(spent my late night maintenance window trying to debug this issue instead of the original tasks...)