When in AP mode Flint light is flashing, but everything seems to be working. Although i can't find it on my network, when I look on my routers device list. I didn't have time to tinker with it, so I let it be for several weeks. But today i noticed that the light had stopped flashing. I could see Flint in my router device list now and could connect to the ip adress. Later that same day after a couple of hours it starts flashing again and it's not displayed in the device list. What is this? Is this a problem with my Flint 2 or my router, is it some setting, or my setup process when making Flint a access point?
Maybe it is detecting the availability of the Internet. Bule flashing means the track is unreachable, but the Internet is available, probably the IP(s) cannot ping.
You can return to the Router mode, close the interface state tracking, and then switch to the AP mode.
Only way to get back to router mode is to reset Flint. Because i can't reach it
Ok so I managed to get into router mode, and did the change suggested. And then back to AP mode. No difference. How long does the bridging to AP mode take. Still flashing blue light.
I'm at a loss here. The one main reason for getting Flint 2 is for setting up a dedicated network for SteamVR with quest3. Can it by that theres a conflict when connecting Flint to a orbi satellite rather then directly into router? Unfortunately my only option is connecting Flint to a satellite because that is where the PC:s are.
Ok, so there´s something weird going on here. I´m getting two IP:s for the M6000. See pic
Flint is flashing blue and I cant connect to either of them.
And now its dissapeared from the device list
I´ve been doing some tests. When I attach the Flint to Orbi node I get the IP adress 192.168.1.55. When I ping it from the Orbi network I get this:
Pinging 192.168.1.55 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 192.168.1.28: Destination host unreachable.
Reply from 192.168.1.28: Destination host unreachable.
When I turn Flint into AP mode, it shows up in the Orbi device list with a different IP and other MAC. When I try to ping both the new and old IP this is what I get.
Pinging 192.168.1.13 with 32 bytes of data:
Reply from 192.168.1.28: Destination host unreachable.
Reply from 192.168.1.28: Destination host unreachable.
Reply from 192.168.1.28: Destination host unreachable.
Reply from 192.168.1.28: Destination host unreachable.
Ping statistics for 192.168.1.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
PS C:\Users\vasic> ping 192.168.1.13
Pinging 192.168.1.13 with 32 bytes of data:
Reply from 192.168.1.28: Destination host unreachable.
Reply from 192.168.1.28: Destination host unreachable.
Reply from 192.168.1.28: Destination host unreachable.
Reply from 192.168.1.28: Destination host unreachable.
After a couple of minutes the device dissapers from the Orbi device list.
I try to reboot Flint and my Orbi says hey there buddy here´s your IP, but Flint just stares back with no answer and just "PUFF" it wanishes like a Jedi.
The WAN address of the Router mode and AP mode probably is different, so there are 2 IPs DHCP offer from the main router. But only 1 IP under works.
Seems strange, it cannot ping the IP of Flint 2 from the same subnet clients.
Does the main routing have a MAC black/white list? Since it seems that Flint 2 has no access.