made the Verdin SoM an AP that I can start and I can connect to it, and remote in, but if I connect to a different wifi, and my Verdin also connects to the same wifi, I can’t remote in anymore. To better explain:
Scenario 1:
Network 1 = Local home network, Verdin AP is not enabled
Verdin and PC are both connected. I can remote in just fine
Scenario 2:
Network AP = Verdin is AP is enabled
PC is connect to Verdin AP. I can remote in just fine
Scenario 3:
Network 1 = Local home network, and Verdin AP is enabled (shows in Wi-fi list)
Verdin and PC are both connected to the Local home network. Can not remote in.
I think in Scenario 3, the AP is setting a static IP I’m thinking this has something to do with it. I want to be able to remote in on a local network, even if my AP is enabled. Any ideas.
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello!
It sounds like you’re encountering a common issue when using the Verdin SoM as both an Access Point (AP) and a client on your local home network. Let’s break down the scenarios and explore some solutions.
Understanding the Scenarios:
Scenario 1: When the Verdin AP is not enabled, both your Verdin and PC connect to the local home network without any issues, allowing for successful remote access.
Scenario 2: With the Verdin AP enabled and your PC connected directly to it, remote access works fine because the PC is directly connected to the Verdin AP.
Scenario 3: When both the Verdin and your PC are connected to the local home network and the Verdin AP is enabled, remote access fails. This might be due to the Verdin AP assigning a static IP that conflicts with the local network’s DHCP settings.
Solutions to Consider:
Configure the Verdin AP in Bridge Mode: This configuration allows the AP to pass through the local network’s DHCP settings without assigning its own static IPs, which could prevent conflicts.
Disable DHCP on the Verdin AP: If the Verdin AP is assigning static IPs, disabling its DHCP server might help. This allows the local network’s DHCP server to manage IP assignments, avoiding conflicts.
Ensure Both Devices are on the Same Subnet: Verify that both the Verdin and your PC are on the same subnet when connected to the local home network. You may need to adjust the IP settings of the Verdin to avoid conflicts with the local network’s IP range.
Test Connectivity: After implementing these changes, test the remote access functionality again to ensure it works as expected when both devices are connected to the local home network with the Verdin AP enabled.
By following these steps, you should be able to maintain remote access to the Verdin SoM even when it is acting as an AP and connected to your local network.
Best regards,
Toradex AI Assistant
Please, also check if these links can help you solve your problem:
