|
|
|
Yep, got "the badge" here in Wgtn region now!
Seems to have doubled the speed and made my life so much better all round![]()
Anyway, good going Orcon guys.
My wife's comp couldn't access google.com (gmail) today until I unticked IPv6 in adapter settings. Didn't seem to have any problems with other sites and my comp is fine.
No idea why IPv6 is problematic on this one machine. Guess I just leave IPv6 disabled.
The adapter is an onboard one in a Dell Optiplex 780.
The error reported is:- ERR_QUIC_PROTOCOL_ERROR
Same problem with Chrome and Edge. The problem page seems to be https://accounts.google.com/
Yeah, I'm seeing slow response (intermittently) from Google since the IPV6 went live. Haven't really investigated too much; but the issue does seem to be device-agnostic (i.e. all my devices occasionally have slowdowns on Google traffic).
@Sounddude - any known issue in this area?
Go here for a fix for Chrome https://appuals.com/fix-google-chrome-error-err_quic_protocol_error/
It involves disabling the 'experimental' QUIC protocol.
Not something we have come across before?
Can you guys confirm what modem you have and the firmware version?
Manufacturer:
NetComm Wireless
Product Class:
NF4V
Build Timestamp:
201408221004
Software Version:
GURNV5.OT132A-8-NC.Orcon-R5B032.EN
Mine is same as James above.
MadEngineer: What happens if you run a nslookup IPv6.google.com from command prompt?
Technically, this is from a BASH shell, rather than a command-prompt; but I don't think that's going to make a huge difference:
james:[~]$ nslookup
> ipv6.google.com
Server: 121.98.0.1
Address: 121.98.0.1#53
Non-authoritative answer:
ipv6.google.com canonical name = ipv6.l.google.com.
More interestingly, "ipv6.l.google.com" doesn't resolve:
> ipv6.l.google.com.
Server: 121.98.0.1
Address: 121.98.0.1#53
Non-authoritative answer:
*** Can't find ipv6.l.google.com.: No answer
I've got the following set in my router under Advanced Setup/DNS: "Select DNS server from available WAN interface"; and I'm pushing my router's IP address for DNS via DHCP. Also "DNS Proxy" is turned off.
^ based on "Server: 121.98.0.1" your dhcp server is pushing orcon's dns server, not itself (assuming that machine is on dhcp not static)
also, for nslookup under bash you'll need to add -query=AAAA or set query=AAAA
MadEngineer: based on "Server: 121.98.0.1" your dhcp server is pushing orcon's dns server, not itself (assuming that machine is on dhcp not static)
I can assure you it is configured to push itself; I just checked. However, as I also previously stated, "DNS Proxy" is disabled; which presumably is overriding the DHCP DNS-setting in the router. That's my assumption - I don't have source code for the firmware, so I can't check! :-)
MadEngineer: also, for nslookup under bash you'll need to add -query=AAAA or set query=AAAA
Wow; long day at work today obviously - I should have thought of that myself.
james:[~]$ nslookup
> set type=aaaa
> ipv6.l.google.com
Server: 121.98.0.1
Address: 121.98.0.1#53
Non-authoritative answer:
ipv6.l.google.com has AAAA address 2404:6800:4006:808::200e
Better. Also, this:
james:[~]$ ping6 ipv6.google.com
PING6(56=40+8+8 bytes) 2404:4404:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX --> 2404:6800:4006:808::200e
16 bytes from 2404:6800:4006:808::200e, icmp_seq=0 hlim=52 time=36.471 ms
16 bytes from 2404:6800:4006:808::200e, icmp_seq=1 hlim=52 time=46.495 ms
16 bytes from 2404:6800:4006:808::200e, icmp_seq=2 hlim=52 time=40.209 ms
|
|
|