I have Samsung M2070W printer connected to network via WiFi. When I changed router to Turris Omnia, printer is not sometimes accessible. Ping from my linux sometime returns (192.168.10.118 is my linux IP):
hlavki@hlavkinb:~> ping obluda
PING obluda (192.168.10.232) 56(84) bytes of data.
From 192.168.10.118 (192.168.10.118) icmp_seq=1 Destination Host Unreachable
From 192.168.10.118 (192.168.10.118) icmp_seq=2 Destination Host Unreachable
From 192.168.10.118 (192.168.10.118) icmp_seq=3 Destination Host Unreachable
Ping from turris router is OK. After some time everythink work correctly also from my linux machine. I found that I am not only one with this problem.
Strange is that with it works fine with previous router (Asus RT-N12).
Have you checked, maybe it is the sleep-modus or something like that.
Many times to save power, printers go in to some kind of sleep modus. Try to look in to that, if you already have and it’s not that, try to connect it with a network-cable. Maybe wifi is the problem. So try these both things first if you have not done it yet.
thanks for reply. As I mentioned, at the same time ping from turris router is OK, but NOT OK from my linux desktop. I also tried to turn off firewall. Printer hasn’t RJ45 plug, only WiFi. I also checked sleep mode and it’s turned off. Maybe there is a problem with router’s firewall.
To be on the safe side with your conclusion, could you maybe try it with another computer or so. Maybe put terminal app on your phone and try to ping from your own phone.
Then you can be sure if it is indeed the firewall. If it is the firewall, look for the ICMP protocol if it is accepted. Sometimes there are those safety protocol against DDOS in routers.
I tried from android, there is 10% packet loss on 100% signal strength. But not always. I also had packet loss on ping turris. I thing this is not normal behaviour. Look at those times (from 1.06 ms to 967 ms):
hlavki@hlavkinb:~> ping turris
PING turris (192.168.10.1) 56(84) bytes of data.
64 bytes from turris (192.168.10.1): icmp_seq=1 ttl=64 time=967 ms
64 bytes from turris (192.168.10.1): icmp_seq=2 ttl=64 time=462 ms
64 bytes from turris (192.168.10.1): icmp_seq=3 ttl=64 time=704 ms
64 bytes from turris (192.168.10.1): icmp_seq=4 ttl=64 time=13.1 ms
64 bytes from turris (192.168.10.1): icmp_seq=5 ttl=64 time=1.82 ms
64 bytes from turris (192.168.10.1): icmp_seq=6 ttl=64 time=1.68 ms
64 bytes from turris (192.168.10.1): icmp_seq=7 ttl=64 time=11.7 ms
64 bytes from turris (192.168.10.1): icmp_seq=8 ttl=64 time=1.24 ms
64 bytes from turris (192.168.10.1): icmp_seq=9 ttl=64 time=58.0 ms
64 bytes from turris (192.168.10.1): icmp_seq=10 ttl=64 time=1.60 ms
64 bytes from turris (192.168.10.1): icmp_seq=11 ttl=64 time=850 ms
64 bytes from turris (192.168.10.1): icmp_seq=12 ttl=64 time=79.0 ms
64 bytes from turris (192.168.10.1): icmp_seq=13 ttl=64 time=3.36 ms
64 bytes from turris (192.168.10.1): icmp_seq=14 ttl=64 time=1.34 ms
64 bytes from turris (192.168.10.1): icmp_seq=16 ttl=64 time=73.5 ms
64 bytes from turris (192.168.10.1): icmp_seq=17 ttl=64 time=1.06 ms
64 bytes from turris (192.168.10.1): icmp_seq=18 ttl=64 time=18.7 ms
64 bytes from turris (192.168.10.1): icmp_seq=19 ttl=64 time=221 ms
64 bytes from turris (192.168.10.1): icmp_seq=20 ttl=64 time=101 ms
64 bytes from turris (192.168.10.1): icmp_seq=21 ttl=64 time=50.6 ms
64 bytes from turris (192.168.10.1): icmp_seq=22 ttl=64 time=0.946 ms
64 bytes from turris (192.168.10.1): icmp_seq=23 ttl=64 time=481 ms
64 bytes from turris (192.168.10.1): icmp_seq=24 ttl=64 time=173 ms
64 bytes from turris (192.168.10.1): icmp_seq=25 ttl=64 time=448 ms
64 bytes from turris (192.168.10.1): icmp_seq=26 ttl=64 time=380 ms
64 bytes from turris (192.168.10.1): icmp_seq=27 ttl=64 time=231 ms
64 bytes from turris (192.168.10.1): icmp_seq=28 ttl=64 time=491 ms
64 bytes from turris (192.168.10.1): icmp_seq=29 ttl=64 time=207 ms
64 bytes from turris (192.168.10.1): icmp_seq=30 ttl=64 time=207 ms
64 bytes from turris (192.168.10.1): icmp_seq=31 ttl=64 time=16.7 ms
64 bytes from turris (192.168.10.1): icmp_seq=32 ttl=64 time=69.7 ms
^C
--- turris ping statistics ---
32 packets transmitted, 31 received, 3% packet loss, time 31072ms
rtt min/avg/max/mdev = 0.946/204.352/967.870/263.205 ms
I looked that link that you posted earlier about other people having the problem. One person said this…
It seems that they are losing wireless communication between Wi-Fi AP and the printer. Turning the PC would it not have any impact.
Not to set any printer saving? If so, try it off completely.
It indeed could also be that the printer is losing the connection. Which network are you using 2.4 or 5 GHz?
Also have you looked if you are using a wifi-channel that is less crowded?
Yes, it needs API Level 22 aka Android 5.1. I may take on issue #57 (support older Versions) if i got my other projects finished but this will take some time.
This i have never stumbled upon. Is there something in API level 22, so necessary that wifianalyzer should use? That is the only conclusion that i am coming up with.
As i though that was the only conclusion that i could come up with.Sadly not going to use it for now.
I am planning to use my Samsung Galaxy S 4 at least till 2020 if it makes it :P. Maybe if a stable Cyanogenmod version is available with maybe Android 6 or even 7 that i then try to put that on it.
My future smartphone will probably be a chineese phone running Android. Hopefully then running Cyanogenmod or something like that so i won’t be dependend on companies anymore for updates.
Ok, anyway problem is still there. After some time printer is temporary unaccessible. Same behavior from android and Linux. Printer is always accessible from router. It is possible to turn off firewall on turris? Maybe problem is there.
I THOUGHT that you already checked on the printer drivers, firmware and such…But my assumption was wrong. I guess you haven’t looked at them. Look at this…
