Tjeezzes ...
I don't get a connection over eth2 of the access point. Not only no IP address, but not a connection. The LAN cable works, and so does the notebook on other (switch)ports.
I might say I could exclude hardware, cause I tried both access points...
YOU say "connection over eth2 of the access point" here. Can we agree ?
If you can not get an IP address when connected to ether2 port of cap ac, something is wrong with your config on that cap ac as well unless you specifically configured it that way but then I would expect you also know how to undo that.
Simple. OK ?
Is that cap ac connected to that same device from your other tread ?
well, cool, I got the access point this Monday, took it off the box and rebooted into caps mode like the manual says.
In the other thread I want to find the root cause of getting no ip address from the DHCP-server, which seems to be bart of a bug that had to do with quick-setup.
So I wasn't all MY fault... when there's a bug and I don't know that this old bug makes the devices unusable,... Should I first read all the things of the last 10 years just to know every bit? It would take ages...
Maybe it's too much to expect a device running somehow out of the box... I'll overthink that.
Second: I wrote (please read carefully) that I not only get no IP address, but I didn't get A CONNECTION. The light didn't went on, the notebook didn't recognize any changes.
As if the port was turned off. But it wasn't me, I did nothing on the ap after unboxing and rebooting to caps.