i'm currently unable to reach the internet through the router
yes, i turned it off and back on again. i rebooted both the router and the modem. several times
lan IPv4: 10.0.1.1/24, IPv6: fd06:4aab:e32b::1/60.
wan has no ip
earlier today my ISP was down, but it is back up now
i can get internet by connecting directly to modem, bypassing router
in the last week, i installed a bunch of tasmota dimmers, idk if that's relevant. they were up and working for at least a few days now
i tried setting option igmp_snooping '1' in the file /etc/config/network as suggested by another thread (can't find that thread now), to no avail. not sure what this option does, so i turned it back off now.
i don't know what else might be helpful to troubleshoot. here's the tail of logread
# logread | tail
Tue Jan 10 10:51:31 2023 kern.info kernel: [10456.160628] mtk_soc_eth 1b100000.ethernet eth0: configuring for fixed/2500base-x link mode
Tue Jan 10 10:51:31 2023 kern.info kernel: [10456.168972] mtk_soc_eth 1b100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx
Tue Jan 10 10:52:56 2023 kern.err kernel: [10541.084726] mtk_soc_eth 1b100000.ethernet eth0: transmit timed out
Tue Jan 10 10:52:56 2023 kern.info kernel: [10541.091242] mtk_soc_eth 1b100000.ethernet eth0: Link is Down
Tue Jan 10 10:52:56 2023 kern.info kernel: [10541.120851] mtk_soc_eth 1b100000.ethernet eth0: configuring for fixed/2500base-x link mode
Tue Jan 10 10:52:56 2023 kern.info kernel: [10541.129206] mtk_soc_eth 1b100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx
Tue Jan 10 10:54:11 2023 kern.err kernel: [10616.124727] mtk_soc_eth 1b100000.ethernet eth0: transmit timed out
Tue Jan 10 10:54:11 2023 kern.info kernel: [10616.131067] mtk_soc_eth 1b100000.ethernet eth0: Link is Down
Tue Jan 10 10:54:11 2023 kern.info kernel: [10616.160578] mtk_soc_eth 1b100000.ethernet eth0: configuring for fixed/2500base-x link mode
Tue Jan 10 10:54:11 2023 kern.info kernel: [10616.168905] mtk_soc_eth 1b100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx
i tried some stuff in other threads, but so far i'm still in the same situation.
any help is much appreciated. if there's some other logs that would be helpful, i'll post those too. about to go afk for 12 hours.
The eth0 which keeps going up and down in the log is the internal link from the CPU chip to the switch chip, and it is not supposed to do that. It should start up once and stay up.
Which version are you running? 22.03.3 should work.
haven't power cycled the router since hitting upgrade. i'll be afk for at least an hour running errands, hoping it just needs more time and everything will work perfectly when i return.
thanks @mk24 for notifying me of the new version. unfortunately, it currently does not look promising.
What IP do you get on your laptop? If it is, for example, somethign in the 192.168.1.0/24 range, it would be expected that the router would also be in that range (default for OpenWrt is 192.168.1.1). Therefore, the router wouldn't be reachable at 10.0.1.1 (unless you set it as such after installing openwrt).
ah, i figured it kept the settings from before the upgrade.
there's no other device i could be connected to. the ethernet cable goes from my laptop to the router. there's no other router with the essid my wifi is connected to. i disconnected and reconnected the wifi after the upgrade process finished.
so ... it's still running something. maybe because i haven't power cycled, it's still running the old image from ... ram?
ok, weird.
now the router has the following lan IPv4: 10.0.1.1/24, wan IPv4: 24.6.31.217/21
but my laptop is unable to get to the internet through wifi, but it does get an ip at least.
laptop doesn't get an ip on ethernet from the router.
lol, wan disappeared.
here's another tail of logread
# logread | tail
Tue Jan 10 12:33:03 2023 kern.err kernel: [ 4157.174865] mtk_soc_eth 1b100000.ethernet eth0: transmit timed out
Tue Jan 10 12:33:03 2023 kern.info kernel: [ 4157.181178] mtk_soc_eth 1b100000.ethernet eth0: Link is Down
Tue Jan 10 12:33:03 2023 kern.info kernel: [ 4157.210709] mtk_soc_eth 1b100000.ethernet eth0: configuring for fixed/2500base-x link mode
Tue Jan 10 12:33:03 2023 kern.info kernel: [ 4157.219042] mtk_soc_eth 1b100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx
Tue Jan 10 12:34:33 2023 kern.err kernel: [ 4247.174865] mtk_soc_eth 1b100000.ethernet eth0: transmit timed out
Tue Jan 10 12:34:33 2023 kern.info kernel: [ 4247.181184] mtk_soc_eth 1b100000.ethernet eth0: Link is Down
Tue Jan 10 12:34:33 2023 kern.info kernel: [ 4247.210755] mtk_soc_eth 1b100000.ethernet eth0: configuring for fixed/2500base-x link mode
Tue Jan 10 12:34:33 2023 kern.info kernel: [ 4247.219222] mtk_soc_eth 1b100000.ethernet eth0: Link is Up - 2.5Gbps/Full - flow control rx/tx
Tue Jan 10 12:35:21 2023 authpriv.info dropbear[7415]: Child connection from XXX
Tue Jan 10 12:35:21 2023 authpriv.notice dropbear[7415]: Pubkey auth succeeded for 'root' with ssh-rsa key SHA256:XXX from XXX
reset to default settings, ethernet worked fine, 192.168.1.1
turned on wifi with former essid and pw, and immediately was unable to connect.
reset to default settings again. ethernet worked fine. enabled wifi, but different essid and pw (just to be sure), and that's working fine too.
so now i think it really is something to do with all the tasmota devices connecting. i have maybe 20 different devices (bulbs and dimmers). does that sound plausible?
Please copy the output of the following commands and post it here using the "Preformatted text </> " button:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
config defaults
option syn_flood 1
option input ACCEPT
option output ACCEPT
option forward REJECT
# Uncomment this line to disable ipv6 rules
# option disable_ipv6 1
config zone
option name lan
list network 'lan'
option input ACCEPT
option output ACCEPT
option forward ACCEPT
config zone
option name wan
list network 'wan'
list network 'wan6'
option input REJECT
option output ACCEPT
option forward REJECT
option masq 1
option mtu_fix 1
config forwarding
option src lan
option dest wan
# We need to accept udp packets on port 68,
# see https://dev.openwrt.org/ticket/4108
config rule
option name Allow-DHCP-Renew
option src wan
option proto udp
option dest_port 68
option target ACCEPT
option family ipv4
# Allow IPv4 ping
config rule
option name Allow-Ping
option src wan
option proto icmp
option icmp_type echo-request
option family ipv4
option target ACCEPT
config rule
option name Allow-IGMP
option src wan
option proto igmp
option family ipv4
option target ACCEPT
# Allow DHCPv6 replies
# see https://github.com/openwrt/openwrt/issues/5066
config rule
option name Allow-DHCPv6
option src wan
option proto udp
option dest_port 546
option family ipv6
option target ACCEPT
config rule
option name Allow-MLD
option src wan
option proto icmp
option src_ip ffff::/10
list icmp_type '130/0'
list icmp_type '131/0'
list icmp_type '132/0'
list icmp_type '143/0'
option family ipv6
option target ACCEPT
# Allow essential incoming IPv6 ICMP traffic
config rule
option name Allow-ICMPv6-Input
option src wan
option proto icmp
list icmp_type echo-request
list icmp_type echo-reply
list icmp_type destination-unreachable
list icmp_type packet-too-big
list icmp_type time-exceeded
list icmp_type bad-header
list icmp_type unknown-header-type
list icmp_type router-solicitation
list icmp_type neighbour-solicitation
list icmp_type router-advertisement
list icmp_type neighbour-advertisement
option limit 1000/sec
option family ipv6
option target ACCEPT
# Allow essential forwarded IPv6 ICMP traffic
config rule
option name Allow-ICMPv6-Forward
option src wan
option dest *
option proto icmp
list icmp_type echo-request
list icmp_type echo-reply
list icmp_type destination-unreachable
list icmp_type packet-too-big
list icmp_type time-exceeded
list icmp_type bad-header
list icmp_type unknown-header-type
option limit 1000/sec
option family ipv6
option target ACCEPT
config rule
option name Allow-IPSec-ESP
option src wan
option dest lan
option proto esp
option target ACCEPT
config rule
option name Allow-ISAKMP
option src wan
option dest lan
option dest_port 500
option proto udp
option target ACCEPT
### EXAMPLE CONFIG SECTIONS
# do not allow a specific ip to access wan
#config rule
# option src lan
# option src_ip 192.168.45.2
# option dest wan
# option proto tcp
# option target REJECT
# block a specific mac on wan
#config rule
# option dest wan
# option src_mac 00:11:22:33:44:66
# option target REJECT
# block incoming ICMP traffic on a zone
#config rule
# option src lan
# option proto ICMP
# option target DROP
# port redirect port coming in on wan to lan
#config redirect
# option src wan
# option src_dport 80
# option dest lan
# option dest_ip 192.168.16.235
# option dest_port 80
# option proto tcp
# port redirect of remapped ssh port (22001) on wan
#config redirect
# option src wan
# option src_dport 22001
# option dest lan
# option dest_port 22
# option proto tcp
### FULL CONFIG SECTIONS
#config rule
# option src lan
# option src_ip 192.168.45.2
# option src_mac 00:11:22:33:44:55
# option src_port 80
# option dest wan
# option dest_ip 194.25.2.129
# option dest_port 120
# option proto tcp
# option target REJECT
#config redirect
# option src lan
# option src_ip 192.168.45.2
# option src_mac 00:11:22:33:44:55
# option src_port 1024
# option src_dport 80
# option dest_ip 194.25.2.129
# option dest_port 120
# option proto tcp
internet still works today with default settings. in about 2 hours, i'll try changing it back to the wifi essid and pw that all the tasmota devices will connect to and see what happens.