You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Device problem occurs on
tp-link 1043nd hw ver 2.1 exact current case,
but 1043, 4300 many hw versions
Software versions of OpenWrt/LEDE release, packages, etc.
current, with exact problem:
BB14.07, 0.12+svn-r10530
and some another BB, CC about 6 cases on about 10 devices per last 2 years.
combinations with openvpn, p910nd, statistics, multiwan, etc
Mainly, I have to reset to defaults and reinstall sw and settings.
This time I have spare and bit of time to learn this case -
I've seen suddenly that ovpn tun connected to remote peer
(so, not a brick) but lan or that router lan ip not reacheble directly or via ovpn)
Steps to reproduce
change LAN IP by Luci 10.1.4.254 --> 10.1.9.254, save+apply
= semi-"brick", LAN missed totally
(another variants - edit network file, or set new lan ip by cli - the same results)
(sometimes I've seen that noscript or adblock prevent Luci make something,
but in this case transaction plan will be already at owrt side completely, imho)
Recover is possible,
ok from serial console
by vi edit 1 symbol in LAN IP at file /etc/config/network lan ip 9-->4
result - ok, totaly recovered.
found no more 1 place, where LAN IP stored and changed,
so, whats wrong during/after change LAN IP?
My scripts add some routes, but not for default LAN segment,
for remote via ovpn only, so I sure no errors
Bug is not exact LEDE, but may be inherited from BB-CC,
so imho report should be there.
I'm newbie at LEDE tracker,
so don't know better place for this report, moderate, please.
poor english, sorry!
The text was updated successfully, but these errors were encountered:
dennz:
change LAN IP
Supply the following if possible:
Device problem occurs on
tp-link 1043nd hw ver 2.1 exact current case,
but 1043, 4300 many hw versions
Software versions of OpenWrt/LEDE release, packages, etc.
current, with exact problem:
BB14.07, 0.12+svn-r10530
and some another BB, CC about 6 cases on about 10 devices per last 2 years.
combinations with openvpn, p910nd, statistics, multiwan, etc
Mainly, I have to reset to defaults and reinstall sw and settings.
This time I have spare and bit of time to learn this case -
I've seen suddenly that ovpn tun connected to remote peer
(so, not a brick) but lan or that router lan ip not reacheble directly or via ovpn)
Steps to reproduce
change LAN IP by Luci 10.1.4.254 --> 10.1.9.254, save+apply
= semi-"brick", LAN missed totally
(another variants - edit network file, or set new lan ip by cli - the same results)
(sometimes I've seen that noscript or adblock prevent Luci make something,
but in this case transaction plan will be already at owrt side completely, imho)
Recover is possible,
ok from serial console
by vi edit 1 symbol in LAN IP at file /etc/config/network lan ip 9-->4
result - ok, totaly recovered.
found no more 1 place, where LAN IP stored and changed,
so, whats wrong during/after change LAN IP?
My scripts add some routes, but not for default LAN segment,
for remote via ovpn only, so I sure no errors
Bug is not exact LEDE, but may be inherited from BB-CC,
so imho report should be there.
I'm newbie at LEDE tracker,
so don't know better place for this report, moderate, please.
poor english, sorry!
The text was updated successfully, but these errors were encountered: