Problems with PyMSn :(

Ludo · July 15, 2006, 1:23pm

Hi,

My Wildfire Server is working… i am trying to add the PyMSNt module ! Everuthing look to be ok but I can’‘t subscribe to the transport : i can see the pymsn in the Wildfire Setup Tool (session tab) but it’'s is impossible to see the transport in my Psi client !

May you help me ?

Thx !!!

Ludo · July 15, 2006, 3:15pm

Must I open the 10015 port ?

Ludo · July 16, 2006, 2:08pm

No ideas ???

Manuzhai · July 16, 2006, 2:53pm

This place is usually a little silent on the weekends.

Andreas_Monitzer · July 16, 2006, 4:51pm

Does the transport not only show up in that session tab, but also say that it’'s an MSN transport? If this column is blank, there was an issue after connecting (like the invalid host name , or an error during service discovery).

Wildfire requires the transport’‘s name to be a direct subdomain of the server name, for example jivesoftware.com and msn.jivesoftware.com. If you have a setup like I did (like jabber.jivesoftware.com for the main server and msn.jivesoftware.com for the transport), it won’'t work.

Ludo · July 16, 2006, 5:49pm

Hi,

No it doesn’'t say it is an MSN Transport here is the text in the session tab :

Component Sessions

Connected External Components: 1 - Sessions per page:

Below is a list of connected external components to this server. You can also modify the external components settings.

Domain Name Category Type Creation Date Last Activity Close Connection

1 msn 6:56 PM 7:10 PM

List last updated: Jul 16, 2006 7:40:21 PM

There is nothing in the type field

Here is my debug.log :

Log opened.

INFO :: :: :: init :: PyTransport :: {’‘self’’: ‘‘instance’’}

INFO :: :: SVN r189 :: init :: PyTransport :: {’‘self’’: ‘‘instance’’}

INFO :: :: :: init :: ServerDiscovery :: {’‘pytrans’’: <main.PyTransport instance at 0xa129a54c>, ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addFeature :: ServerDiscovery :: {’‘var’’: ‘‘http://jabber.org/protocol/disco’’, ‘‘jid’’: ‘‘MSN’’, ‘‘handler’’: None, ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addFeature :: ServerDiscovery :: {’‘var’’: ‘‘http://jabber.org/protocol/disco’’, ‘‘jid’’: ‘‘USER’’, ‘‘handler’’: None, ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addIdentity :: ServerDiscovery :: {’‘category’’: ‘‘gateway’’, ‘‘jid’’: ‘‘MSN’’, ‘‘name’’: ‘‘Service MSN’’, ‘‘ctype’’: ‘‘msn’’, ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addIdentity :: ServerDiscovery :: {’‘category’’: ‘‘conference’’, ‘‘jid’’: ‘‘MSN’’, ‘‘name’’: ‘‘Service MSN Chatrooms’’, ‘‘ctype’’: ‘‘text’’, ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addFeature :: ServerDiscovery :: {’‘var’’: ‘‘jabber:x:conference’’, ‘‘jid’’: ‘‘MSN’’, ‘‘handler’’: None, ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addFeature :: ServerDiscovery :: {’‘var’’: ‘‘jabber:iq:conference’’, ‘‘jid’’: ‘‘MSN’’, ‘‘handler’’: None, ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addIdentity :: ServerDiscovery :: {’‘category’’: ‘‘client’’, ‘‘jid’’: ‘‘USER’’, ‘‘name’’: ‘‘MSN Messenger’’, ‘‘ctype’’: ‘‘pc’’, ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addFeature :: ServerDiscovery :: {’‘var’’: ‘‘jabber:iq:register’’, ‘‘jid’’: ‘‘MSN’’, ‘‘handler’’: , ‘‘self’’: ‘‘instance’’}

INFO :: :: :: init :: RegisterManager :: {’‘pytrans’’: <main.PyTransport instance at 0xa129a54c>, ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addFeature :: ServerDiscovery :: {’‘var’’: ‘‘jabber:iq:gateway’’, ‘‘jid’’: ‘‘MSN’’, ‘‘handler’’: , ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addFeature :: ServerDiscovery :: {’‘var’’: ‘‘jabber:iq:version’’, ‘‘jid’’: ‘‘MSN’’, ‘‘handler’’: , ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addFeature :: ServerDiscovery :: {’‘var’’: ‘‘jabber:iq:version’’, ‘‘jid’’: ‘‘USER’’, ‘‘handler’’: , ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addFeature :: ServerDiscovery :: {’‘var’’: ‘‘http://jabber.org/protocol/commands’’, ‘‘jid’’: ‘‘MSN’’, ‘‘handler’’: , ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addNode :: ServerDiscovery :: {’‘node’’: ‘‘http://jabber.org/protocol/commands’’, ‘‘jid’’: ‘‘MSN’’, ‘‘name’’: ‘‘command_CommandList’’, ‘‘self’’: ‘‘instance’’, ‘‘handler’’: , ‘‘rootnode’’: True}

INFO :: :: :: addFeature :: ServerDiscovery :: {’‘var’’: ‘‘vcard-temp’’, ‘‘jid’’: ‘‘USER’’, ‘‘handler’’: , ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addFeature :: ServerDiscovery :: {’‘var’’: ‘‘vcard-temp’’, ‘‘jid’’: ‘‘MSN’’, ‘‘handler’’: , ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addFeature :: ServerDiscovery :: {’‘var’’: ‘‘jabber:iq:avatar’’, ‘‘jid’’: ‘‘USER’’, ‘‘handler’’: , ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addFeature :: ServerDiscovery :: {’‘var’’: ‘‘storage:client:avatar’’, ‘‘jid’’: ‘‘USER’’, ‘‘handler’’: , ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addNode :: ServerDiscovery :: {’‘node’’: ‘‘connectusers’’, ‘‘jid’’: ‘‘MSN’’, ‘‘name’’: ‘‘command_ConnectUsers’’, ‘‘self’’: ‘‘instance’’, ‘‘handler’’: , ‘‘rootnode’’: False}

INFO :: :: :: init :: Proxy65 :: {’‘self’’: ‘‘instance’’, ‘‘port’’: 8010}

ft.Proxy65 starting on 8010

Starting factory <ft.Proxy65 instance at 0xa0c97a8c>

INFO :: :: :: addFeature :: ServerDiscovery :: {’‘var’’: ‘‘http://jabber.org/protocol/si’’, ‘‘jid’’: ‘‘USER’’, ‘‘handler’’: , ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addFeature :: ServerDiscovery :: {’‘var’’: ‘‘http://jabber.org/protocol/si/profile/file-transfer’’, ‘‘jid’’: ‘‘USER’’, ‘‘handler’’: , ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addFeature :: ServerDiscovery :: {’‘var’’: ‘‘http://jabber.org/protocol/bytestreams’’, ‘‘jid’’: ‘‘USER’’, ‘‘handler’’: , ‘‘self’’: ‘‘instance’’}

INFO :: :: :: addNode :: ServerDiscovery :: {’‘node’’: ‘‘stats’’, ‘‘jid’’: ‘‘MSN’’, ‘‘name’’: ‘‘command_Statistics’’, ‘‘self’’: ‘‘instance’’, ‘‘handler’’: , ‘‘rootnode’’: False}

Starting factory <tlib.xmlstream.XmlStreamFactory instance at 0xa129a42c>

INFO :: :: :: componentConnected :: PyTransport :: {’‘xmlstream’’: <tlib.xmlstream.XmlStream instance at 0xa0ca4fcc>, ‘‘self’’: ‘‘instance’’}

INFO :: :: Looking for handler :: onIq :: ServerDiscovery :: {’‘el’’: <tlib.domish.Element object at 0xa0c3226c>, ‘‘froj’’: <tlib.jabber.jid.JID instance at 0xa0c3278c>, ‘‘iqType’’: u’‘get’’, ‘‘self’’: ‘‘instance’’, ‘‘fro’’: u’‘component.jabber.binouzeworld.org’’, ‘‘ulang’’: None, ‘‘to’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘53-4’’}

INFO :: :: :: sendDiscoInfoResponse :: ServerDiscovery :: {’‘ulang’’: None, ‘‘to’’: u’‘component.jabber.binouzeworld.org’’, ‘‘jid’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘53-4’’, ‘‘self’’: ‘‘instance’’}

INFO :: :: Looking for handler :: onIq :: ServerDiscovery :: {’‘el’’: <tlib.domish.Element object at 0xa0c327cc>, ‘‘froj’’: <tlib.jabber.jid.JID instance at 0xa0c3298c>, ‘‘iqType’’: u’‘get’’, ‘‘self’’: ‘‘instance’’, ‘‘fro’’: u’‘revlam@jabber.binouzeworld.org/Psi’’, ‘‘ulang’’: None, ‘‘to’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘aac8a’’}

INFO :: :: :: sendDiscoInfoResponse :: ServerDiscovery :: {’‘ulang’’: None, ‘‘to’’: u’‘revlam@jabber.binouzeworld.org/Psi’’, ‘‘jid’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘aac8a’’, ‘‘self’’: ‘‘instance’’}

INFO :: :: Looking for handler :: onIq :: ServerDiscovery :: {’‘el’’: <tlib.domish.Element object at 0xa0c3296c>, ‘‘froj’’: <tlib.jabber.jid.JID instance at 0xa0c3298c>, ‘‘iqType’’: u’‘get’’, ‘‘self’’: ‘‘instance’’, ‘‘fro’’: u’‘revlam@jabber.binouzeworld.org/Psi’’, ‘‘ulang’’: None, ‘‘to’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘aac9a’’}

INFO :: :: :: sendDiscoItemsResponse :: ServerDiscovery :: {’‘ulang’’: None, ‘‘to’’: u’‘revlam@jabber.binouzeworld.org/Psi’’, ‘‘jid’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘aac9a’’, ‘‘self’’: ‘‘instance’’}

INFO :: :: Looking for handler :: onIq :: ServerDiscovery :: {’‘el’’: <tlib.domish.Element object at 0xa0c32aac>, ‘‘froj’’: <tlib.jabber.jid.JID instance at 0xa0c3298c>, ‘‘iqType’’: u’‘get’’, ‘‘self’’: ‘‘instance’’, ‘‘fro’’: u’‘revlam@jabber.binouzeworld.org/Psi’’, ‘‘ulang’’: None, ‘‘to’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘aacaa’’}

INFO :: :: :: sendDiscoInfoResponse :: ServerDiscovery :: {’‘ulang’’: None, ‘‘to’’: u’‘revlam@jabber.binouzeworld.org/Psi’’, ‘‘jid’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘aacaa’’, ‘‘self’’: ‘‘instance’’}

INFO :: :: Looking for handler :: onIq :: ServerDiscovery :: {’‘el’’: <tlib.domish.Element object at 0xa0c32bac>, ‘‘froj’’: <tlib.jabber.jid.JID instance at 0xa0c3298c>, ‘‘iqType’’: u’‘get’’, ‘‘self’’: ‘‘instance’’, ‘‘fro’’: u’‘revlam@jabber.binouzeworld.org/Psi’’, ‘‘ulang’’: None, ‘‘to’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘aacba’’}

INFO :: :: :: sendDiscoItemsResponse :: ServerDiscovery :: {’‘ulang’’: None, ‘‘to’’: u’‘revlam@jabber.binouzeworld.org/Psi’’, ‘‘jid’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘aacba’’, ‘‘self’’: ‘‘instance’’}

INFO :: :: Looking for handler :: onIq :: ServerDiscovery :: {’‘el’’: <tlib.domish.Element object at 0xa0c32cac>, ‘‘froj’’: <tlib.jabber.jid.JID instance at 0xa0c3298c>, ‘‘iqType’’: u’‘get’’, ‘‘self’’: ‘‘instance’’, ‘‘fro’’: u’‘revlam@jabber.binouzeworld.org/Psi’’, ‘‘ulang’’: None, ‘‘to’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘aacca’’}

INFO :: :: :: sendDiscoItemsResponse :: ServerDiscovery :: {’‘ulang’’: None, ‘‘to’’: u’‘revlam@jabber.binouzeworld.org/Psi’’, ‘‘jid’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘aacca’’, ‘‘self’’: ‘‘instance’’}

INFO :: :: Looking for handler :: onIq :: ServerDiscovery :: {’‘el’’: <tlib.domish.Element object at 0xa0c32dac>, ‘‘froj’’: <tlib.jabber.jid.JID instance at 0xa0c3298c>, ‘‘iqType’’: u’‘get’’, ‘‘self’’: ‘‘instance’’, ‘‘fro’’: u’‘revlam@jabber.binouzeworld.org/Psi’’, ‘‘ulang’’: None, ‘‘to’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘aacda’’}

INFO :: :: :: sendDiscoInfoResponse :: ServerDiscovery :: {’‘ulang’’: None, ‘‘to’’: u’‘revlam@jabber.binouzeworld.org/Psi’’, ‘‘jid’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘aacda’’, ‘‘self’’: ‘‘instance’’}

INFO :: :: Looking for handler :: onIq :: ServerDiscovery :: {’‘el’’: <tlib.domish.Element object at 0xa0ca420c>, ‘‘froj’’: <tlib.jabber.jid.JID instance at 0xa0c3298c>, ‘‘iqType’’: u’‘get’’, ‘‘self’’: ‘‘instance’’, ‘‘fro’’: u’‘revlam@jabber.binouzeworld.org/Psi’’, ‘‘ulang’’: None, ‘‘to’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘aacea’’}

INFO :: :: :: sendDiscoInfoResponse :: ServerDiscovery :: {’‘ulang’’: None, ‘‘to’’: u’‘revlam@jabber.binouzeworld.org/Psi’’, ‘‘jid’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘aacea’’, ‘‘self’’: ‘‘instance’’}

INFO :: :: Looking for handler :: onIq :: ServerDiscovery :: {’‘el’’: <tlib.domish.Element object at 0xa0ca410c>, ‘‘froj’’: <tlib.jabber.jid.JID instance at 0xa0c3298c>, ‘‘iqType’’: u’‘get’’, ‘‘self’’: ‘‘instance’’, ‘‘fro’’: u’‘revlam@jabber.binouzeworld.org/Psi’’, ‘‘ulang’’: None, ‘‘to’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘aacfa’’}

INFO :: :: :: sendDiscoItemsResponse :: ServerDiscovery :: {’‘ulang’’: None, ‘‘to’’: u’‘revlam@jabber.binouzeworld.org/Psi’’, ‘‘jid’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘aacfa’’, ‘‘self’’: ‘‘instance’’}

INFO :: :: Looking for handler :: onIq :: ServerDiscovery :: {’‘el’’: <tlib.domish.Element object at 0xa0ec03ec>, ‘‘froj’’: <tlib.jabber.jid.JID instance at 0xa129a6cc>, ‘‘iqType’’: u’‘get’’, ‘‘self’’: ‘‘instance’’, ‘‘fro’’: u’‘revlam@jabber.binouzeworld.org/Miranda’’, ‘‘ulang’’: None, ‘‘to’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘mir_6’’}

INFO :: :: :: sendDiscoItemsResponse :: ServerDiscovery :: {’‘ulang’’: None, ‘‘to’’: u’‘revlam@jabber.binouzeworld.org/Miranda’’, ‘‘jid’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘mir_6’’, ‘‘self’’: ‘‘instance’’}

INFO :: :: Looking for handler :: onIq :: ServerDiscovery :: {’‘el’’: <tlib.domish.Element object at 0xa129a68c>, ‘‘froj’’: <tlib.jabber.jid.JID instance at 0xa129a6cc>, ‘‘iqType’’: u’‘get’’, ‘‘self’’: ‘‘instance’’, ‘‘fro’’: u’‘revlam@jabber.binouzeworld.org/Miranda’’, ‘‘ulang’’: None, ‘‘to’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘mir_7’’}

WARN :: :: Unknown Iq request :: onIq :: ServerDiscovery :: {’‘node’’: None, ‘‘el’’:

I hope you will help me

Message was edited by: revlam

Andreas_Monitzer · July 16, 2006, 9:00pm

This line:

2006-07-16 19:10:59 WARN :: :: Unknown Iq request :: onIq :: ServerDiscovery :: {’‘node’’: None, ‘‘el’’: <tlib.domish.Element object at 0xa129a68c>, ‘‘froj’’: <tlib.jabber.jid.JID instance at 0xa129a6cc>, ‘‘iqType’’: u’‘get’’, ‘‘self’’: ‘‘instance’’, ‘‘fro’’: u’‘revlam@jabber.binouzeworld.org/Miranda’’, ‘‘ulang’’: None, ‘‘to’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘xmlns’’: u’‘jabber:iq:register’’, ‘‘query’’: <tlib.domish.Element object at 0xa0c9d0ac>, ‘‘searchjid’’: u’‘msn.jabber.binouzeworld.org’’, ‘‘ID’’: u’‘mir_7’’}

is describing the issue you have. I don’'t have any idea how to decrypt it or how to fix the issue, though.

Perhaps the WIldfire’‘s domain (listed as “Server Name” in the server settings tab in the admin interface) isn’'t “jabber.binouzeworld.org”? When I upgraded my server to 3.0.1, it somehow lost the correct information for it and just supplied the one given by the hostname command.

Ludo · July 16, 2006, 10:44pm

No everything is ok, my serveur domain is jabber.binouzeworld.org ! I don’'t understand

Christophe_Gravier · July 20, 2006, 4:57pm

I’'ve tried to install it today and I have the same problem.

Latest PyMSNt and wildfire 3.0.1 python 2.3.x and twisted 2.4

Christophe_Gravier · July 20, 2006, 5:01pm

Fixed the type “blank” by setting the tag in config.xml of Pymsnt from

// this is my jabber server

HTH.

But I can register my MSNt but it is directly set to offline:

Failed to connect to MSN servers: [Failure instance: Traceback (failure with no frames): exceptions.Exception: Timeout

]

(in my psi client after some times it tries to put the transport online)

Regards.

Message was edited by: cgravier

Ludo · July 20, 2006, 10:23pm

I changed the JID too and now it’'s ok ! i open 10015 port on NAT too !

Thx ! If your have the same pb tell me more i can help you !

Bye

Christophe_Gravier · July 21, 2006, 9:05am

Glad it helpt

What is this 10015 port for ?

I open it and it still doesn’'t change a thing.

I can register, it says it is successfull, but the agent transport isn’'t going online. I can authorized it though. After 30 sec (approx.) psi tells me:

Failed to connect to MSN servers: [Failure instance: Traceback (failure with no frames): exceptions.Exception: Timeout

]

In fact, the only thing I got in wildfire log is:

2006.07.21 10:36:40 org.jivesoftware.wildfire.update.UpdateManager$1.run(UpdateManager.java:120) Error checking for updates

java.net.UnknownHostException: www.jivesoftware.org

at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:177)

at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)

at java.net.Socket.connect(Socket.java:507)

at java.net.Socket.connect(Socket.java:457)

at java.net.Socket.(Socket.java:238)

at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocke t(DefaultProtocolSocketFactory.java:79)

at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocke t(DefaultProtocolSocketFactory.java:121)

at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:706)

at org.apache.commons.httpclient.HttpMethodDirector.executeWithRetry(HttpMethodDir ector.java:386)

at org.apache.commons.httpclient.HttpMethodDirector.executeMethod(HttpMethodDirect or.java:170)

at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:396)

at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:324)

at org.jivesoftware.wildfire.update.UpdateManager.checkForServerUpdate(UpdateManag er.java:182)

at org.jivesoftware.wildfire.update.UpdateManager$1.run(UpdateManager.java:112)

As I run wildfire behind a proxy, I think I miss some configuration for it ?

(debug is enaled in wildfire)

I launch pyMSNt with -d flag pfor debug output but I receive nothing.

So i think there’‘s a problem only between my client and my serveur (the name I use aren’'t yet in DNS so I edit may /etc/hosts.conf).

I see that I hadn’‘t msn.myserver.com in my hosts file (so msn.myserver wasn’'t resolve to an ip address !).

I add it but I still got the same issue

PS: same problem ehre: http://www.jivesoftware.org/community/thread.jspa?messageID=125404&#125404 but the solution isn’'t mention

Well well flushing all the rules, I have no longer the message on my psi client (which does I need to open though ?)

But the agent transport stay to offline (because of my proxy ?)

Message was edited by: cgravier

Christophe_Gravier · July 21, 2006, 9:43am

Let me add that i modify my iptables rules to get dropped packets.

I add to, for testing purpose, allow:

iptables -A INPUT -i eth0 -s 161.3.1.11 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT

iptables -A INPUT -i eth0 -s 161.3.1.42 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT

iptables -A INPUT -i eth0 -s 65.54.239.140 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT

iptables -A INPUT -i eth0 -s 207.46.0.0/16 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT

And thus I don’'t have the mesage on my psi client (but the transport is still offline ).

Each time it seems it is a random high port that is used. Is there a possibility to restrict it to some fix ports ?
As I use a non transparent proxy (hum I mean I have to do with it) and a firewall I don’'t control … For MSNt, are there any port that must be open from the outside world ?

jeff_garner · July 21, 2006, 11:58am

Yes, pyMSNT has three port to open to the outside world so that it can talk and allow file transfer. look in the readme file included with the installation, it will give you good advice, as well as the port names to open up on the firewall.

Jeff

Ludo · July 21, 2006, 8:31pm

Mh

Try to open the port : 8010

The port 10015 is the port where wildfire listen to accept a connection from a gateway (external composant) like Pymsn-t !

Can you up your config.xml please and the result of the ‘‘iptables -L’’ command

Message was edited by: revlam

Christophe_Gravier · July 21, 2006, 8:54pm

Sorry I can’'t do this now as the network from which I depend is down (breakdown :/)

Today is begining of holidays … I hope they will put it back online :S

Nevertheless, I opened those ports (I’'ll post iptables listing as soon as the network is up) and the config.xml …

But !

I first need my jabber.myserver.com and msn.jabber.myserver.com to be registered in DNS and the port 443, 8010 open from the outside. (it is open on my firewall and on my subnet but I depend on a university firewall so I need time to make those 3 ports open in a front firewall (and the guys have to deal with the breakdown, remember ^^)

I’'ll post when the ports are open and DNS entries updated.

Nevertheless, what I don’'t understand, is that it seems I have to allow :

iptables -A INPUT -i eth0 -s 65.54.239.140 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT

iptables -A INPUT -i eth0 -s 207.46.0.0/16 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT

since pymsnt seems to need them … (I trace it in syslog by logging dropped packet).

I really DON’‘T understand why it is and why it is using random high ports on my server … (I definitly won’'t allow entire external ips to my server …)

What are you iptables rules ? (again, i’‘m soo upset I can’'t post mine )

Message was edited by: cgravier