https://bugzilla.novell.com/show_bug.cgi?id=280403 ------- Comment #3 from mvdv@spamcop.net 2007-06-05 22:43 MST ------- Another two hints, I don't know if you could put this down as a bug....? Hint 1: ======= If you move on from just making local connections on the same machine then you will need to open up port 5000:tcp. More for more connections. Not great, but maybe you can use the knockd daemon and knock client to open ports - would be good to add the knock client facility into the KNX connection parameters, may be secured with some pass word/passphrase/private key? anyway back to the topic..... What happens if one of the '5000+' range of ports is currently occupied? I don't know. Hint 2: ======= If you want to connect to more than one remote machine you should just add the remote host's private key to the client machines authorized_keys2 file: You'll need to look in the remote hosts & clients nxsetup script or nxloadconfig file to work out where these are.... it seems to differ between distributions and even arch.... but they are consistently bizarre locations - to my mind at least :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.