Community Discussions and Support
Listen on 2 ip's

It's possible to run more than one instance of Mercury, from different directories. As they have separate settings it would be possible to have them listen on different interfaces. They would however have separate mailbox directories as well.

 

<p>It's possible to run more than one instance of Mercury, from different directories. As they have separate settings it would be possible to have them listen on different interfaces. They would however have separate mailbox directories as well.</p><p> </p>

Hi, everybody.

Do you know if Mercury can listen on 2 differente ip's?

I tested with 1 ip and it's ok, or empty listen on all ip's.

How can setup to listen on ip 192.168.1.128 and 192.168.1.228, the cpu has several more ip's.

 Thanks

<p>Hi, everybody. </p><p>Do you know if Mercury can listen on 2 differente ip's?</p><p>I tested with 1 ip and it's ok, or empty listen on all ip's.</p><p>How can setup to listen on ip 192.168.1.128 and 192.168.1.228, the cpu has several more ip's. </p><p> Thanks </p>

This is what Mercury help says about this subject (in this case MercuryS, but applies to other server modules as well):

If your computer supports multiple IP interfaces, you can use this field to tell MercuryS which interface it should select when listening for connections: enter the interface as a dotted IP address in the general form www.xxx.yyy.zzz. As an example, your system may have one IP address assigned to a dialup PPP connection, and another, different IP address assigned to a local Ethernet network - you would enter here the interface MercuryS should use. If you leave this field blank, MercuryS will listen on all available interfaces. Unless you are very sure of what you are doing, or have been instructed by an ISP or network administrator, you should leave this field blank. If you change the IP interface in this field, you must restart Mercury before the new interface number will be used. 

<p>This is what Mercury help says about this subject (in this case MercuryS, but applies to other server modules as well):</p><blockquote><p><i>If your computer supports multiple IP interfaces, you can use this field to tell MercuryS which interface it should select when listening for connections: enter the interface as a dotted IP address in the general form www.xxx.yyy.zzz. As an example, your system may have one IP address assigned to a dialup PPP connection, and another, different IP address assigned to a local Ethernet network - you would enter here the interface MercuryS should use. If you leave this field blank, MercuryS will listen on all available interfaces. Unless you are very sure of what you are doing, or have been instructed by an ISP or network administrator, you should leave this field blank. If you change the IP interface in this field, you must restart Mercury before the new interface number will be used. </i></p></blockquote>

Thanks for the reply, the issue is how to listen on 2 ip's because it's "Listen on 1 Ip" or "Listen in all IP's"

 

By example:

     IP interface to use:  (blank)               this listen on all available ip's

    IP interface to use: 192.168.1.100      this listen on 192.168.1.100

If I want to listen on 192.168.1.100 but also in 192.168.1.200 (of course this machine has more ip's)

 

<p>Thanks for the reply, the issue is how to listen on 2 ip's because it's "Listen on 1 Ip" or "Listen in all IP's"</p><p> </p><p>By example:</p><p>     IP interface to use:  (blank)               this listen on all available ip's</p><p>    IP interface to use: 192.168.1.100      this listen on 192.168.1.100</p><p>If I want to listen on 192.168.1.100 but also in 192.168.1.200 (of course this machine has more ip's)</p><p> </p>

The way I read it it's one or all. Depending on circumstances there are perhaps some possible workarounds, like setting connection control for relevant server modules to block access from IP addresses in subnets that shouldn't be able to connect, or running multiple instances of Mercury. 

<p>The way I read it it's one or all. Depending on circumstances there are perhaps some possible workarounds, like setting connection control for relevant server modules to block access from IP addresses in subnets that shouldn't be able to connect, or running multiple instances of Mercury.<span style="font-size: 10pt;"> </span></p>

I remember reading that you have more than one instance of Mercury open - although I've never done this. Can the separate instances be configured to listen on different interfaces, Rolf?

I remember reading that you have more than one instance of Mercury open - although I've never done this. Can the separate instances be configured to listen on different interfaces, Rolf?
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft