-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've also heard that comcast was going after people setting up servers in the non-pro accounts. It seems that they only look at the default ports tho. So if you serve web from a non-standard port, you should be fine. About NAT, I seriously doubt they're doing anything about it (I know of examples of people using NAT -- which is as I understand what the linksys routers use -- for two years now, with no problems). Some dynamic dns servers will automatically forward web requests to the port you specify (look at the webhop service, by dyndns.org), i.e., people will type www.yourhost.com and get automatically say www.yourhost.com:12345. Adalberto On Monday 26 January 2004 11:27, Damon Register wrote:
In another post I commented that I had trouble yesterday with what seems to be Comcast blocking ports 21 and 80 so I couldn't serve ftp or http. I mentioned this to my brother who said he remembers reading somewhere that Comcast is "going after people running NAT" but he didn't remember any more. Has anyone else heard this? How would NAT be detected with SuSEfirewall2 on 9.0?
Damon Register -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux)
iQIVAwUBQBVXkN6AspoXaofZAQIHUQ/+KFwWTE0E1p7YKggSZaVtcSiaV7C9ajT5 EJHwsSdji318HUufluR7AqbPvwUPhrfXJNcZ65wh8b4YUT3EkxZXnf1aBOKnxmMw WM3VlR/BUnhVN2vYDrostONdNbvo6yPEcQPfqZK9m/49oSksIOOZQGxp7s8dWavh J5eo9h+yLMmd9qyI1/UXtx16YwwqE4Fb1p95GPEi1pnLeWQYuUFi7Y4fPUSVPeyM vjlZtig+Ei3YARt8h9TW7oCsvQd8Jic15zzJo/c1IHe8UCLNV7uDgd3ZqYnD7hUu JGYSuZZW6UJW5qZdt16pKcDVUwic3Zao7lJb3rTdjSLSQ81BHty5Vd2GTUXbNfjt 5rOarz+93ysi0xgbX0PNiE3kCvJDFl4qxwNYPi3cfQ5LiEHmsNh4k6PwdI5RxLwt kpvt4BHz+XeRnrCKOm13IpzuPWKis8XThOrxM75oI0jbnYEc8sgjWsSTxQCY0TUT PALpc7trcIMqGKBOACDwdex312LerTvE3EZHUdZwbqVSDZtfMbdc5IFqVVq6jEpY urlSbhHioXxB7EC2YxtCLReY4/UE0hg6KRZzkyTSnwUFnvJKYQllvMzcejLJzi28 IP7le8rAv7CAY4+nIQyNMG7jc5IR7UKdpGWJodzB8OHHeKD4Y0wM6WGe38WLlimt a/vTivVBEgQ= =iP5l -----END PGP SIGNATURE-----