I've searched as much as I possibly could to find a solution to this.  I found you can bind it on another port, which is all well and good, but it still listens on *:port on any attached interface.

 

Is there another command line trigger to run it on IP:PORT ?  I'm trying to keep it on 80, and start apache on another interface on 80, but emhttp is keeping that from happening.  I'd prefer to keep emhttp on 80 on eth0 and apache on 80 on eth1.

 

Thanks for any help--

 

I've searched as much as I possibly could to find a solution to this.  I found you can bind it on another port, which is all well and good, but it still listens on *:port on any attached interface.

 

Is there another command line trigger to run it on IP:PORT ?  I'm trying to keep it on 80, and start apache on another interface on 80, but emhttp is keeping that from happening.  I'd prefer to keep emhttp on 80 on eth0 and apache on 80 on eth1.

 

Thanks for any help--

 

no way I know of.

is it changed in 5.x at all?  I would think it should respect the first interface and not bind across all of them--is this by design?

is it changed in 5.x at all?  I would think it should respect the first interface and not bind across all of them--is this by design?

again, unknown. 

 

Report it as a bug to lime-tech.  Perhaps it will get some attention that way.  (But don't hold your breath waiting for a change)

 

Joe L.

It listens on all interfaces. This is by design. It only brings up eth0, however.