Networking Issues

[achampion]

Firmware: 1.10.1
Luban: 3.11.0 (3.12.3 / 3.13.0)
Laptop: MacOS Catalina (10.15)
Router: Asus AC88U

I'm having some problematic connectivity issues.

1. Connects to the wrong wifi... there's no option in the UI to forget a previous wifi network and because of the challenges I was having I changed to a different wifi network. However, when I restart it connects to the old wifi network.

2. When connected to wifi the device keeps going unreachable. It claims to be still connected to the wifi (and still prompts to "disconnect" if previously connected to luban) but does not respond to pings (or connection requests from Luban). Or, more confusingly, will respond (ping) to one device but not the other device (e.g. will not respond to a ping from the router but will respond to a ping from my laptop or vice versa).

E.g.:

[I] 08:11 me@laptop ~
[0]# ping 10.0.1.8                                                                                                                                                              08:11:19
PING 10.0.1.8 (10.0.1.8): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1

5 mins later with no changes:

[I] 08:16 me@laptop ~
[0]# ping 10.0.1.8                                                                                                                                                              08:16:22
PING 10.0.1.8 (10.0.1.8): 56 data bytes
64 bytes from 10.0.1.8: icmp_seq=0 ttl=64 time=229.912 ms
64 bytes from 10.0.1.8: icmp_seq=1 ttl=64 time=46.247 ms
64 bytes from 10.0.1.8: icmp_seq=2 ttl=64 time=84.399 ms

Note: these are extremely long ping times, and also the same when pinging from the router:

admin@RT-AC88U-2280:/# ping 10.0.1.8
PING 10.0.1.8 (10.0.1.8): 56 data bytes
64 bytes from 10.0.1.8: seq=0 ttl=64 time=65.940 ms
64 bytes from 10.0.1.8: seq=1 ttl=64 time=88.947 ms
64 bytes from 10.0.1.8: seq=2 ttl=64 time=111.269 ms
64 bytes from 10.0.1.8: seq=3 ttl=64 time=159.139 ms

And then some random time in the future it will stop responding to pings and luban disconnects. Sometime later it will start to respond to pings again. And the cycle repeats.

Request timeout for icmp_seq 45
ping: sendto: Host is down
Request timeout for icmp_seq 46
ping: sendto: Host is down
Request timeout for icmp_seq 47
ping: sendto: Host is down
Request timeout for icmp_seq 48
Request timeout for icmp_seq 49
64 bytes from 10.0.1.8: icmp_seq=50 ttl=64 time=19.050 ms
64 bytes from 10.0.1.8: icmp_seq=51 ttl=64 time=41.959 ms
64 bytes from 10.0.1.8: icmp_seq=52 ttl=64 time=66.361 ms
64 bytes from 10.0.1.8: icmp_seq=53 ttl=64 time=186.642 ms
64 bytes from 10.0.1.8: icmp_seq=54 ttl=64 time=103.617 ms

Because of this it seems to be very problematic to "discover" so I've had to downgrade to Luban 3.11 in order to be able to manually connect and not get a blank screen (Snapmaker/Luban#640)

[ywabiko]

+1 for this feature (forget Wifi).
Also, please show MAC address on Settings -> About Machine.

These two are very important when you are using MAC address filtering.

[efedel]

Another vote for forget-wifi. MAC addr would be nice.

There's a common new-machine workflow that goes something like this:

1. connect to the wide-open guest Wifi network, troubleshooting as necessary
2. connect to the secure Wifi network once step 1 succeeds

When doing this on the Snapmaker, any problems (bad password, timeouts) with the secure network cause a default connection to the guest network. If all computers are on the secure network, Luan etc cannot connect to the Snapmaker.

Another problem with the controller wifi setup is that selecting a protected network requires re-entering the password every time. Maybe that should be the long-press option when a password has already been stored.

UPDATE: Just a quick follow-up. I disabled the guest network so that the snapmaker controller would be forced to connect to the password-protected network. The controller was unable to do so, which makes me wonder:

a) if the initial setup uses different connection code, which is able to handle WPA
b) if the initial setup failed to connect, but reported success
c) if the controller is incapable of connecting to WPA-protected networks
d) if the controller does not support long passwords (~ 30 characters)

[mr-manuel]

2. When connected to wifi the device keeps going unreachable. It claims to be still connected to the wifi (and still prompts to "disconnect" if previously connected to luban) but does not respond to pings (or connection requests from Luban). Or, more confusingly, will respond (ping) to one device but not the other device (e.g. will not respond to a ping from the router but will respond to a ping from my laptop or vice versa).

I have exaclty the same issue since the update from Luban 3 to 4 and update from the Snapmaker 2.0 A250 firmware to the latest version. The Snapmaker has 4 meters distance to the WiFi Access Point and there is no wall or other objects in between. I'm not able to print directly from the PC anymore. I have to copy the files to the USB and then plug the USB in the Snapmaker. Could we please investigate furter to solve this for all?

[szimonek]

I have my WiFi router standing 2 meters above Snapmaper 2.0, and machine can't even find my wireless networks, but finds networks from my neighbours. This ticket wasn't even answered within over two years. This is unacceptable.

Maybe we all should fill a support issue to stop being ignored by snapmaker support?