Hi great_white and thank you for taking the time.
I had the issue since the beginning with factory installed FW 1.0.00 build 14 and then with 1.0.00 build 15 and 1.0.01 build 2.
I am using the X3000 only as a router. I have another router/modem provided by the ISP (Telenor) because I have VoIP phone.
The X3000 is connected to the Telenor router by Ethernet cable and all the clients are connected to the X3000 through WLAN and LAN. I reconfigured the DHCP server away from factory IP ranges, passwords and with some fixed addresses for instance for the printer and the NAS. Of course the WiFi has been reconfigured with new SSID, password, etc.
It is configured in mix 20/40 MHz. I also have a few port forwarding configured.
I tried to play a bit with firewall parameters, disabling etc. but it did not change anyhting. I did not play with MTU and other deep parameters at all.
For a while I had a USB hard drive shared, but then I bought a NAS and removed the USB drive. That's when I started to experince the routing problems more drastically.
The basic symptom is that after a while (days) one of my devices (Android tablet) could not even ping the NAS (QNAP). I checked the NAS of course and the only way to make it work again was to factory-reset the router and enter the config by hand again. Exact same config.
I have noticed other weird things: like the webUI not showing entirely the heading or not even proposing the menu for sharing storage. see below (firmware version not shown, menu missing). It happened with any FW version I tried.
I also noticed that the DHCP client table was mixed-up after a few days: client names not corresponding to the right IP or MAC address, WLAN-connected device shown as LAN, etc. which makes me think there may be a software issue in the indexation of the routing tables.
FInally I also noticed that the DHCP client table shows empty if you use an appostrophy in the SSID name. Somehting like "John's network" would mess-up all the JAVA based (I think) pop-up windows of the UI (including but not limited to showing the DHCPclient list), while "John_network" would be fine. I know it is a strage way to call an SSID, but this character is still supposely supported by IEEE802.11.
I may be facing multiple small issues witht he router as I can't believe someone would put a product on the market with so poor testing. But anyway, the routing issue and the appostrophy thing are more than real.
