Hello. I can't ping the openwrt.org site in the diagnostics menu. My question is why not and how can i fix it?
here is some info, when i tried finding the reason. Can anyone of you see anything wierd?
? But most importantly how to fix it. 
Thanks!
I followed this setup, but it just don't seem to work this time.
What does this mean?
daemon.warn odhcpd[1352]: No default route present, overriding ra_lifetime!
It went from a working set up to not working... then i updated openwrt.
Now i need to get a connection, then fix the rest. Might have been connection issues... slow 4g...
What are your thought? You have the knowledge! I need some quick support if someone can help.. i'm using some temporary crap solution right now to even get internet!
I'm contemplating buying a new router, also. This is a zbt router. It's an unstable model with openwrt.
It appears that you have a connection. Can you ping a well-known site by its numeric IP like 8.8.4.4 or 1.1.1.1 ?
If that works there is likely a DNS issue. Check that a DNS server has been installed in /tmp/resolv.conf.d/resolv.conf.
If you can't ping the Internet by number, check if you can ping the gateway IP that the modem installed. This should be the first router on the other side of your link. If you can ping into the ISP but not all the way to the Internet they are probably blocking your subscription.
Hi. Thanks, yes this is some DNS error or something... I also got these errors..
Trying to bring up and down the router, please give me a quick solution like some steps.. I got important stuff to fix i really need internet. Thanks allot! Peace
Here is some more info:
IPv4 Neighbours
IP address MAC address Interface
192.168.1.**
mac address
Active IPv4 Routes
Network Target Gateway Metric Table Protocol
4G_4 0.0.0.0/0 10.1**.1**.12* 0 main
4G_4 10.1**.1**.12*/28 - 0 main
lan 192.168.1.0/24 - 0 main
Active IPv4 Rules
Priority Rule
0 from all lookup local
32766 from all lookup main
32767 from all lookup default
IPv6 Neighbours
IP address MAC address Interface
No entries available
Active IPv6 Routes
and...
Mon Oct 9 22:37:46 2023 daemon.warn odhcpd[1352]: No default route present, overriding ra_lifetime!
Mon Oct 9 22:37:46 2023 kern.info kernel: [ 540.058541] br-lan: port 1(eth0.1) entered disabled state
Mon Oct 9 22:37:46 2023 daemon.err odhcpd[1352]: Failed to send to ff02::1%lan@br-lan (Network unreachable)
Mon Oct 9 22:37:46 2023 kern.info kernel: [ 540.090967] device eth0.1 left promiscuous mode
Mon Oct 9 22:37:46 2023 kern.info kernel: [ 540.095633] device eth0 left promiscuous mode
Mon Oct 9 22:37:46 2023 kern.info kernel: [ 540.100332] br-lan: port 1(eth0.1) entered disabled state
Mon Oct 9 22:37:46 2023 daemon.notice netifd: Interface 'lan' is disabled
Mon Oct 9 22:37:46 2023 daemon.notice netifd: bridge 'br-lan' link is down
Mon Oct 9 22:37:46 2023 daemon.notice netifd: Interface 'lan' has link connectivity loss
Mon Oct 9 22:37:46 2023 daemon.notice netifd: VLAN 'eth0.1' link is down
Mon Oct 9 22:37:46 2023 daemon.notice netifd: Network device 'eth0' link is down
Mon Oct 9 22:37:46 2023 kern.info kernel: [ 540.346518] 8021q: adding VLAN 0 to HW filter on device eth0
Mon Oct 9 22:37:46 2023 kern.info kernel: [ 540.372905] br-lan: port 1(eth0.1) entered blocking state
Mon Oct 9 22:37:46 2023 kern.info kernel: [ 540.378555] br-lan: port 1(eth0.1) entered disabled state
Mon Oct 9 22:37:46 2023 kern.info kernel: [ 540.384483] device eth0.1 entered promiscuous mode
Mon Oct 9 22:37:46 2023 kern.info kernel: [ 540.389464] device eth0 entered promiscuous mode
Mon Oct 9 22:37:46 2023 kern.info kernel: [ 540.451341] br-lan: port 1(eth0.1) entered blocking state
Mon Oct 9 22:37:46 2023 kern.info kernel: [ 540.456896] br-lan: port 1(eth0.1) entered forwarding state
Mon Oct 9 22:37:46 2023 daemon.notice netifd: Interface 'lan' is enabled
Mon Oct 9 22:37:46 2023 daemon.notice netifd: Interface 'lan' is setting up now
Mon Oct 9 22:37:46 2023 daemon.notice netifd: Interface 'lan' is now up
Mon Oct 9 22:37:46 2023 daemon.notice netifd: Network device 'eth0' link is up
Mon Oct 9 22:37:46 2023 daemon.notice netifd: VLAN 'eth0.1' link is up
Mon Oct 9 22:37:46 2023 daemon.notice netifd: bridge 'br-lan' link is up
Mon Oct 9 22:37:46 2023 daemon.notice netifd: Interface 'lan' has link connectivity
Mon Oct 9 22:37:47 2023 daemon.info dnsmasq[1]: read /etc/hosts - 12 names
Mon Oct 9 22:37:47 2023 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 4 names
Mon Oct 9 22:37:47 2023 daemon.info dnsmasq[1]: read /tmp/hosts/odhcpd - 0 names
Mon Oct 9 22:37:47 2023 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Mon Oct 9 22:37:47 2023 user.notice firewall: Reloading firewall due to ifup of lan (br-lan)
Mon Oct 9 22:37:51 2023 daemon.info dnsmasq[1]: read /etc/hosts - 12 names
Mon Oct 9 22:37:51 2023 daemon.info dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 4 names
Mon Oct 9 22:37:51 2023 daemon.info dnsmasq[1]: read /tmp/hosts/odhcpd - 0 names
Mon Oct 9 22:37:51 2023 daemon.info dnsmasq-dhcp[1]: read /etc/ethers - 0 addresses
Mon Oct 9 22:38:04 2023 daemon.warn odhcpd[1352]: No default route present, overriding ra_lifetime!
Mon Oct 9 22:38:20 2023 daemon.warn odhcpd[1352]: No default route present, overriding ra_lifetime!
Mon Oct 9 22:38:36 2023 daemon.warn odhcpd[1352]: No default route present, overriding ra_lifetime!
What can i do step-by-step? Thanks!
edit: About the pinging to 1.1.1.1. Im gonna check i need to unplug my temporary setup and try... so brb...
edit2: No, i could not..
PING 1.1.1.1 (1.1.1.1): 56 data bytes
--- 1.1.1.1 ping statistics ---
5 packets transmitted, 0 packets received, 100% packet loss
and
traceroute to 1.1.1.1 (1.1.1.1), 20 hops max, 46 byte packets
1 *
2 *
3 *
4 10..36. 65.280 ms !A (some internal ip. )
It takes a while for me to test stuff, so yeah... If someone knows the answer to this issue, please help out.
It worked a few days ago, then just stopped... Might have been a bad 4g connection, and then i flashed a new firmware unnecessary instead of waiting it out.. And i spent ages setting that up and cant remember what i did now.
Technology. It drives people mad.. oh well.. Gotta get this working later on. Thanks for the support. I don't understand why its not working.
A packet going several hops into the ISP then dying really suggests that they are internally refusing to connect you to the Internet due to a subscription issue, or you're using an APN that is not valid with your subscription.
Try the SIM card in a standalone device like a smartphone and confirm that it can reach the Internet.
You don't have to redact RFC1918 private IPs like those that start with 10 as no one on the Internet can reach them anyway.
HI. Thanks it works with a phone, but i dont want to use that, with camera and mic and i need my router working again. I don't like android. It works there, though, but far from a solution.
Still no solution? Should it just work? Is it some host file error, or what? Someone should see the obvious answer right?
Can this help someone to answer? Yesterday i tried some settings and got:
Mon Oct 9 23:00:27 2023 daemon.info dnsmasq[14]: 1358 192.168.1.225/59078 config error is REFUSED (EDE: not ready)
Mon Oct 9 23:00:28 2023 daemon.info dnsmasq[1]: 1467 ::1/38979 query[A] 2.openwrt.pool.ntp.org from ::1
Mon Oct 9 23:00:28 2023 daemon.info dnsmasq[1]: 1467 ::1/38979 config error is REFUSED (EDE: not ready)
Mon Oct 9 23:00:28 2023 daemon.info dnsmasq[1]: 1468 127.0.0.1/38979 query[A] 2.openwrt.pool.ntp.org from 127.0.0.1
Mon Oct 9 23:00:28 2023 daemon.info dnsmasq[1]: 1468 127.0.0.1/38979 config error is REFUSED (EDE: not ready)
Mon Oct 9 23:00:28 2023 daemon.info dnsmasq[1]: 1469 ::1/38979 query[AAAA] 2.openwrt.pool.ntp.org from ::1
How shoudl i troubleshoot this, or where should i even start?
I played around with these settings..
/tmp/resolv.conf.d/resolv.conf.auto
/etc/dnsmasq.servers
But i uually get this error:
daemon.warn odhcpd[1352]: No default route present, overriding ra_lifetime!
so what do i do?
A 4G wan connection should not require modifying any of the default dhcp settings. Whatever you tried seems to be invalid, so you should go back to defaults.
This file is in RAM and is automatically generated as the network comes up and receives configuration from the ISP. It is pointless to edit it as it is temporary, but it is useful to inspect it to be sure that the upstream DNS has been properly configured.
This is an IPv6 related error which is to be expected and is harmless if the ISP does not support IPv6.
The first step in troubleshooting a "no internet" problem is to differentiate if it is a general routing problem or a DNS problem. If you can ping numeric sites such as 8.8.8.8 but not names like dns.google, there is a path to the Internet but DNS is not working.
Thanks, yeah i will look into it... i think it was connection issues with the signal strength, but i will see when i fix this.