You can likely configure the name and IP of the bridge to Static (unchanging) and manually forward the ports for the device to the device’s ip so that this won’t happen anymore. The good news is that this is something you actually have control over. This is something known as DHCP and DHCP leasing. In fact, most networks are designed to reassign new local ip addresses to devices on a regular basis depending on the configuration of the router/gateway and if you own it or not. The reason this is the most likely is that this can and will happen without you, the customer doing anything. Issue 3: “Your bridge’s ip/local address on the network has changed.” We also have a great guide on this that could help you solve it. Shouldn’t take more than one call to resolve that.
#Free airbridge not working how to
If you don’t know how to do this, I'd reach out to your ISP (Internet Service Provider) or router maker for more info. You have a dedicated network name for the base Wi-Fi (2.4 Ghz) that the lock will connect to and a different name for the faster 5 Ghz devices to connect to. The way you solve this is to make sure that your network bands are separated from each other. This means most modern networks will allow it to connect initially but when your network restarts, the power goes out, or the bridge updates it could then lose connection and stay that way. The bridge doesn’t support the 5 Ghz band of Wi-Fi.
This also is a issue when you connect your phone to the Wi-Fi during the initial setup because it's hard to tell which frequency you're connected to of the Wi-Fi. If you said “Hey Sally!”, which one would know to respond? This is the issue with the bridge being on a network where both bands of the Wi-Fi are sharing a singular name. Imagine you had two friends named Sally and you invited them over for tea.
Issue 2: “Your Wi-Fi is broadcasting two different frequencies using the same Wi-Fi network name instead of having the network names being independent of each other.” (We’ll address this later on in Issue 3.) It doesn’t address the fact that the IP might change due to the managing device reassigning IP addresses. This would still be a temporary solution. This might trigger the managing device (the router/gateway) to possibly set up uPnP (Universal Plug and Play) again to the new IP address of the bridge where it would allow the user to connect remotely. This could help with connectivity but typically why this might work to solve the issue is the same reason support will ask us to disconnect and reconnect the bridge (possibly after a reset of the bridge). Issue 1: “The bridge could need a firmware update.” Let’s explore each of these and see why they would be the solution and how it might be a combination of the three that might permanently solve our issues.
We tried to include some links to click on to help explain certain concepts when possibly. If any of the following seems like Greek to you, I would recommend using google to look up the term being using as this might be somewhat technical. You probably want to know “Why is my bridge not working?”, right?
0 kommentar(er)
