G10 Router is worst i have ever bought

wardog wrote: wardog typed in a post above this wrote: Admin panel > Wireless > Wireless-2.4G > TX Power Adjustment Admin panel > Wireless > Wireless-5G > TX Power Adjustment radicaldoc discovers where wrote: Aaahh i have found it in wireless and TX is set at 100% I knew you could find it. Pensioner my butt. Now, hehe, are BOTH the 2.4G and 5G bands set to 100%? Again, see the top of THIS post for where each are found. Too, list out all your wireless devices, phone(s) included, that connect to the router if you would be so kind.

yes they are both at 100% as for devices at the moment i am only using 2 mobile phones (oneplus one and homtom 7) and a samsung tab 3. on wireless. this may change in the future ..
and wired 1. my PC and 2. A VU+ Solo 2 Linux box...
that's it nothing else. As i said maybe if i can get it to work any better i will add more but not while it is like this.
I have to add i have changed nothing except the passwords and the LAN ip address everything else is on default..
thanks

My log if it is any use.....

Feb 13 01:52:41 (none) daemon.notice netifd: Interface 'loopback' is now up
Feb 13 01:52:42 (none) local6.debug upnpd[9380]: UPnP SDK Successfully Initialized.
Feb 13 01:52:42 (none) local6.debug upnpd[9380]: Succesfully set the Web Server Root Directory.
Feb 13 01:52:42 (none) local6.debug upnpd[9380]: IGD root device successfully registered.
Feb 13 01:52:43 (none) local6.debug upnpd[9380]: Advertisements Sent.  Listening for requests ...
Feb 13 01:52:43 (none) local6.debug upnpd[9408]: UPnP SDK Successfully Initialized.
Feb 13 01:52:43 (none) local6.debug upnpd[9408]: Succesfully set the Web Server Root Directory.
Feb 13 01:52:43 (none) local6.debug upnpd[9408]: IGD root device successfully registered.
Feb 13 01:52:44 (none) local6.debug upnpd[9408]: Advertisements Sent.  Listening for requests ...
Feb 13 01:52:45 (none) local0.notice redis[9489]: Max number of open files set to 10032
Feb 13 01:52:45 (none) local0.warn redis[9489]: Warning: 32 bit instance detected but no memory limit set. Setting 3 GB maxmemory limit with 'noeviction' policy now.
Feb 13 01:52:45 (none) local0.notice redis[9489]: [truncated]                 _._                                                              _.-``__ ''-._                                                    _.-``    `.  `_.  ''-._           Redis 2.6.13 (4692d19d/1) 32
Feb 13 01:52:45 (none) local0.warn redis[9489]: Server started, Redis version 2.6.13
Feb 13 01:52:45 (none) local0.warn redis[9489]: WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_mem
Feb 13 01:52:45 (none) local0.notice redis[9489]: The server is now ready to accept connections on port 6379
Feb 13 01:52:45 (none) local0.notice redis[9489]: The server is now ready to accept connections at /var/run/appflow/redis.sock
Feb 13 01:52:46 (none) user.warn sbsaved[9669]: Failed to open file /var/run/appflow/stats.redis: 2
Feb 13 01:52:46 (none) daemon.err sead[9825]: sea loglevel error is available
Feb 13 01:52:46 (none) daemon.notice sead[9825]: (NOTICE): sea loglevel notice is available
Feb 13 01:52:46 (none) daemon.notice sead[9839]: (NOTICE): connection event log: eventdb:connections (trim: -768)
Feb 13 01:52:46 (none) daemon.notice sead[9839]: (NOTICE): flow event log: eventdb:events  (trim: -22500)
Feb 13 01:52:46 (none) daemon.notice sead[9839]: (NOTICE): feature discovery event log: eventdb:features (trim: -768)
Feb 13 01:52:46 (none) daemon.notice sead[9839]: (NOTICE): connected to redis server /var/run/appflow/redis.sock:0
Feb 13 01:52:46 (none) daemon.notice sead[9839]: (NOTICE): connected to redis server /var/run/appflow/redis.sock:0
Feb 13 01:52:46 (none) user.info nodedetect[9892]: (INFO): Loaded 178 device patterns from /etc/appflow/devices.
Feb 13 01:52:47 (none) daemon.notice qdiscman[10073]: (NOTICE): using uplink interface: eth0 (index 2)
Feb 13 01:52:47 (none) daemon.notice qdiscman[10073]: (NOTICE): using downlink interface: br0 (index 13)
Feb 13 01:52:47 (none) daemon.notice qdiscman[10073]: (NOTICE): using redis server: 127.0.0.1
Feb 13 01:52:47 (none) daemon.notice qdiscman[10073]: (NOTICE): using redis port: 6379
Feb 13 01:52:47 (none) daemon.notice qdiscman[10073]: (NOTICE): using redis oversub channel: oversub
Feb 13 01:52:47 (none) daemon.notice qdiscman[10073]: (NOTICE): using redis flow bytes channel: flows.bytes
Feb 13 01:52:47 (none) daemon.notice qdiscman[10073]: (NOTICE): using redis bandwidth events channel: bandwidth.events
Feb 13 01:52:47 (none) daemon.notice qdiscman[10073]: (NOTICE): blocking feature not available when zones are configured
Feb 13 01:52:47 (none) daemon.notice qdiscman[10073]: (NOTICE): connected to redis server 127.0.0.1:6379
Feb 13 01:52:47 (none) daemon.notice qdiscman[10073]: (NOTICE): connected to redis server 127.0.0.1:6379
Feb 13 01:52:47 (none) daemon.notice flowmark[10084]: (NOTICE): connected to redis server (null)
Feb 13 01:52:47 (none) user.info overlord[10091]: (INFO): No weights set for conversational.
Feb 13 01:52:47 (none) user.info overlord[10091]: (INFO): Using default weights.
Feb 13 01:52:47 (none) daemon.info blockman[10098]: (INFO): creating blockman
Feb 13 01:52:47 (none) daemon.info blockman[10098]: (INFO): subscribed to flows.block
Feb 13 01:52:47 (none) daemon.info blockman[10098]: (INFO): blockman_init: connected and subscribed
Feb 13 01:52:47 (none) daemon.info blockman[10098]: (INFO): starting main loop.
Feb 13 01:52:47 (none) daemon.info blockman[10098]: (INFO): subscribed to flowmarks
Feb 13 01:52:47 (none) daemon.info flowman[10107]: (INFO): subscribed to policy.decisions
Feb 13 01:52:47 (none) daemon.info flowman[10107]: (INFO): flowman_init: connected and subscribed
Feb 13 01:52:47 (none) daemon.info flowman[10107]: (INFO): starting main loop.
Feb 13 01:52:47 (none) daemon.info flowman[10107]: (INFO): subscribed to connection.events
Feb 13 01:52:47 (none) daemon.notice cape[10114]: (NOTICE): node exceptions key: policydb:except:nodes
Feb 13 01:52:47 (none) user.warn jigglyp0f[9914]: bad line: .
Feb 13 01:52:48 (none) user.info syslog: (INFO): Running as daemon
Feb 13 01:52:49 (none) user.info syslog: (INFO): Listening on 127.0.0.1:9000
Feb 13 01:52:49 (none) local0.notice drflocs[10125]: (NOTICE): Local IPv4 Host: 192.168.**.**
Feb 13 01:52:49 (none) local0.notice drflocs[10125]: (NOTICE): Local IPv4 Netmask: 255.255.255.0
Feb 13 01:52:49 (none) local0.notice drflocs[10125]: (NOTICE): Local IPv4 Network: 192.168.**.**
Feb 13 01:52:49 (none) local0.notice drflocs[10125]: (NOTICE): Local IPv6 Host: fe80::76da:38ff:fe61:2970
Feb 13 01:52:49 (none) local0.notice drflocs[10125]: (NOTICE): Local IPv6 Netmask: ffff:ffff:ffff:ffff::
Feb 13 01:52:49 (none) local0.notice drflocs[10125]: (NOTICE): Local IPv6 Network: fe80::
Feb 13 01:52:51 (none) local0.notice drflocs[10125]: (NOTICE): unable to resolve sfe family FC: -12
Feb 13 01:52:51 (none) local0.notice drflocs[10125]: (NOTICE): SFE offload not available
Feb 13 01:52:51 (none) local0.notice drflocs[10125]: (NOTICE): NSS offload enabled
Feb 13 01:52:51 (none) local0.notice drflocs[10125]: (NOTICE): using channel classifications for classifications
Feb 13 01:52:51 (none) local0.notice drflocs[10125]: (NOTICE): using channel connection.events for connection events
Feb 13 01:52:51 (none) local0.notice drflocs[10125]: (NOTICE): using channel nodes.ipaddr.drflocs for mac-to-ip associations
Feb 13 01:52:51 (none) local0.notice drflocs[10125]: (NOTICE): feature discovery is disabled
Feb 13 02:56:13 (none) daemon.info hostapd: ath0: STA 00:00:fa:b5:97:fa IEEE 802.11: associated
Feb 13 02:58:21 (none) daemon.info hostapd: ath0: STA c0:ee:fb:26:12:ce IEEE 802.11: disassociated
Feb 13 02:58:21 (none) daemon.info hostapd: athi5: STA c0:ee:fb:26:12:ce IEEE 802.11: associated
Feb 13 04:02:35 (none) user.err overlord[10091]: Error getting node for flow 37.
Feb 13 05:14:37 (none) user.err overlord[10091]: Error getting node for flow 66.
Feb 13 05:38:51 (none) user.err overlord[10091]: Error getting node for flow 77.
Feb 13 05:53:51 (none) user.err overlord[10091]: Error getting node for flow 83.
Feb 13 06:56:16 (none) user.err overlord[10091]: Error getting node for flow 104.
Feb 13 08:45:01 (none) user.err overlord[10091]: Error getting node for flow 157.
Feb 13 09:15:29 (none) user.err overlord[10091]: Error getting node for flow 168.
Feb 13 09:31:01 (none) user.err overlord[10091]: Error getting node for flow 177.
Feb 13 10:32:38 (none) user.err overlord[10091]: Error getting node for flow 199.
Feb 13 10:36:55 (none) user.err overlord[10091]: Error getting node for flow 208.
Feb 14 00:57:58 (

Edited by radicaldoc - 16 Feb 2017 at 6:31pm

Ok, let's see here what we might be able to help with.

The PC and VU+ Solo 2 are wired so we can discount them from wireless consideration here.

Your wireless device Specs as I can discover are:
OnePlus One - 2.4G 802.11 b, g, n
Samsung Galaxy Tab 3 - 2.4G 802.11 a, b, g, n
DOOGEE HOMTOM HT7 - 2.4G 802.11 b, g, n


Knowing those specs, _and_ your saying there is no range/coverage in your home, I'm going to go out on a limb here and guess since you just bought a shiny new 5G capable wireless router, ASRock G10, that you've gone and assigned the above three wireless devices to the 5G band. Correct?

radicaldoc wrote: sorry no i have the homtom 7 and samsung tab 3 on  2.g and the Oneplus one on 5g although i have read somewhere these will all operate on the 2.4g because the 2.4g will pull the rest down yes?? I have now put everything on 2.4g..

Neither three of the wireless devices you list have 5Ghz capability. That I could discover anyways.

But what is more important is the 5Ghz band, while faster than 2.4Ghz, also does not penetrate physical objects as walls too well.

Knowing your previously installed TP Link was 2.4Ghz only and you had "great' RX and TX throughout the house yet with the G-10 you suffer is why I've asked you to place your current(!) Wi-Fi devices onto the 2.4Ghz band.




Please, let them ride on the 2.4Ghz band for a day and reply back if you have better coverage and throughput there.

well it has been a few days now with no significant increase in signal yes it is very marginally better but not  a lot at all;;

I wasn't going to chime in here as my experience with routers and their firmware is very limited but it occurred to me that I may be able to shed some light on what is happening here.