This is a new thread related to an earlier post about Olimex ESP32-Gateway. Thinking that board just wasnt supported I searched for “ESP32 POE” and came up with another Olimex board. ESP32-POE - Open Source Hardware Board
I can’t get Ethernet working on this either.
Steps:
Using the online installer I installed WLED/ethernet on the ESP32 POE. I connected through my wireless router and noted the IP address 192.168.86.27
I connected my mac via USBC/ethernet adapter to a Netgear JGS524 switch. System settings/ network shows I am connected to an AX881179A. In TCP/IP I set:
Configure IPv4 = Manually
IP address = 192.168.20.10
Subnet mask = 255.255.255.0
Via WiFi browser, in WLED I set:
Static IP = 192.168.20.20
Subnet mask = 255.255.255.0
Ethernet Type = ESP32-POE
I disabled Wifi on my Mac, hoping to find the ESP via ethernet.
In a browser, neither 192.168.86.27 nor 192.168.20.20 find the ESP. Pinging doesn’t connect either.
I read a couple of posts that said sometimes the online WLED ethernet installer didn’t seem to install a working version with a recommendation to try flashing with ESPTool. I did this and got the same result - can’t find the ESP32.
Help! Am I doing somethign wrong?
Alternatively, is the list of ethernet protocols supported by WLED manufacturer specific? Is the ESP32-POE type meant to apply to a specific manufacturer/ it’s not a generic name?
If that is the case, can someone recommend a manufacturer/ board known to work well? My requirements are:
Wifi and Ethernet support
6 output pins to control LEDs
This 16,000 LED / 20 ESP32 project is going to burning man in August and I’d really like to replace WiFi with Ethernet for that environment. I’m on the US West Coast.
So, setting your WLED to 192.168.20.20 and your router to 192.168.86.27, unless you have proper subnetted network rules/ACL’s/Firewall’s configured for each subnet (assuming they are same VLAN too?), you can not talk out to the internet on it. Your WLED will NOT connect to the router/internet.
If you are going to setup a static IP and you do not have subnetting/VLAN’s configured on your network, just a basic wifi router hooked up to your modem, then set your static IP to an IP outside your scope, but within your subnet. i.e. Your router is 192.168.86.27 and your scope is set from 192.168.86.100-192.168.86.254 tthen you can set (assuming nothing else is on this IP) to anything between 192.168.86.1-192.168.86.100.
You can not just change the IP subnet like that when you are using 192.168.86.0/24 (which is what you indicated)
So leave your wifi on your laptop, wipe your static IP info in your WLED controller and either put to a proper IP or DHCP and then get the new IP and put that into your web browser and it will connect to the WLED controller and WLED can talk out to the internet.
Thank you. I’m not a network pro and may have miscommunicated. Once WLED was installed on the ESP32 I gave it access to my wireless router and disconnected the USB cable. Router DHCP assigned 192.168.86.27 to the ESP32 and I communicated with WLED from my Mac via a browser to that IP. Via browser, I went to WLED config and specified ESP32-POE Ethernet type and gave it static IP 192.168.20.20 and subnet 255.255.255.0.
I then connected both my Mac and the ESP32 to a Netgear ethernet switch (which I understand does not have DHCP, it’s just a passthru). On my Mac I turned off WiFi, went into it’s ethernet connection with the switch and edited TCPIP 192.168.20.10 and subnet 255.255.255.0.
What I thought I was doing was making it possible for my Mac (192.168.10.10) to talk to the ESP32 (192.168.10.20) via the ethernet switch. WiFi and the WiFi router is out of scope.
With my knowledge level it’s hard for me to interpret your answer but I have the impression you think WiFi is part of my final architecture. WiFi was just there to get up and running - the goal is Mac/ESP via ethernet cables through a switch. Does that impact your answer?
I would try and get the ESP32 connected via cable and DHCP 1st before trying to hard code an address.
If your WiFi router is giving out DHCP addresses via WiFi, you should be able to plug the router into your Netgear switch (the router should have a few LAN ports) then plug the Mac and the ESP32 into the Netgear.
If you have turned off WiFi on the Mac, you should still get a hardwired IP address and internet access. Once that’s proven, connect the ESP32 and see if it gets a hardwired address.
Having a DHCP server (your WiFi router) on the net will be easier to start out. Once you’ve proven a wired connection, you can try and move forward.
So for your network, you are looking to ISOLATE your WLED controllers on their own switch with NO internet access and the ONLY way to connect to it (since no DHCP with that subnet) is to manually plug in your laptop into the switch and set your IP to the same subnet? Why would you setup like this? Is this just to isolate it all for security? Not sure I’m understanding the use case for doing it this way.
For this case, you can do that. If you set the WLED ethernet IP’s to that .20.x subnet, then setting your laptop address to the .20.x subnet too then would work. Setting your laptop to .10.x will NOT work as that is again a diffrent subnet.
So if you do this… Set your WLED controllers with IPs of 192.168.20.10, 192.168.20.11,192.168.20.12,192.168.20.13,192.168.20.14, and so on. Then on your laptop eithernet, plug into that same switch and change your IP of your laptop ethernet to 192.168.20.1. Now when you open chrome and go to 192.168.20.10, the wled controller WILL load up.
If you are setting up your WLED with static IP’s on their own switch with no internet access, for your own sanity and ease of accessing and typing, I would use static IPs of 10.10.10.x for them all. Just is so much easier to type repeatedly then 192.168.20.x.
So doing this, you just need to make sure your on the same subnet with your WLED and Laptop. and your subnet is 255.255.255.0 which equals a 192.168.20.0/24 (writen a diffrent way, prefered by network engineers, but says the same thing without typing out all the extra bits), then that means your IP SCOPE is 192.168.20.1-192.168.20.254 (192.168.20.255 being the multicast address). So this means your laptop you were giving a 192.168.10.20 address, that is NOT in that same scope. And the only way for the .10.20 address to talk to .20.10 is over a network router with rules setup to allow various network traffic to talk over the subnets (this is a MUCH more advanced network leason…) But just keep is simple like i said above. 10.10.x.x space is a “private” subnet as well, just like 192.168.x.x and 172.16.x.x (some special rules in there, but this is just a gist).