However, since reboot, the LED is static white, the AP is not requesting an IP with dhcp. It seems to be working in bridge mode: if I connect a laptop to it to its the secondary RJ45, I get network an IP assigned (no hop on traceroute).
If I try to assign a static IP 192.168.1.10 to the laptop with gateway 192.1.1.1, I cannot connect. How it is supposed to get itself IP http://192.168.1.1/ ?
Note that the main network is not on 192.168. but on 10....
I checked
Is it a problem with the firmware update or just a basic openwrt config I misunderstand? What did I miss to get an IP assigned?
A device with two ports will firstboot with one of the ports as lan and one as wan. It sounds like in this case the port that accepts PoE is the lan. You can only log in with that port, since the default firewall prohibits logging in from wan.
This means connect the PoE port only to your laptop using a separate PoE injector or switch. Then you can obtain a 192.168.1 IP on the laptop and log in to OpenWrt. From there you can set up the configuration that meets your use case.
Do not connect the lan side to your exising network at first, since OpenWrt default is to serve DHCP and this will conflict with and disrupt operation of the network.
I connected only the laptop and the AP with a distinct PoE switch, completely outside the network. The Laptop is configured to use IP 192.168.1.25 gateway 192.168.1.1. It fails to ping 192.168.1.1. No route to host. I dont see any assigned IP. No DHCP either.
Is it possible that the firmware install bricked it?