G10 Router is worst i have ever bought
Printed From: ASRock.com
Category: Media&User's Review
Forum Name: Networking Products
Forum Description: ASRock Networking Products
URL: https://forum.asrock.com/forum_posts.asp?TID=4417
Printed Date: 28 Apr 2024 at 11:41am
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: G10 Router is worst i have ever bought
Posted By: radicaldoc
Subject: G10 Router is worst i have ever bought
Date Posted: 13 Feb 2017 at 5:49pm
|
I have to say this router is the worst router i have ever bought. I bought it new on the 3rd of January . And my network has NEVER Been so poor. i upgraded from my trusty TP-LINK TP-WR1043ND because i wanted faster speeds on my network instead i got nothing like and half the coverage of my old one My TP-LINK covered my entire house and even a little drifting on to the back patio so we could sit out with it.. After reading all the gumph about how good this was and great coverage it was the all singing all dancing Router I bought it instead of TP-LINK newer one but what a total waste of money the G10 won't even cover half the house and forget any of it leaking out onto the patio. Sorry but this has been the biggest waste of money i have spent i am a pensioner so what ever i bought i was stuck with it as i don't have the money to change it out. So it looks like i will be putting my old one back in boxing this up and hoping someone will buy it off me.... Appalling bit of kit..  ------------- GA-X58A-UD3R (Rev 2) M/B with i7 950 @ 3.07GHz 24.0GB Triple-Channel DDR3 @ 531MHz EVGA GTX 780 SC ACX W/BACKPLATE COOLER MASTER Real Power Pro1000 RS-A00-EMBA 1000W ATX12V G10 Router |
Replies:
Posted By: wardog
Date Posted: 14 Feb 2017 at 12:34am
|
" rel="nofollow - Does the Admin panel have a Power Setting that may be at 50% from the factory? I'll have to read the manual. |
Posted By: parsec
Date Posted: 14 Feb 2017 at 9:33am
|
First complaint of this type about the G10 Router that we've ever seen in this forum. ------------- http://valid.x86.fr/48rujh" rel="nofollow"> 
|
Posted By: wardog
Date Posted: 14 Feb 2017 at 1:06pm
|
radicaldoc, if it's like the other AC wireless routers I have experience with I must ask a couple questions/make a couple observations seeings your TP-WR1043ND is a 300 N. 1. Keep your non-AC devices on one band and your AC capable ones on the other. The slowest device on each band will match it's particular transmit speed onto all other devices on that band. Not sure I explained that to come across ....... 2. After reading the Manual you do indeed have 2 power output adjustments in the Admin panel. One for the 2.4G band and one for the 5G band. Check that both are starting at 100% and then if you feel like it lower it until you have coverage only where needed. That will keep your "signal' from being broadcast all over the neighborhood. Keeping kiddies, phreaks, and freeloaders off your connection/network Admin panel > Wireless > Wireless-2.4G > TX Power Adjustment Admin panel > Wireless > Wireless-5G > TX Power Adjustment |
Posted By: wardog
Date Posted: 14 Feb 2017 at 1:17pm
Allow me to take a second go at explaining that better  The slowest rated device on each band, that will be the speed that ALL devices on that band will RX and TX. There! Much better if I dare say so  |
wardog wrote:Posted By: radicaldoc
Date Posted: 14 Feb 2017 at 5:58pm
|
No it doesn't and i haven't come across anything like that on this or any other router.. :) Although i am no expert ------------- GA-X58A-UD3R (Rev 2) M/B with i7 950 @ 3.07GHz 24.0GB Triple-Channel DDR3 @ 531MHz EVGA GTX 780 SC ACX W/BACKPLATE COOLER MASTER Real Power Pro1000 RS-A00-EMBA 1000W ATX12V G10 Router |
Posted By: radicaldoc
Date Posted: 14 Feb 2017 at 6:01pm
I have no other wireless router in the system or in my house that was my old one i don't use it since i bought this to replace it..thanks. it just has NO coverage only half the TP-LINK ------------- GA-X58A-UD3R (Rev 2) M/B with i7 950 @ 3.07GHz 24.0GB Triple-Channel DDR3 @ 531MHz EVGA GTX 780 SC ACX W/BACKPLATE COOLER MASTER Real Power Pro1000 RS-A00-EMBA 1000W ATX12V G10 Router |
Posted By: wardog
Date Posted: 14 Feb 2017 at 11:05pm
" rel="nofollow -
If that was "No, it doesn't have TX Power Adjustment's, I can assure you it does. Do you know how to enter the routers Administration panel/applet?? |
Posted By: radicaldoc
Date Posted: 16 Feb 2017 at 1:38am
I know how to go into normal administration with the router status and firmware update is there another one?? as i can see nothing in there to change Aaahh i have found it in wireless and TX is set at 100% ------------- GA-X58A-UD3R (Rev 2) M/B with i7 950 @ 3.07GHz 24.0GB Triple-Channel DDR3 @ 531MHz EVGA GTX 780 SC ACX W/BACKPLATE COOLER MASTER Real Power Pro1000 RS-A00-EMBA 1000W ATX12V G10 Router |
Posted By: wardog
Date Posted: 16 Feb 2017 at 3:56am
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. |
Posted By: radicaldoc
Date Posted: 16 Feb 2017 at 6:17pm
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 ( ------------- GA-X58A-UD3R (Rev 2) M/B with i7 950 @ 3.07GHz 24.0GB Triple-Channel DDR3 @ 531MHz EVGA GTX 780 SC ACX W/BACKPLATE COOLER MASTER Real Power Pro1000 RS-A00-EMBA 1000W ATX12V G10 Router |
Posted By: radicaldoc
Date Posted: 16 Feb 2017 at 6:33pm
|
rest of it Feb 14 00:57:58 (none) user.err overlord[10091]: Error getting node for flow 702. Feb 14 01:33:57 (none) user.err overlord[10091]: Error getting node for flow 713. Feb 14 01:52:01 (none) user.err overlord[10091]: Error getting node for flow 722. Feb 14 02:07:01 (none) user.err overlord[10091]: Error getting node for flow 727. Feb 14 02:09:58 (none) user.err overlord[10091]: Error getting node for flow 730. Feb 14 02:22:02 (none) user.err overlord[10091]: Error getting node for flow 737. Feb 14 03:58:01 (none) user.err overlord[10091]: Error getting node for flow 770. Feb 14 04:34:02 (none) user.err overlord[10091]: Error getting node for flow 782. Feb 14 04:52:06 (none) user.err overlord[10091]: Error getting node for flow 794. Feb 14 05:10:03 (none) user.err overlord[10091]: Error getting node for flow 800. Feb 14 06:58:05 (none) user.err overlord[10091]: Error getting node for flow 836. Feb 14 07:13:08 (none) user.err overlord[10091]: Error getting node for flow 842. Feb 14 09:35:59 (none) user.err overlord[10091]: Error getting node for flow 898. Feb 14 12:52:03 (none) user.err overlord[10091]: Error getting node for flow 1030. Feb 14 13:42:09 (none) user.err overlord[10091]: Error getting node for flow 1057. Feb 14 14:55:42 (none) user.err overlord[10091]: Error getting node for flow 1091. Feb 14 15:22:14 (none) user.err overlord[10091]: Error getting node for flow 1115. Feb 14 16:03:02 (none) user.err overlord[10091]: Error getting node for flow 1150. Feb 14 19:05:16 (none) user.err overlord[10091]: Error getting node for flow 1277. Feb 14 19:39:12 (none) user.err overlord[10091]: Error getting node for flow 1309. Feb 14 20:24:14 (none) user.err overlord[10091]: Error getting node for flow 1346. Feb 14 20:39:13 (none) user.err overlord[10091]: Error getting node for flow 1366. Feb 14 20:58:29 (none) user.err overlord[10091]: Error getting node for flow 1385. Feb 14 21:21:40 (none) daemon.info hostapd: ath0: STA 00:00:fa:b5:97:fa IEEE 802.11: disassociated Feb 14 21:21:44 (none) daemon.info hostapd: ath0: STA 00:00:fa:b5:97:fa IEEE 802.11: associated Feb 14 21:37:18 (none) user.err overlord[10091]: Error getting node for flow 1419. Feb 14 21:40:47 (none) user.err overlord[10091]: Error getting node for flow 1425. Feb 14 22:01:14 (none) daemon.info hostapd: ath0: STA 30:19:66:eb:af:e4 IEEE 802.11: associated Feb 14 22:26:49 (none) user.err overlord[10091]: Error getting node for flow 1458. Feb 14 22:41:48 (none) user.err overlord[10091]: Error getting node for flow 1466. Feb 14 23:02:00 (none) user.err overlord[10091]: Error getting node for flow 1480. Feb 14 23:36:01 (none) user.err overlord[10091]: Error getting node for flow 1514. Feb 14 23:49:29 (none) user.err overlord[10091]: Error getting node for flow 1528. Feb 15 00:05:39 (none) user.err overlord[10091]: Error getting node for flow 1548. Feb 15 01:07:49 (none) user.err overlord[10091]: Error getting node for flow 1627. Feb 15 01:41:44 (none) user.err overlord[10091]: Error getting node for flow 1654. Feb 15 02:08:54 (none) user.err overlord[10091]: Error getting node for flow 1670. Feb 15 02:36:56 (none) user.err overlord[10091]: Error getting node for flow 1688. Feb 15 02:44:31 (none) user.err overlord[10091]: Error getting node for flow 1695. Feb 15 02:45:55 (none) user.err overlord[10091]: Error getting node for flow 1698. Feb 15 02:45:55 (none) user.err overlord[10091]: Error getting node for flow 1699. Feb 15 03:21:54 (none) user.err overlord[10091]: Error getting node for flow 1723. Feb 15 03:53:35 (none) user.err overlord[10091]: Error getting node for flow 1745. Feb 15 03:57:55 (none) user.err overlord[10091]: Error getting node for flow 1749. Feb 15 04:20:34 (none) user.err overlord[10091]: Error getting node for flow 1765. Feb 15 04:50:57 (none) user.err overlord[10091]: Error getting node for flow 1780. Feb 15 05:08:35 (none) user.err overlord[10091]: Error getting node for flow 1791. Feb 15 05:09:56 (none) user.err overlord[10091]: Error getting node for flow 1794. Feb 15 05:13:58 (none) user.err overlord[10091]: Error getting node for flow 1797. Feb 15 05:53:37 (none) user.err overlord[10091]: Error getting node for flow 1820. Feb 15 05:53:37 (none) user.err overlord[10091]: Error getting node for flow 1821. Feb 15 06:09:17 (none) user.err overlord[10091]: Error getting node for flow 1830. Feb 15 06:21:58 (none) user.err overlord[10091]: Error getting node for flow 1838. Feb 15 06:24:17 (none) user.err overlord[10091]: Error getting node for flow 1841. Feb 15 06:54:18 (none) user.err overlord[10091]: Error getting node for flow 1856. Feb 15 06:57:59 (none) user.err overlord[10091]: Error getting node for flow 1862. Feb 15 07:33:58 (none) user.err overlord[10091]: Error getting node for flow 1891. Feb 15 07:51:39 (none) user.err overlord[10091]: Error getting node for flow 1898. Feb 15 08:21:40 (none) user.err overlord[10091]: Error getting node for flow 1918. Feb 15 08:35:08 (none) user.err overlord[10091]: Error getting node for flow 1927. Feb 15 08:36:40 (none) user.err overlord[10091]: Error getting node for flow 1929. Feb 15 09:05:46 (none) daemon.info hostapd: athi5: STA c0:ee:fb:26:12:ce IEEE 802.11: disassociated Feb 15 09:06:31 (none) daemon.info hostapd: ath0: STA 00:00:fa:b5:97:fa IEEE 802.11: disassociated Feb 15 10:33:46 (none) user.err overlord[10091]: Error getting node for flow 1956. Feb 15 17:49:41 (none) daemon.info hostapd: ath0: STA 00:00:fa:b5:97:fa IEEE 802.11: associated Feb 15 18:01:24 (none) daemon.info hostapd: athi5: STA c0:ee:fb:26:12:ce IEEE 802.11: associated Feb 15 18:29:00 (none) user.err overlord[10091]: Error getting node for flow 2024. Feb 15 18:40:24 (none) user.err overlord[10091]: Error getting node for flow 2035. Feb 15 23:31:11 (none) user.err overlord[10091]: Error getting node for flow 2302. Feb 15 23:50:04 (none) user.err overlord[10091]: Error getting node for flow 2318. Feb 16 00:23:52 (none) user.err overlord[10091]: Error getting node for flow 2336. Feb 16 00:38:38 (none) user.err overlord[10091]: Error getting node for flow 2351. Feb 16 00:52:45 (none) user.err overlord[10091]: Error getting node for flow 2359. Feb 16 01:40:36 (none) user.err overlord[10091]: Error getting node for flow 2387. Feb 16 02:01:13 (none) user.err overlord[10091]: Error getting node for flow 2399. Feb 16 02:06:59 (none) user.err overlord[10091]: Error getting node for flow 2404. Feb 16 02:39:37 (none) user.err overlord[10091]: Error getting node for flow 2429. Feb 16 03:05:19 (none) user.err overlord[10091]: Error getting node for flow 2448. Feb 16 03:16:48 (none) user.err overlord[10091]: Error getting node for flow 2455. Feb 16 03:35:20 (none) user.err overlord[10091]: Error getting node for flow 2466. Feb 16 03:40:57 (none) user.err overlord[10091]: Error getting node for flow 2472. Feb 16 04:22:49 (none) user.err overlord[10091]: Error getting node for flow 2499. Feb 16 04:52:48 (none) user.err overlord[10091]: Error getting node for flow 2520. Feb 16 05:07:49 (none) user.err overlord[10091]: Error getting node for flow 2526. Feb 16 05:24:16 (none) user.err overlord[10091]: Error getting node for flow 2534. Feb 16 06:56:17 (none) user.err overlord[10091]: Error getting node for flow 2587. Feb 16 07:20:53 (none) user.err overlord[10091]: Error getting node for flow 2605. Feb 16 08:28:22 (none) user.err overlord[10091]: Error getting node for flow 2648. Feb 16 08:43:23 (none) user.err overlord[10091]: Error getting node for flow 2660. Feb 16 08:58:21 (none) user.err overlord[10091]: Error getting node for flow 2667. Feb 16 09:29:31 (none) user.err overlord[10091]: Error getting node for flow 2683. Feb 16 10:07:18 (none) user.err overlord[10091]: Error getting node for flow 2709. Feb 16 10:08:08 (none) daemon.info hostapd: ath0: STA 30:19:66:eb:af:e4 IEEE 802.11: disassociated Feb 16 10:09:35 (none) daemon.info hostapd: ath0: STA 30:19:66:eb:af:e4 IEEE 802.11: associated Feb 16 10:23:22 (none) daemon.info hostapd: ath0: STA 30:19:66:eb:af:e4 IEEE 802.11: disassociated Feb 16 11:14:45 (none) user.err overlord[10091]: Error getting node for flow 2742. Feb 16 11:14:45 (none) user.err overlord[10091]: Error getting node for flow 2743. ------------- GA-X58A-UD3R (Rev 2) M/B with i7 950 @ 3.07GHz 24.0GB Triple-Channel DDR3 @ 531MHz EVGA GTX 780 SC ACX W/BACKPLATE COOLER MASTER Real Power Pro1000 RS-A00-EMBA 1000W ATX12V G10 Router |
Posted By: wardog
Date Posted: 16 Feb 2017 at 9:35pm
|
" rel="nofollow - 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? |
Posted By: radicaldoc
Date Posted: 17 Feb 2017 at 3:21am
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.. edited by wardog to correct quotation ------------- GA-X58A-UD3R (Rev 2) M/B with i7 950 @ 3.07GHz 24.0GB Triple-Channel DDR3 @ 531MHz EVGA GTX 780 SC ACX W/BACKPLATE COOLER MASTER Real Power Pro1000 RS-A00-EMBA 1000W ATX12V G10 Router |
Posted By: wardog
Date Posted: 17 Feb 2017 at 6:03am
" rel="nofollow -
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. |
Posted By: wardog
Date Posted: 17 Feb 2017 at 6:20am
" rel="nofollow -
I must have been looped last night, which I guarantee I was not, to have fallen dupe to not believing ANY OnePlus phone didn't have 802.11 AC/5Ghz. I must have been typing at the keyboard exhausted. Your OnePlus One does indeed enjoy 5Ghz.. Still, for here and now testing, let's leave it on the 2.4Ghz band for a day. Without my physical presence there in your home, I have to go by what you have spoken so far. I feel/think/believe that where your G-10 is currently placed, the poorly penetrating 5Ghz band is just a wall too far for it to offer any performance. Actually, I feel where your 5Ghz reception is "bad' in your house is too much obstruction and may be re-transmitting, further hobbling it at the far reaches of your home. Post back in a day with what you discover. |
Posted By: radicaldoc
Date Posted: 22 Feb 2017 at 8:30pm
|
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;; ------------- GA-X58A-UD3R (Rev 2) M/B with i7 950 @ 3.07GHz 24.0GB Triple-Channel DDR3 @ 531MHz EVGA GTX 780 SC ACX W/BACKPLATE COOLER MASTER Real Power Pro1000 RS-A00-EMBA 1000W ATX12V G10 Router |
Posted By: wardog
Date Posted: 22 Feb 2017 at 8:45pm
|
" rel="nofollow - Hmmmmm What is your home constructed of? How many walls does the signal travel through? Have you thought of a repeater? |
Posted By: Xaltar
Date Posted: 22 Feb 2017 at 11:21pm
|
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. TPLink tend to be tuned for tolerance and ease of use. The most common issues I experience with them are poor latency, dropped packets and unreliability. Typically resetting the router a few times a day solves most of these issues, that and changing the channel to less used channels in your area to avoid signal contamination. ASRock's G10 is aimed at gamers, gamers worst enemy is latency, packet loss and corruption. It would stand to reason that the ASRock router would be tuned with much lower tolerance to dropped packets and data corruption as a result. These settings would by extension decrease signal range, significantly given how aggressively I suspect the firmware rejects weak connections. It also limits contamination to an extent by rejecting weaker signals off the bat. I can't offer any fixes as I am not familiar with the G10's firmware but this may be of some help locating the issue, if these tolerances can be altered it should increase range the more tolerance you allow. Basically higher tolerance = greater range at the cost of lower reliability Lower tolerance = decreased range but lower latency + greater reliability I hope this is of some help. I am no expert and could be wrong but this makes sense to me. ------------- 
|
Posted By: radicaldoc
Date Posted: 03 Mar 2017 at 1:52am
thanks bud i will look into it and see if it can be tweeked... I have decided i am going to persevere with it i do genrally like it i am no expert but it does seem to be a nice bit of kit.... ------------- GA-X58A-UD3R (Rev 2) M/B with i7 950 @ 3.07GHz 24.0GB Triple-Channel DDR3 @ 531MHz EVGA GTX 780 SC ACX W/BACKPLATE COOLER MASTER Real Power Pro1000 RS-A00-EMBA 1000W ATX12V G10 Router |
Posted By: radicaldoc
Date Posted: 03 Mar 2017 at 1:54am
|
We like in an old cortijo out in the middle of no where it's built of rock flint and mud for the main part signal has one thick wall to go through and a thin one
------------- GA-X58A-UD3R (Rev 2) M/B with i7 950 @ 3.07GHz 24.0GB Triple-Channel DDR3 @ 531MHz EVGA GTX 780 SC ACX W/BACKPLATE COOLER MASTER Real Power Pro1000 RS-A00-EMBA 1000W ATX12V G10 Router |
Posted By: radicaldoc
Date Posted: 03 Mar 2017 at 2:46am
|
" rel="nofollow - Can i also add does anyone here have or use one of these routers?? as i have just started messing with the H2R Router you get with it works pretty well with EZCAST but my question is when i am using this and i have working fine you watch pretty much most things through i like films on my pad etc, and things like Filmon etc... but can i watch stuff from my key in the USB sockets through the media server built in as well it's a bit confusing for me although i did get everything working with each other.... just don't know if i can watch stuff on that through the H2R as well........ thanks guys ------------- GA-X58A-UD3R (Rev 2) M/B with i7 950 @ 3.07GHz 24.0GB Triple-Channel DDR3 @ 531MHz EVGA GTX 780 SC ACX W/BACKPLATE COOLER MASTER Real Power Pro1000 RS-A00-EMBA 1000W ATX12V G10 Router |