Could you share a bit more information on how “doesn’t work” manifests? Assuming you’re using the router’s hostname to connect to it, does DNS resolution work while you’re offline?
I ahve noticed it while there was modem failure and I was trying to use VLC on TV. There was almost infinite loading of samba folders. When internet is working properly, samba works fine too.
If you mean under DNS resolution that, I can reach router after entering its IP, then yes, that is working even offline.
I don´t know what is using VLC on AndroidTV. I have only basic Samba settings, so I think it is only IP. I think VLC is scanning network for network folders, which it remembers from “online” times, so it was trying to reach them, but it took about 5 minutes to show them. And when trying to dig deeper into folder structure it took very very long…
And I remember that TV displayed warnig about disconnected Ethernet network. I have tried to plug and unplug ethernet cable, restart TV and Omnia, but nothing helped. Even disconnecting from electricity.
I’m afraid we won’t get far in terms of troubleshooting based on such sparse information. You could try to access the Samba share from a PC and try to reproduce the issue there – this should allow for better troubleshooting than on the TV.
Besides that you could think about going back to TOS 3 for the time being if it worked better for you. Using schnapps this should be quite easy.
TOS 5 is pretty fine (installed from medkit, so no update from TOS3), internet is working 99,95% of the time. But, this Samba bug is known all over the internet as I have noticed and still not repaired… I have noticed it only due to modem failure at my parent´s and then tried it at home with the same results.
I don´t know if I am doing this right, but NSlookup in LuCI returns this for 192.168.1.1 (no matter if online or offline):
Server: 127.0.0.1
Address: 127.0.0.1#53
** server can't find 1.1.168.192.in-addr.arpa: NXDOMAIN