Using a Netgear EX6120 wifi extender to reach to a somewhat remote igate with the following config:
TTGO_T_BEAM_V1_2
Igate Version date: 2025-06-20
Build date: 2025-06-19 16:16:27 UTC
the igate will not connect to the extender (other devices have no issue connecting) and always uses the second SSID in the Wifi Access list.
The extender SSID and password are different than the router . I have tried Address reservation and normal DHCP for the igate in the router, both produce the same result.
Is there something unique about connecting to an extender that the igate is not supplying or is the SSID connection period too short?
Thanks,
N2VEN
Using a Netgear EX6120 wifi extender to reach to a somewhat remote igate with the following config:
TTGO_T_BEAM_V1_2
Igate Version date: 2025-06-20
Build date: 2025-06-19 16:16:27 UTC
the igate will not connect to the extender (other devices have no issue connecting) and always uses the second SSID in the Wifi Access list.
The extender SSID and password are different than the router . I have tried Address reservation and normal DHCP for the igate in the router, both produce the same result.
Is there something unique about connecting to an extender that the igate is not supplying or is the SSID connection period too short?
Thanks,
N2VEN
<!-- github-sync-id:3278506084 -->
SSID is: ext_zach and password contains only letters and numbers (11 characters long). The second SSID (which it does connect to) is: zach_net and password has only letters and numbers (9 character long)
SSID is: ext_zach and password contains only letters and numbers (11 characters long). The second SSID (which it does connect to) is: zach_net and password has only letters and numbers (9 character long)
<!-- github-comment-id:3137927259 -->
can you avoid the "_" and test it on the repeater SSID ? (i've seen some esp32 had trouble with them on SSID and check that the SSID and PASSWORD of the first one do not have any " " before or after the characters too
can you avoid the "_" and test it on the repeater SSID ? (i've seen some esp32 had trouble with them on SSID and check that the SSID and PASSWORD of the first one do not have any " " before or after the characters too
<!-- github-comment-id:3137933249 -->
2.4G and 5G capable, I am using the 2.4G path to the repeater (selected by use of the SSID). I have also tried turning off the 5G path in the repeater, no change.
2.4G and 5G capable, I am using the 2.4G path to the repeater (selected by use of the SSID). I have also tried turning off the 5G path in the repeater, no change.
<!-- github-comment-id:3137963808 -->
save just the needed one and delete all the others (also use the needed one in the first position = don't have a empty wifi defined at first)
how many WIFI are defined and saved on the board?
save just the needed one and delete all the others (also use the needed one in the first position = don't have a empty wifi defined at first)
<!-- github-comment-id:3138051931 -->
Only two are defined, first one is the repeater, second is the primary wifi router.
If the first and only one is the repeater, the igate goes into AP mode (192.168.4.1)
Only two are defined, first one is the repeater, second is the primary wifi router.
If the first and only one is the repeater, the igate goes into AP mode (192.168.4.1)
<!-- github-comment-id:3138251542 -->
i mean, any other firmware to test to connect the same board to this wifi repeater to test everything is running fine with it ?
i mean, any other firmware to test to connect the same board to this wifi repeater to test everything is running fine with it ?
<!-- github-comment-id:3139784889 -->
I have loaded Meshtastic FW and it also will not connect to the repeater! Must be something in the ESP32 wifi code that is not handling things properly, your thoughts?
I have loaded Meshtastic FW and it also will not connect to the repeater! Must be something in the ESP32 wifi code that is not handling things properly, your thoughts?
<!-- github-comment-id:3140110527 -->
I have loaded Meshtastic FW and it also will not connect to the repeater! Must be something in the ESP32 wifi code that is not handling things properly, your thoughts?
show/paste here a picture of your board.
> I have loaded Meshtastic FW and it also will not connect to the repeater! Must be something in the ESP32 wifi code that is not handling things properly, your thoughts?
show/paste here a picture of your board.
<!-- github-comment-id:3140117542 -->
nothing strange there besides the marks on one corner but this should not affect the wifi connections neither the wifi to one SSID and others don't (like the repeater)
maybe a reset of the repeater (as some do save for some time clients to avoid?)?
i'm running out off ideas :/
nothing strange there besides the marks on one corner but this should not affect the wifi connections neither the wifi to one SSID and others don't (like the repeater)
maybe a reset of the repeater (as some do save for some time clients to avoid?)?
i'm running out off ideas :/
<!-- github-comment-id:3140203578 -->
I agree, I'm out of ideas also that's why I sought your help.!
I am going to look into purchasing a different chipset board, is there one you could recommend?
I agree, I'm out of ideas also that's why I sought your help.!
I am going to look into purchasing a different chipset board, is there one you could recommend?
<!-- github-comment-id:3140289508 -->
I agree, I'm out of ideas also that's why I sought your help.! I am going to look into purchasing a different chipset board, is there one you could recommend?
different LoRa board? or different WiFi-Repeater ?
> I agree, I'm out of ideas also that's why I sought your help.! I am going to look into purchasing a different chipset board, is there one you could recommend?
different LoRa board? or different WiFi-Repeater ?
<!-- github-comment-id:3140363270 -->
I configured the repeater in AP mode, the t-beam can now connect to it. Although not ideal for my application (since an ethernet connection is now needed) I can move forward.
Still a mystery as to why repeater mode will not work.
I configured the repeater in AP mode, the t-beam can now connect to it. Although not ideal for my application (since an ethernet connection is now needed) I can move forward.
Still a mystery as to why repeater mode will not work.
<!-- github-comment-id:3141169748 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Using a Netgear EX6120 wifi extender to reach to a somewhat remote igate with the following config:
TTGO_T_BEAM_V1_2
Igate Version date: 2025-06-20
Build date: 2025-06-19 16:16:27 UTC
the igate will not connect to the extender (other devices have no issue connecting) and always uses the second SSID in the Wifi Access list.
The extender SSID and password are different than the router . I have tried Address reservation and normal DHCP for the igate in the router, both produce the same result.
Is there something unique about connecting to an extender that the igate is not supplying or is the SSID connection period too short?
Thanks,
N2VEN
does the extender has " " or special characters in the SSID or Password?
SSID is: ext_zach and password contains only letters and numbers (11 characters long). The second SSID (which it does connect to) is: zach_net and password has only letters and numbers (9 character long)
can you avoid the "_" and test it on the repeater SSID ? (i've seen some esp32 had trouble with them on SSID and check that the SSID and PASSWORD of the first one do not have any " " before or after the characters too
Removed the _ in the SSID no change. Confirmed there are no " " before and or after the SSID or password
is your wifi-repeater only 5G wifi ?
2.4G and 5G capable, I am using the 2.4G path to the repeater (selected by use of the SSID). I have also tried turning off the 5G path in the repeater, no change.
how many WIFI are defined and saved on the board?
save just the needed one and delete all the others (also use the needed one in the first position = don't have a empty wifi defined at first)
Only two are defined, first one is the repeater, second is the primary wifi router.
If the first and only one is the repeater, the igate goes into AP mode (192.168.4.1)
with other firmwares can you connect to the repeater? any other firmware with wifi?
I can connect Android Phone and Tablets. I don't have any other IOT type devices to try.
i mean, any other firmware to test to connect the same board to this wifi repeater to test everything is running fine with it ?
I have loaded Meshtastic FW and it also will not connect to the repeater! Must be something in the ESP32 wifi code that is not handling things properly, your thoughts?
show/paste here a picture of your board.
nothing strange there besides the marks on one corner but this should not affect the wifi connections neither the wifi to one SSID and others don't (like the repeater)
maybe a reset of the repeater (as some do save for some time clients to avoid?)?
i'm running out off ideas :/
I agree, I'm out of ideas also that's why I sought your help.!
I am going to look into purchasing a different chipset board, is there one you could recommend?
different LoRa board? or different WiFi-Repeater ?
Different LoRa board
Which WLAN Security do you use at the router and the extender, WPA2 / WPA3 ?
WPA2-PSK [AES] on both router and extender.
I configured the repeater in AP mode, the t-beam can now connect to it. Although not ideal for my application (since an ethernet connection is now needed) I can move forward.
Still a mystery as to why repeater mode will not work.
so at least your board is not bad! :)
Yes!
Thank you very much for real time support with this issue! Your the Best.
73's
lets hope you find the issue with the repeater or return it 😅