Remember that a UDP "session" is defined as a local-ip-port/remote-ip-port
pair - if you are communicating with 2 disparate external hosts even if
you use the same internal port number the 2 connections will have
different masqueraded port numbers.
This is a consequence of how the system works - fixing it will take a
major rewrite.
You do need to watch timeouts - default is a few minutes. This can be
reset by ipfwadm.
Nigel.
[EMAIL PROTECTED] said:
} Really? I will forward this to the masq mailing list, as i was NOT
} aware of this behavior. I thought the local ip/port had a one-to-one
} mapping to the visible port number, and if the local host used the
} same source port for two separate "sessions" (processes, threads, what
} have you) the same external visible port would be used for both,
} seeing as the masq router has NO way of knowing they are "separate"
} sessions; i.e. it just looks up the ip/port pair in the Masq database,
} and either uses the existing entry or allocates a new (visible) port
} for the pair if the pair isn't in the database.
} btw. It WILL allocate a new external port if the other ip/port pair
} expired. The expiry time is rather short, so if you don't keep the
} entry "fresh" by periodically using the ip/port pair it will be
} deleted.
--
[ [EMAIL PROTECTED] - Systems Software Engineer ]
[ Tel : +44 113 207 6112 Fax : +44 113 234 6065 ]
[ Real life is but a pale imitation of a Dilbert strip ]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
