Olivier ARCHER comments

Results 58 comments of


                                            Olivier ARCHER

[wifi, ethernet] Allow Wifi AP to reuse existing network interface (ethernet or modem) for NAT

Sorry for the title, just changed it!

[wifi, ethernet] Allow Wifi AP to reuse existing network interface (ethernet or modem) for NAT

@nagyrobi , Yes, the wifi AP still offer DHCP for clients. It also send the previously found DNS server to. It then configure NAT. The doc title is "Allow Wifi...

[wifi, ethernet] Allow Wifi AP to reuse existing network interface (ethernet or modem) for NAT

> Any plans to make configurable some DHCP-specific options? Like custom DNS, NTP, no gateway, etc... Not for the moment, I want to keep this PR as small as possible....

[wifi, ethernet] Allow Wifi AP to reuse existing network interface (ethernet or modem) for NAT

@rosbeef Yes, L2 bridging is probably more efficient and faster than the current implementation. This version relies on `ip_napt_enable`, which does most of the work. It's convenient for small use...

[wifi, ethernet] Allow Wifi AP to reuse existing network interface (ethernet or modem) for NAT

I've tried to setup L2 bridging, but it seems impossible to use it with a ppp netif. I was able to copy packets from the wifi netif to the ppp...

[wifi, ethernet] Allow Wifi AP to reuse existing network interface (ethernet or modem) for NAT

Yes @rosbeef , it's exactly what I mean

[wifi, ethernet] Allow Wifi AP to reuse existing network interface (ethernet or modem) for NAT

Keep open until https://github.com/esphome/esphome/pull/6721#issuecomment-3366238958

md5 checksum of firmware, and 'esphome publish' command

Currently, I've added `CORE.firmware_md5`, `CORE.firmware_gz`, `CORE.firmware_gz_md5`, but it might not be a good idea. I've done that because `espota2.py` compute md5 by his own, and I've refactored it to use...