Find the perfect gift for the grad in your life with Graduation gifts that connects us from AT&T.
smayo44's profile

Tutor

 • 

33 Messages

Saturday, March 18th, 2023 6:03 PM

Fixed Wireless with Pace 5268ac - ethernet port not working

We had a snowstorm which caused all sorts of havoc at my house. When all was said and done, one of my connections to a remote building stopped working. Mind you that this connection had been working for years, even before Fixed Wireless. The connection to the remote building is using a pair of Ubiquiti M900s in bridge mode.  DHCP is handled by the 5268ac. 

There was some water on the power adaptor for the M900 and some burning on the RJ45. I replaced the RJ45 with no success. I then replaced the entire ethernet cable from the POE adaptor to the M900. I then replaced the M900 itself. I am able to go into the setup on both of the M900s from the remote side but not from the 5268ac side. If I plug a laptop in the same ethernet port on the 5268ac, it works and gets an IP address. If I try to connect from the remote side, I do not get an IP address. 

At this point, I have replaced all of the cables and equipment between the two points and it still does not work. 

I do not know if this is important, but when I plug a laptop into the ethernet port on the 5268ac the cord gets a orange light, but when I plug the bridge POE power adaptor in, I get a green light from the socket. 

Does anyone have any ideas?

TIA

ACE - Expert

 • 

35.5K Messages

1 year ago

I think that the color of the light indicates the link speed: Amber (Orange) indicates 1 Gbps.  Green indicates 100 Mbps.

If your laptop works in the 5268AC's port, then that would make me think that it's working and the issue is either in or between the Ethernet bridges.  Do the bridges get their own IP and have a user interface?  If so, try probing them from both sides and see if you can connect to them from both sides.

Tutor

 • 

33 Messages

1 year ago

Thanks for your response. The bridges have their own IP addresses and are set up as 192.168.1.50 & 60. I am able to reach both using a laptop and each side can "see" the other bridge. I am also able to get into each bridge's setup pages.

ACE - Expert

 • 

35.5K Messages

1 year ago

If you can reach the web page of each bridge from something connecting through from the other bridge that seems to say that link is up fine.  This is with the bridge connected to the Gateway and the traffic being routed through the LAN bridge on the Gateway, right?

Tutor

 • 

33 Messages

1 year ago

No. In order to test the local and remote bridges, I set my laptop with a fixed IP in the same subnet as the bridges and connected directly to them on each side. When I try to do it from a wifi port, I get timeouts. Even ping comes back oddly:

>ping 192.168.1.50

Pinging 192.168.1.50 with 32 bytes of data:
Reply from 192.168.1.99: Destination host unreachable.
Request timed out.
Reply from 192.168.1.50: bytes=32 time=3ms TTL=64
Request timed out.

Ping statistics for 192.168.1.50:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 3ms, Average = 3ms

Not sure why this is happening 

ACE - Expert

 • 

35.5K Messages

1 year ago

I set my laptop with a fixed IP in the same subnet as the bridges and connected directly to them on each side.

Okay.

Even ping comes back oddly:

There is something not quite right going on here.

Is 192.168.1.99 the IP address that the laptop was assigned on Wi-Fi?

What happens if you try to ping 192.168.1.254 on the Wi-Fi?

Tutor

 • 

33 Messages

1 year ago

192.168.1.99 is the desktop I am using over wifi that is connected to the 5268ac. It was assigned that number from DHCP. I can ping 192.168.1.254 with no problem from that computer. 

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=5ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64

Ping statistics for 192.168.1.254:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 3ms, Maximum = 5ms, Average = 3ms

Tutor

 • 

33 Messages

1 year ago

Is it possible there is a hardware problem with the 5268ac? I have switched ports for local bridge and it experiences the same problem.

Tutor

 • 

33 Messages

1 year ago

One more thing I will try today is to take the laptop to the remote side and set it with a fixed IP and try to ping 192.168.1.254. BTW: This was working correctly prior to the snow storm. I thought for sure it was the wiring. When I removed the ethernet plug from the Ubiquiti M900 (POE side), there was soot on the RJ45. That is why I suspected the cable and replaced it.  

ACE - Expert

 • 

35.5K Messages

1 year ago

There could be an issue with the 5268AC... it may have taken a voltage surge during a failure of the equipment attached to it.  If it was simple to eliminate other things first, I thought we should try.  

Tutor

 • 

33 Messages

1 year ago

Thanks for responding JefferMC.

I took my laptop to the remote side and set it with a fixed IP address (IPv4) and it did not work. Again, I was able to ping both the remote and local bridges but not the 5268ac. 

I will be calling AT&T to see about getting a replacement 5268ac. Not sure how to approach it. Any suggestions are welcome.

Not finding what you're looking for?
New to AT&T Community?
New to the AT&T Community? Start by visiting the Community How-To.
New to the AT&T Community?
Visit the Community How-To.