thats what the sticker says
had to reboot again, ran dmesg and found nothing , lan cable just lose connections is like is disconnected the cable but is not the cable i come from openbsd and that did not happened, it started with openwrt, please help im puzzled and exhausted and i do not know what to do, the usb adapter is recognized in LSUSB but if i type ifconfig it wont show eth2 it show only eth0 and eth1 not eth3
there wouldn't be an eth3, if there's no eth2.
this the dmesg when it exploded , it do not show anything weird, just stop working, it says cable disconnected, yet eth0 (intel) can ping to modem, but realtek shuts down i do not know what is happening, how can i start using the usb lan as eth? i mean lsusb detect it but ifconfig shows no adapter

i agree, its eth2
is there any way to see openwrt logs? like cat /etc/logs or something? sorry for being such a ignorant
dmesg
for past log entries, logread -f
for future entries.
thank you!!! , logread -f will do the job now we arent blind, just we have to wait for the fnord again
there's no proof of any communication issue(s) in that photo, that I can see.
ctrl-c the logread, and run a continuous ping towards som IP on internet, even your ISPs DNS, if it replies.
if i run ping i get response
that's the whole point, keep it running.
see if it starts to fail once you have an outage.
I thought you installed 8139too - per another thread?
will do, thanks
it is already installed
Then I would uninstall the wrong one (review message again). I don't see any post noting you resolved that issue posted from the log - my apology if you fixed it already.
it is weird because 8139to did not worked, 1000e did the job
Your statement is unclear. I'm not sure what you mean when saying an Intel driver "did the job" for a Realtek NIC.
Also, to be clear, it's e1000e.
sorry , i mean the 8**too did not make the realtek work, it was the e1000e that made it work, i believe, i do not know what to think, it crashed again, the ping did not stop so is not wan is lan
dmesg
logread -f
Let's try one more time:
As I already noted, this belief is incorrect - and your log clearly shows otherwise.
It seems you fixed the 8139too (or you just didn't show us this previously).