Why Does My Macbook Air Show As a Bridge on My Wifi Network?
We are fighting some network gremlins in our small office. We have an unnecessarily complicated network topology, but I don't believe the network "complexity" is the ultimate issue (total guess). Here's the situation.
Periodically, we have network issues that range from individual devices or IP phones having trouble getting to the Internet, to office-wide outages. The Internet connection appears to be stable during the network issues, and is also big enough to handle the traffic. There doesn't appear to be any issues with the Internet connection itself - FYI.... We have a mixture of Macs and PCs, printers, file server and IP phones using the network. The network is a mix of wifi connected devices and wired devices (generally speaking PCs/Macs wifi connected...printers/phones wired).
The network itself is as follows:
AirOS WAP that is NOT delivering IPs, just bridging to a HP switch, that in turn is connected to a D-Link router that is handling DHCP. D-Link is then connected to our Internet modem. The AirOS WAP is being used because it's signal strength and performance are believed to be better than the D-Link's wifi performance. Note: The wifi radio is turned OFF on the D-Link. All connected devices are showing in the ARP table on the D-Link device (as expected).
But, and I'm finally getting to my question, on the AirOS my MacBook Air (El Capitan) is showing up in the ARP table as a bridge. It's the only device that appears in the ARP table besides the D-Link (also showing as a bridge - which is expected). Simply put, my Mac is "acting" differently than any other device in the office, which we want to eliminate as a potential problem.
Anyone have thoughts on why my Mac is showing as a bridge. I did check my Network settings and nothing appears out of the ordinary on my laptop. (only bridge I find set is Thunderbolt - which is NOT connected)
I'm sure someone has a thought or two on why my device is showing as a bridge in our network, and whether this might be an issue.
Thanks.
MacBook Air, OS X El Capitan (10.11.3)