Developer info for NAT ALG

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am working on improving an existing NAT ALG that we use for helping MSN's
talk, whiteboard and remote assistance to work through NAT.

I was wondering if there is a list of messages that contain payloads, or
some protocol document that explains the messages that are sent back and
fourth.

Is there some partnership that Microsoft has with other companies to give
them updates when there is a change in the protocol or advanced warning on
new releases of the protocol so that our routers can get testing on the new
protocol? I dont know where to start with this...

I have looked around and have just found posts talking avout older MSN
protocols, nothing close to MSNP14
 
Greetings Brent,

A lot of these features have changed in the various Messenger versions and are changing in
Vista. As such, why are you creating a ALG? Why not just support UPnP which would allow all
this to work, regardless of versions now and in the future?

--
Jonathan Kay
Microsoft MVP - Windows Messenger/MSN Messenger/Windows Live Messenger
Associate Expert
http://www.microsoft.com/windowsxp/expertzone/
Messenger Resources - http://messenger.jonathankay.com
All posts unless otherwise specified are (c) 2006 Jonathan Kay.
You *must* contact me for redistribution rights.
 
UPnP does not work in all settings, especially corperate settings, The
routers I am working on are used in a corperate setting and in many cases you
can not depend on UPnP traversing through the corperate network. Most
security people would also tell you that UPnP is VERY unsafe in a corperate
environment.

We already have an existing ALG that handles the voice, video, whiteboard,
and filesharing, but the original writer had no clue how to write a TCP alg
(they treated every packet like it had a single message in it, and that is
not the case with TCP), So I am having to rewrite it.

I have gotten it working with basic features, but keep running into new
commands that have payloads associated with them, and was wondering if I can
quit the guessing work and get a list of all possible commands. What might
help us in the future is some form of a messenger developer mail list that
would send out changes/additions to the protocol.

Do you know if there is some partnership that Microsoft does with 3rd
parties for this kind of thing, they would have had to do something like this
with cisco or any other vendors that do ALGs
 
Back
Top