Hi List,
Is there a way to force SER to send requests from a user defined IP address when used on a multihomed system?
We have a box with two consecutive addresses 81.x.x.81 81.x.x.82 the primary address is .82 but it always uses .81, doesn't matter which way around the listen statements are.
Many Thanks,
Alan
------------------------------------------------------------------------------------------------------- This email, and any files transmitted with it, is copyright and may contain confidential information. The contents are intended for the use of the addressee(s) only. Unauthorized use may be unlawful. If you receive this email by mistake, please advise sender immediately. The views of the author may not necessarily constitute the views of Telco Electronics Limited. Nothing in this mail shall bind Telco Electronics Limited in any contract or obligation.
Telco Electronics Limited 6-8 Oxford Court Brackley Northants NN13 7XY
Tel 07000 701999 Fax 07000 701777
On Mar 02, 2004 at 15:35, Alan Litster alitster@telcoelectronics.co.uk wrote:
Hi List,
Is there a way to force SER to send requests from a user defined IP address when used on a multihomed system?
No. If mhomed is off (default), ser will send a message on the same socket it received it (so if you receive the message on .81, it will get sent on .81 too).
If mhomed is on ser will try to guess the outgoing interface and it will use it to send the message: if the outgoing interface for the message would be .81, then ser will send on .81, if it would be .82 => the message will be sent on .82. Notice that turning mhomed will introduce a performance penalty.
We have a box with two consecutive addresses 81.x.x.81 81.x.x.82 the primary address is .82 but it always uses .81, doesn't matter which way around the listen statements are.
The order of the listen statement is important for forwarding from tcp to udp, ipv6 to ipv4, locally generated requests (e.g. as a result of a fifo command). In all this cases the first non-loopback interface will be used.
Andrei