Got a brand new One. Consol works, WAN works (updated). No LAN access. No dhcp (up and running). I did all the Linux crack head stuff commands i can think of, even asked my llm, all services up and running, luci running, firewall disabled. LAN device on handshake works, but there is no access to the One on LAN. Updated latest FW (USB), same. eth0 ist up, addr added, flushed, br-lan manual settet, dnsmasq all checked, running, config checked lan os not ignored … did ntf rule flush, nothing.
Did try multi devices, 2 laptops, … 2 cables, added switch, even used coross over cable
Am i 2 stupid for this “One”? Well i send it back to the seller either way, this is nothing for the retail market.
Since the console works, let's see the config to try to find out what's wrong...
Please connect to your OpenWrt device and copy the output of the following commands and post it here using the "Preformatted text </> " button (red circle; this works best in the 'Markdown' composer view in the blue oval):
Remember to redact passwords, VPN keys, MAC addresses and any public IP addresses you may have:
As far as i know there is a LAN, TCP handshake that runs between two devices in a nework to handle what speed a device can do and such stuff. That works, devices do connect to the LAN port of the One but there is no “real” connection, no data transfer. Over WAN i can find it in my network, even ping it as you can see, the default config allows it. But over LAN port, nothing.
In my opinion, this is not a config issue. There should be some data transfer between two devices, something to sniff no matter how bad my config is. I mad a small LAN data sniffer back in the days, there is nothing going on on the LAN port besides the handshake itself.
I did a few software resets, did the clear & reset images and NOR switch. All the stuff seems to work but not my LAN port. Did open up the case, can’t see any damage on the network port itself (doent meant it is not broken in some way) or solder points. Maybe a firmware can fix it?
No idea how to fix this by myself, dont got the time for it.
Thanks, ill send it back. Looks like a cool device.
The WAN port was connected once to use the opkg update command.
Yes, WAN is not “direct” to the internet, it is inside my network. The device got internet access to update. There is no reason to share my local network, it will not fix the LAN port issue.
Is your upstream network 192.168.1.0/24?? If so, that's your problem.
you cannot have the wan and lan using an overlapping subnet. In that case, you need to change one or the other (the easy one to change is the OpenWrt One's lan -- make its address something like 192.168.52.1).
Sure, but since 3 resets and one throw out of the window, it was not connected anymore ot my local network. To clearfy, my local network is a class a not c, starts with 10, not 192. But since the One is not connected and resettet multiple times, he does not know that network i run.
Ok... well, given that you've been rather sparse on the details and somewhat unwilling to provide them when asked, we can't really help.
FWIW, RFC1918 addresses do not reveal any sensitive data about your network. And in this case, it's not the issue if you're on the 10. netblock instead of 192.168.1.0/24. But nonetheless, it's safe to provide that information and necessary in many cases to successfully debug issues.
That said, you seem more interested in returning the device than troubleshooting to see if it is a device hardware issue, firmware, config, or some other problem.
So, you want me to the the One out of the box again, and send you the WAN output? It is the default output you get, because it is not connected to the WAN and was not connected to the WAN port since a few soft and hard resets. To what end?
It will not connect to LAN with default settings. Thats it. Can you fix that by config?
Again: It is not a matter of bad config, there is ZERO = 0 data transfer on LAN port. There is ALWAY some transfer over LAN if two devices are connected, there is always something going on. Dosent matter if you use a win, linux, mac or playstation, os and apps always send somehting.
You seem angry, though. I get the frustration of a possible hardware defect (and I can’t rule that out). But for the future, remember that the more info you can provide the better.
Hello,
i just ask the following questions to make sure i understood you right:
Your LAN is a 10.x.x.x network
The ONE WAN is not connected
If you just connect a device with DHCP enabled (PC, Notebook, whatever with a single ethernet cable, no other connection) only to the ONE LAN port you won't get neither an IPv4 (in the 192.168.1.x range) nor an IPv6 address.
Because you are sure that both the cable and the device are otherwise working absolutely without problems, i also would assume that your ONE is defective.
That might happen, but of course it really s*cks.
Better luck next time...