[FreeNX-kNX] kNX behind a firewall (only port 22 open) unusable?

LROUFAIL at nc.rr.com LROUFAIL at nc.rr.com
Sat Feb 19 12:50:43 UTC 2005


In moznx, See Protocol.cpp

It does send the switch command (Protocol::SendSwitch()).

The code is a little convoluted (based on nxrun/nxcompsh) and my changes have made it pretty ugly, but it seems to work.

 - L

----- Original Message -----
From: Fabian Franz <FabianFranz at gmx.de>
Date: Friday, February 18, 2005 5:03 pm
Subject: Re: [FreeNX-kNX] kNX behind a firewall (only port 22 open) unusable?

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Am Freitag, 18. Februar 2005 22:45 schrieb LROUFAIL at nc.rr.com:
> > I looked at the code and they have not yet implemented the new 
> session> negotiation scheme for SSH connections required by 1.4.0.
> 
> Its not yet in the code.
> 
> At least I could not find any code indicating that you were using 
> the switch 
> command. So I duess moznx also does not yet tunnel over ssh or 
> source is not 
> updated.
> 
> cu
> 
> Fabian
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> 
> iD8DBQFCFnRSI0lSH7CXz7MRAolbAJ41PwS8ddPaE8OfqZ7N3GLqh6rhqwCfT7bE
> dCHTNP83TFuOta1ypEieuug=
> =iJI2
> -----END PGP SIGNATURE-----
> 
> _______________________________________________
> FreeNX-kNX mailing list
> FreeNX-kNX at kde.org
> https://mail.kde.org/mailman/listinfo/freenx-knx
> 




More information about the FreeNX-kNX mailing list