Connecting duet wifi 2

SIam

@t3p3tony said in Connecting duet wifi 2:

cn you pin the Duet from your machine?

translated: can you ping your machine

SIam

@hellpilot said in Connecting duet wifi 2:

@siam I don't see any major differences. Intranet access is disabled on my guest network. But changing it doesn't seem to have effect.

I'm not sure that this will help, but this is the last idea I have.
Remove all known networks (M588) then reflash your duet board (M997) and after this try to add your wifi again

T3P3Tony

@hellpilot and the other related question from me is what is the IP you are trying to connect from.

Hellpilot

@siam
@T3P3Tony

Awh no luck with this method of reflash of M588. Even reinstalled firmware. Interesting enough I changed my main 2.4 network to enable WPS. I no longer get "Failed while trying to connect to WuTangLan24", it is now "Wrong password while trying to connect to WuTangLan24".

I am not to sure what is meant by pinging?

T3P3Tony

@hellpilot if you are on windows open up a command prompt and send:

ping <ip-address>

where the ip address is the once your machine is getting.

Also to check what ip address the machine you are using has send:

ipconfig

basically i want to see if you can communicate with the duet, and if you are on the same subnet.

SIam

@hellpilot said in Connecting duet wifi 2:

it is now "Wrong password while trying to connect to WuTangLan24"

As shown in your 7. Post the error is the same .... but why nobody knows (at the moment). Which router do you use ? Did you run the router with the latest firmware? Have you tried another channel for your wifi?

Hellpilot

@t3p3tony

This was while connected to my guest network.

Pinging 192.168.50.167 with 32 bytes of data:
Reply from 192.168.50.177: Destination host unreachable.
Reply from 192.168.50.177: Destination host unreachable.
Reply from 192.168.50.177: Destination host unreachable.
Reply from 192.168.50.177: Destination host unreachable.

Ping statistics for 192.168.50.167:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Pinging 192.168.50.167 with 32 bytes of data:

Also

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Hellpilot

@siam
I am using the RT-AX82U, I have tried auto channeling as well as trying out 5.

Thought I would get away with putting my old router in bridge mode but that has proven difficult.

T3P3Tony

@hellpilot I think the problem is you are not on the same subnet ( mention bridge etc). What was your IP? (Ipconfig from the command prompt).

Hellpilot

@t3p3tony
Connecting from IP 192.168.50.177

I connected to my old router's network, just couldn't complete a connection to the web interface. The Duet's IP at that time was 192.168.0.3.

T3P3Tony

@hellpilot ok yeah you need to be in the same subnet.

I see you reported this earlier:

"Wrong password while trying to connect to WuTangLan24".

So confirm the Duet is connected, with the right password, then try the ping test.

SIam

@hellpilot when I can trust the Documentation from your router that is it impossible that you can connect to other clients in your network when you use the guest account.

When you connect to the guest network, which authentication Method you use (open system, wpa2 personal or WPA-Auto-Personal)? Can you look in your WuTangLan24 that you use the same auth method

Hellpilot

@siam @T3P3Tony

I can confirm that I am using the correct password for "WuTangLan24". All my other devices accept no issue, but the duet likes to report a wrong password. I tried pinging but no luck; router shows having a max access time of 9 seconds but I don't think a connection is ever made.

I can turn off WPS for my "WuTangLan24", this changes the Duet response from "wrong password" to "failed connection".

I am using WPA2 personal for my networks.

Also, thank you for taking your time out to trouble shoot madness with me. I appreciate it.

Edit
Went ahead and connected my printer to my old router, just running it locally. Maybe a temporary fix, or will turn into a permanent fix since everything works this way. Lol.

No idea why my new router was so high, seemed a little questionable at 192.168.50.167. The new IP is 192.168.0.3

T3P3Tony

@hellpilot said in Connecting duet wifi 2:

No idea why my new router was so high, seemed a little questionable at 192.168.50.167. The new IP is 192.168.0.3

This is normal, the router will have a IP range and a set of address within that range it allocates so that, in and of itself, was not the issue.

I am glad you got it working with the old router, for our reference when we look at the wifi firmware and the new Espressif SDK can you let me know the model number of the router that doe snot work and the settings it had for authentication, Wifi network protocols etc.

SIam

@hellpilot said in Connecting duet wifi 2:

I am using WPA2 personal for my networks.

Only for interest, what's happens when you use WPA-Auto-Personal as protocol?
Can you post Advance settings -> Systemlog -> General Log and Wifi log

Hellpilot

@SIam
The only protocols available on this router range from Open System, WPA-WPA3 both personal and enterprise.
Should I look for specific events during the time frame I was trying to connect to my network?

@T3P3Tony
My router is the RT-AX82U. Running WPA2 under AES.
801.11ax is turned off for my 2.4GHZ network.
Wireless mode is set to auto (Not legacy or N), with b/g protection.
20/40Mhz channel.

Any other settings that would helpful for the SDK let me know.