Intermittant Wireless routing problem on new router setup.

[clashcityrocker]

Thanks, I will try and get that onto it tonight. Assuming it's still in it's "dead" connection state, I can Bluetooth the file across from my phone.

[clashcityrocker]

Sadly the app you linked appeared to want an internet connection to run!!

Attached are some other diagnostics from the dead NON WORKING connection device

Screenshot_2014-05-08-18-32-35.png

Screenshot_2014-05-08-18-33-32.png

Screenshot_2014-05-08-18-34-36.png

I have managed to get these and keep the tablet in its funny connection state. If you can think of any other Linux android network commands to run that may help, or commands to run in the router telnet, let me know.

[clashcityrocker]

And from another deviceWORKING on the same WiFi network taken at the sane time..

Screenshot_2014-05-08-18-31-59.png

Screenshot_2014-05-08-18-33-42.png

Screenshot_2014-05-08-18-34-28-picsay.jpg

[clashcityrocker]

And we have another tablet that's also not talking to the internet, even whilst the other one is playing up too. Interestingly (or not), this one is connected to my other WiFi AP (the 2.2Ghz one). So it's happening on both networks. Disabling and renabing the Wifi on the 2nd device, and it's not back online and happy. I will leave the original one dead, incase there is anything you want me to run.

[Tomken]

Netalyzr does require Internet as it checks various aspects of your connection, but thought the problem was intermittent on all devices.

Try it on one of the working devices and you'll see what it does.

Is the Android capable of connecting to the 'net without a router or does it require the router's WiFi ?

If the latter, try assigning a static IP address either as a reserved one within the DHCP range or to one outside of it.

If that works then either re-flash the firmware or ask billion_fan for a link to revert the f/w to out of the box.

[clashcityrocker]

This is where things get really odd.

When I changed the device with no internet to a static IP in the right range, internet was accessible. Put it back to a static IP that was the same as it got assigned by dhcp, and its not connecting again.

Its like that particular IP address is currently a backhole. Whilst others work. There is nothing odd about the IP assigned.

[Tomken]

It sounds like the DHCP is buggy and re-flashing the f/w or reverting it to out of the box should normally resolve that.

Can you assign another device with that .108 IP to see if it has the same effect - and is this with just that device switched on ?

From the previous shots there doesn't seem to be an IP conflict with other devices but if the DHCP is refreshing for some reason, then that could cause a conflict if the previous one hasn't been released as well as routers have been known to duplicate IP addresses, but billion_fan will know more about that than me.

You should remove your phone number from that screen shot.

[billion_fan]

This is where things get really odd.

When I changed the device with no internet to a static IP in the right range, internet was accessible. Put it back to a static IP that was the same as it got assigned by dhcp, and its not connecting again.

Its like that particular IP address is currently a backhole. Whilst others work. There is nothing odd about the IP assigned.

Have you tried to add your devices to the 'Static IP Lease List' list?? (found under 'Configuration >> LAN >> Static IP Lease List, the IP addresses assigned should be outside the DHCP range, once set restart the device)

[clashcityrocker]

Will do this. I currently only have a print server and a linux file server as static, everything else is left to be dynamic. The statics are outside the range of the dynamics, to avoid conflicts.

[clashcityrocker]

Happy to say the problem has totally disappeared since assigning static IP addresses to all my common devices on my network.

Not ideal, but at least it's alleviated the problem.