Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

connectivity issues



Speaking as someone who configures routers for ISPs and has participated
in policy drafting on such matters, I want to point out that blocking
ports 137 and 139 is typically done as a courtesy to customers.

One reason we do this is to prevent users from being attacked by Winnuke,
Bonk, and similar tools favored by script kiddies.  We also prevent script
kiddies from attacking the outside world by using our dial-up services.

However, another concern is that we do not want dial-up users showing up
in each other's Windows "Network Neighborhood."  If someone really wants
to use CIFS networking from a dial-up Internet connection, we tell them
that they can use VPN with PPTP or something else that provides control.

-- Mike


On 2001-08-12 at 01:46 -0400, Derek Martin wrote:

> [O.k. not exactly -- they block 137 and 139 too.  I can complain on
> general principal, but I don't use Windows networking so it doesn't
> affect me one iota.]


-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request at blu.org (Subject line is ignored).




BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org