Quote:
Originally posted by SecretMethod70
Either way, I just wanted to point out that if you connect a Windows box to the internet through a Linux box that forwards the connection, you will likely have a lot of trouble with online gameplay and such. That's something I didn't know and didn't think of the time that I did this.
|
True, as are FTP connections (which are a nightmare to 'masquerade').
My setup allows all traffic that originates from my backend / LAN to pass right through, and all replies are automagically returned to my PC. But connections from outside are initially denied.
If you run a game/ftp/web/dcc/kazaa/whatever server on your backend it will receive no traffic as the connections are attempted from outside. That is why I have the 'dungeon siege' section in my config (see my first post) which opens the ports dungeon siege servers use. So that allows me to run a dungeon siege server (which I no longer have, but that's beside the point) behind my firewall.
So any server that uses static ports like most games, webservers and such are easily forwarded by expanding that section for the right ports.
FTP is different in that it allocates dynamic ports. Some work has been done to allow ftp transfers through a firewall, but that does not seem to always work. I need to set my ftp-client to "passive mode" or it will fail.
The same goes for MS netmeeting.
In short you'll have no problems with:
- Game clients (play on other servers)
- Browsing / telnet
- e-mail
You'll have small problems with:
- Game servers (setting up your own behind a firewall)
- web servers / dchub's
- IM clients (ICQ, Trillian, MSN, etc)
- most FTP clients
You'll have large problems with:
- Netmeeting
- FTP clients that don't support "passive transfers" like old versions of Internet Explorer
However, these problems are all prevented if you just forward 'everything' through the firewall like
JStrider was planning to do.