Emilia Hane

moving `NatResolver` into `Discovery` would require making a service for `NatResolver`. as you point this out, it is fine to leave `NatResolver` in `NetworkInner`. what we should still do though...

> I see, so if I understand correctly, the ideal functionalities would be > > * `--disable-discovery` should disable all discovery services, including `NatResolver` > * To enable NatResolver only...

- Separated the semantics of discovery and local ip address resolution after all. IP address resolution is done regardless if discovery is disabled. Usually discovery is disabled to isolate the...

@cody-wang-cb can you try out the solution I made and see if it work for your setup? @mattsse there is a test for the docker IP resolution, which passes in...

I added my fix, that was overwritten, here https://github.com/paradigmxyz/reth/pull/10681. still think it's reasonable if you try this code in your docker cluster @cody-wang-cb before proceeding. unassigning myself

> Hey @emhane, sorry I checked again actually, `--net-if.experimental "eth0"` looks like it's just exposing `172.`. If I understand correctly this is the address of the docker container itself, and...

thanks for the explanation @cody-wang-cb . how about using the provided solution with `--net-if`, and setting up one container with a static ip to use as boot node? this will...

> @emhane I don't know networking very well but I don't think this really works cross hosts? I think the `172.x.x.x` ips are isolated per host. This is what I...

why do you specifically want to not use the host network driver? because it would be the best suited for your setup

> @emhane In theory we can run it on host mode but that'll require a bunch of other changes like fixing port collisions. We've been running our chain infra with...