Re: Pyro4 Flame SSH Reverse Tunneling
<[email protected]> Thu, 2 Oct 2014 12:49:04 +0000
| Newsgroups | gmane.comp.python.pyro |
|---|---|
| Message-ID | <[email protected]> |
I gonna check that but what i find weard is is working with Standard Pyro object i use port 8999 for flame and 9000- 9009 for standard who is suppost to be free.. Thank ! Ne manquez pas notre <Symposium 2014 : LE rendez-vous des g?ants en TI> le mardi 28 octobre prochain ? l'h?tel Ch?teau Laurier! Inscrivez-vous d?s maintenant : www.ebr.ca/evenements/symposiumqc2014<http://www.ebr.ca/evenements/symposiumqc2014> [cid:logodedfd9] Martin Lapointe Technicien [email protected] Informatique EBR Inc. 365, rue Racine Est, Bureau 204 Chicoutimi (Qc) G7H 1S8 T?l.:(418) 543-2600 # 2119 Sans frais: 1 (800) 567-2336 Fax : (418) 543-0363 http://www.ebr.ca P Devez-vous vraiment imprimer ce courriel? Pensez ? l'environnement... Ce message est confidentiel et est ? l'usage exclusif de son destinataire. Il est strictement interdit ? toute autre personne de le diffuser, le distribuer ou le reproduire. Si le destinataire ne peut ?tre joint ou vous est inconnu, veuillez informer l'exp?diteur par courrier ?lectronique imm?diatement et effacer ce message et en d?truire toute copie. ________________________________ De : F.C <[email protected]> Envoy? : 2 octobre 2014 08:44 ? : Pyro mailing list Objet : Re: [Pyro] Pyro4 Flame SSH Reverse Tunneling Ah ok, looks like ok for your configuration!!!! i couldn't yet help you more, but try to verify your firewall status for outgoing or incoming protocoles and ports, maybe your firewall is blocking it.... 2014-10-02 8:37 GMT-04:00 Martin Lapointe <[email protected]<mailto:[email protected]>>: Thank for help Fcabarrus, but when i request config i have the folowing result and as we can see FLAME_ENABLED = True is suposse to be ok. Just for help When i connect on local on flame serveur is working If i connection my reverse port to cups web port i can access remotely but when i connect to Flame port i have the folowing error <<Pyro4.errors.CommunicationError: cannot connect: [Errno 111] Connection refused>> Thank for help Active configuration settings: AUTOPROXY = True BROADCAST_ADDRS = <broadcast>, 0.0.0.0 COMMTIMEOUT = 0.0 COMPRESSION = False DETAILED_TRACEBACK = False DOTTEDNAMES = False FLAME_ENABLED = True HMAC_KEY = None HOST = localhost LOGFILE = None LOGLEVEL = None LOGWIRE = False MAX_MESSAGE_SIZE = 0 METADATA = True NATHOST = None NATPORT = 0 NS_BCHOST = None NS_BCPORT = 9091 NS_HOST = localhost NS_PORT = 9090 ONEWAY_THREADED = True PICKLE_PROTOCOL_VERSION = 2 POLLTIMEOUT = 2.0 PREFER_IP_VERSION = 4 REQUIRE_EXPOSE = False SERIALIZER = pickle SERIALIZERS_ACCEPTED = set(['json', 'pickle', 'marshal', 'serpent']) SERVERTYPE = thread SOCK_REUSE = False THREADING2 = False THREADPOOL_SIZE = 16 And check if "flame_enable=3D True", if not change it by True ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Pyro-core mailing list [email protected]<mailto:[email protected]> https://lists.sourceforge.net/lists/listinfo/pyro-core ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Pyro-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pyro-core
logodedfd9
(image/jpeg, 1.6 KB) - not displayed