I'm sorry, I didn't clarify completely. I meant MSN's Video and Audio need to start working (I combined them in my head). No, I can't get them to work, but I've been doing some in depth research today to find out why. I've sent a message to the devel list asking for suggestions but as the netfilter list is the slowest list I've ever seen in my life, it hasn't got there yet.
Right now I only see 2 solutions. One is to have the linux firewall/nat box act as a UPNP device that can tell the Windows messenger what ip address it needs to use, or two, write netfilter modules that will look into the SIP, RDP, and RTP protocols and rewrite the source ip that Windows Messenger encapsulates in there. Also, there would have to be connection tracking as well so that netfilter would open up the ports on the firewall that the local client is sending with that local ip address and map it back. I'd write it, but I have no clue how to write nat modules. I may look into it tomorrow, but I was under the impression that if no one has done it yet, then it must be more complicated than I think. But like I said, I'll look into it a little more. If it's an encrypted protocol then I may be out of luck. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Aquiles Cohen > Sent: Wednesday, April 03, 2002 1:46 PM > To: [EMAIL PROTECTED] > Subject: Re: H323 Success > > > > > > > But like others have been wondering, we'd like to get MSN's video > > working now. As I understand it uses another protocol, SIP > or UPNP. > > Not sure the distinction here. Anyone have any good ideas > about this? > > The MSN voice chat is working??? > > > > Aquiles Cohen > Dialnet de Colombia >
