So currently when I connect to the roboRIO over a wired connection directly to a laptop over either USB or Ethernet I am able to get full comms and everything seems to work fine. However, when the robotio is connected over ethernet to the wireless bridge and a laptop is connected wirelessly to the bridge I am unable to get comms through the driverstation and any attempted pings to roboRIO-1305-FRC.local either timeout or are responded to by the router (10.13.5.1). What complicates this further is that when the bridge is connected to any other robot of ours it works perfectly, attempts to ping roboRIO-1305-FRC.local succeed and we can get comms through the driverstation as well as successfully enable and drive the robot. However not the case on this one particular robot. On top of that whenever I attempt to connect directly from laptop to rio over ethernet and from bridge to rio the ethernet light surrounding the port does light up.
We have attempted to swap cables connecting to the POE injector, powered the bridge off of the barrel adapter and connected it directly to the rio using new ethernet cords, reimaged both the radio and the roboRIO, tried multiple laptops with their firewalls disabled, and nothing seems to solve these weird communication problems.
Because of all these tests, I am lead to believe that the issue lies with the setting and/or software on the roboRIO itself. Currently in settings the RIO is set to configure IPv4 adresses using DCHP or link local. Code is uploaded, it is running 6.0.0.f1 firmware and is imaged on the 2019v14. Has anyone encountered a similar problem? Any hep is greatly appreciated. Thanks