[SOLVED] Howto: Bind to one specific IP / Listen to one IP

[LinuxProphet]

Mr. Digi.
I tried the instructions you gave so eloquently. Alas, now I am having major issues with tomcat.
I even took the server down and re-installed. No problems until I edited the tomcat file and added the address= line.
The error is a java connect Connection refused error. Now I can't execute zmprov commands.
Any thoughts anyone?
Thanks
LP

[7223robh]

See my post a couple up (You need 7101/tcp listening on localhost). Apparently it works if you use zmprov -l but I've not tried it.

[1540ericg]

I submitted bug 20329 for the problem with the basic client and bind IP. The workaround of marcello would not cut it for me. Like you say it's a dirty hack and I'm not sure of the scalability of such a hack.
Anyway figured was better to report the problem and get it fixed at the source..
Vote for it!
Eric

[magikman]

I am having a bit of trouble getting mail through after using this method. After completing this, i am not longer able to receive mail, everything is being deferred. For some reason it is trying to connect to http://www.dvterry.com">http://http://www.dvterry.com rather than mail.dvterry.com. Where can i change with? The logs of this are:
Sep 15 08:35:05 www postfix/qmgr[26921]: 91D881F84D5: to=, relay=none, delay=7956, status=deferred (delivery temporarily suspended: connect to http://www.dvterry.com">http://http://www.dvterry.com[64.34.197.115]: Connection refused)
Sep 15 08:35:05 www postfix/qmgr[26921]: C38751F84BF: to=, relay=none, delay=15764, status=deferred (delivery temporarily suspended: connect to http://www.dvterry.com">http://http://www.dvterry.com[64.34.197.115]: Connection refused)
Anyone have any ideas? Is it possible to go through and remove everything relating to http://www.dvterry.com">http://http://www.dvterry.com and change it to mail.dvterry.com? Why can't you choose the binding IP/hostname during the initial install? That would be awesome and a much needed feature!

[carnold]

I am trying to get zimbra to bind to a specific ip and have followed the steps on the first page. However, we use zimbra 5 rc1 and zimbra 5 rc1 does no use tomcat, it uses jetty. So, how do users on zimbra 5 rc1 get jetty to bind to a specific ip?

[tuanta]

[quote user="dijichi2"]Great job, MrDigi! This is invaluable for many situations. It would be great to get this added to the wiki and refined over time.
Thanks for your work.[/QUOTE]
Could you please tell me where I can find the updated process compatible with Zimbra 5.0.
Thanks,

Tuan

[OneLoveAmaru]

I would also like to find information on binding zimbra to a specific IP, so that I can also run apache on this box with a different IP. mod_proxy just isn't working for me at all. I am running Debian Etch i386. Any help?????
*EDIT*
let me charify, i want to run ALL services on a seperate IP. if I can't do that, then just the webmail interface on a seperate IP. I would be alright with that, since the webadmin is on a non-standard port to begin with.

[carnold]

[quote user="OneLoveAmaru"]I would also like to find information on binding zimbra to a specific IP, so that I can also run apache on this box with a different IP. mod_proxy just isn't working for me at all. I am running Debian Etch i386. Any help?????
*EDIT*
let me charify, i want to run ALL services on a seperate IP. if I can't do that, then just the webmail interface on a seperate IP. I would be alright with that, since the webadmin is on a non-standard port to begin with.[/QUOTE]
By following the OP's first post, with the exception of jetty, i am running a separate instance of LDAP and Apache on the same box as Zimbra. I believe when you bind jetty to a specific IP to will accomplish the web interface you are looking to do. Just follow the first post and you should be fine.

[fverbeek]

I wanted postfix to send messages through a secondary IP address (failover address, not in a cluster, just a simple manual failover) instead of the primary address on the interface.

smtp_bind_address is not possible as explained above, and inet_addresses doesn't work for binding when sending, apparently.

After playing with postfix' config around for a while, I took the alternative route :rolleyes: :

iptables -t nat -A POSTROUTING -o eth0 

    -s the_primary_ip_addresses 

    -p tcp --dport 25 

    -j SNAT --to  the_ip_address_you_want_used

kinda ugly, but does the trick. Still listening on all addresses (including localhost), always sending through the chosen address :cool:

Just got to make sure it's documented somewhere....

[ChaosFreak]

[quote]JUST FOLLOW THE FIRST POST AND YOU SHOULD BE FINE.[/QUOTE]
UMM...THE FIRST POST HAS NO INSTRUCTIONS FOR ZIMBRA 5 WITH JETTY, IT ASSUMES ZIMBRA 4 WITH TOMCAT...
I FOUND THIS SOLUTION:

BINDING ZIMBRA TO A PARTICULAR IP
SEARCH FOR "PARTICULAR IP" IN THAT PAGE. OR, HERE ARE THE INSTRUCTIONS:

• EDIT /OPT/ZIMBRA/MAILBOXD/ETC/JETTY.XML.IN
  
  ADD YOUR-IP-ADDRESS TO THE HTTP CONNECTOR
  
  
• EDIT /OPT/ZIMBRA/MAILBOXD/ETC/ZIMBRA.WEB.XML.IN
  
  UNCOMMENT ZIMBRA.SOAP.URL, CHANGE LOCALHOST:7070 TO YOUR-IP-ADDRESS
  
  
• EDIT /OPT/ZIMBRA/MAILBOXD/ETC/ZIMBRAADMIN.WEB.XML.IN
  
  UNCOMMENT ZIMBRA.SOAP.URL, CHANGE LOCALHOST:7070 TO YOUR-IP-ADDRESS
  
  
• SU - ZIMBRA
  
  
• ZMCONTROL STOP
  
  
• ZMCONTROL START
  
  

:) IT WORKS FOR ME!