You are complicating again .
1. You don't need any port forwarding. All insim stuff works with local connection on same machine as server.
2. InSim port is NOT the same thing as game port ! It must be different. Leave game port as it is, just use different insim one (i recommend /insim 29999 so you don't have to change cfg)
3. LFS said that it cannot bind the port, because you wanted to use the same one for insim which was already used for game !
4. The error you got (connected closed ...) simply means LFSLapper could not connect to port you specified, which means either you didn't start LFS server yet, or LFS Server's insim port on LFS was not open for listening.
5. Yes those files are for coders only.. readme.txt is for users.
Installing and running LFSLapper is very easy actually, usually people just need to change password in cfg file, and then they just run StartNetDefault (or sth like that).
1. You don't need any port forwarding. All insim stuff works with local connection on same machine as server.
2. InSim port is NOT the same thing as game port ! It must be different. Leave game port as it is, just use different insim one (i recommend /insim 29999 so you don't have to change cfg)
3. LFS said that it cannot bind the port, because you wanted to use the same one for insim which was already used for game !
4. The error you got (connected closed ...) simply means LFSLapper could not connect to port you specified, which means either you didn't start LFS server yet, or LFS Server's insim port on LFS was not open for listening.
5. Yes those files are for coders only.. readme.txt is for users.
Installing and running LFSLapper is very easy actually, usually people just need to change password in cfg file, and then they just run StartNetDefault (or sth like that).