Posted: Wed Sep 15, 2021 0:30 Post subject: problem with chromebook web surfing
my son brought home his school provided chromebook - it connects to the ddwrt router via wifi and draws an ip address but he can't get to the internet - any ideas why this is happening? i have about 17 devices that connect and web surf just fine. of course, the chromebook is locked down by the school.
Joined: 16 Nov 2015 Posts: 6435 Location: UK, London, just across the river..
Posted: Wed Sep 15, 2021 7:36 Post subject:
it could be a DNS related, as those cromebooks may have a baked DNS inside so they try to use their own DNS, but may be you have forced DNS on your router.
give a static IP to the cromebook and try to add those lines to firewall:
iptables -t nat -I PREROUTING -i br0 -s 192.168.1.103 -p udp --dport 53 -j DNAT --to 8.8.8.8
iptables -t nat -I PREROUTING -i br0 -s 192.168.1.103 -p tcp --dport 53 -j DNAT --to 8.8.8.8
replace 192.168.1.103 with its IP _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55779 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Last edited by Alozaros on Wed Sep 15, 2021 10:58; edited 1 time in total
I have a Poin2 Chromebook with a MediaTek CPU and I had problems connecting to the Wifi from my router/APs running dd-wrt. At one point I concluded it was due to the having the wireless protection mode set as RTS/CTS and RTS Threshold enabled. My workaround was to have RTS threshold disabled. However, in recent builds I have been able to set RTS threshold to 784. I'm running 47225 on my main R7800 and 46750 on my secondary AP an Archer C7 V2.
If you want to check network configuration the chrome://network/ pages might help you.
But are you running a captive portal on your wifi? _________________ An old man said, “Erasers are made for those who make mistakes.” A youth replied, “Erasers are made for those who are willing to correct their mistakes!” Attitude matters! ~ Anonymous
----------
“You are always a student, never a master. You have to keep moving forward.” ~ Conrad Hall
----------
“Life is about moving on, accepting changes and looking forward to what makes you stronger and more complete.” ~ Anonymous
Then explain to me why a captive portal bug would affect you... ^_^ _________________ An old man said, “Erasers are made for those who make mistakes.” A youth replied, “Erasers are made for those who are willing to correct their mistakes!” Attitude matters! ~ Anonymous
----------
“You are always a student, never a master. You have to keep moving forward.” ~ Conrad Hall
----------
“Life is about moving on, accepting changes and looking forward to what makes you stronger and more complete.” ~ Anonymous
Thanks for the clarification. So it seems the solution is to roll it back to v86 and not anything else unless the bug was fixed since April / May... _________________ An old man said, “Erasers are made for those who make mistakes.” A youth replied, “Erasers are made for those who are willing to correct their mistakes!” Attitude matters! ~ Anonymous
----------
“You are always a student, never a master. You have to keep moving forward.” ~ Conrad Hall
----------
“Life is about moving on, accepting changes and looking forward to what makes you stronger and more complete.” ~ Anonymous
